Historic archive of defunct list bismark-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <d@taht.net>
To: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] flashing woes - instructions don't seem to work
Date: Fri, 15 Apr 2011 11:32:01 -0600	[thread overview]
Message-ID: <4DA88111.1090704@taht.net> (raw)
In-Reply-To: <323A8B55-1A33-4D13-90EE-CED6CC8934C7@cc.gatech.edu>

On 04/13/2011 11:58 PM, Nick Feamster wrote:
> Guys,
>
> I think the instructions need some work.
>
> First, I tried the "sysupgrade" with the appropriate binary.  That appeared to re-flash the router, but not otherwise do much.  After that upgrade, the router appeared on 192.168.42.1, but I could no longer ssh into it, and the normal Web interface did not work.

Usually the only interface enabled after a reflash is telnet. Was telnet 
busted, too?

Otherwise you've found a bug. Up until now I've been reflashing with 
atftp exclusively on Linux.

> Then, I figured I would try Srikanth's flashing instructions.  First, it's not clear what the "reset" button is.  I figure that must be the factory reset button, as opposed to some button on the front of the box (I tried everything).
I have revised the instructions here.

http://www.bufferbloat.net/projects/bismark/wiki/Flashing_instruction_for_Mac

> I did not get any of the flashing sequences that the instructions describe.  At this point, tftp fails, and I see very strange pings:
Hmm... what did you get? how long did you hold the button down for? (see 
above instructions)
> 1:54am:kenmore-square:tmp% ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1): 56 data bytes
> 40 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=-331079123350.339 ms
> wrong total length 60 instead of 84
> wrong data byte #8 should be 0x8 but was 0x69

This is normal, actually. You are pinging a very primitive network stack 
built into uboot(redboot?). The system time is set to the epoch. (1970 
or so)

It sounds like your tftp failed.

>  So, at this point, I am stuck.


Still stuck?



  reply	other threads:[~2011-04-15 17:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  5:58 Nick Feamster
2011-04-15 17:32 ` Dave Taht [this message]
2011-04-15 17:37   ` Nick Feamster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DA88111.1090704@taht.net \
    --to=d@taht.net \
    --cc=bismark-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox