Historic archive of defunct list bismark-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Nick Feamster <feamster@cc.gatech.edu>
To: bismark-devel@lists.bufferbloat.net
Subject: [Bismark-devel] flashing woes - instructions don't seem to work
Date: Thu, 14 Apr 2011 01:58:41 -0400	[thread overview]
Message-ID: <323A8B55-1A33-4D13-90EE-CED6CC8934C7@cc.gatech.edu> (raw)

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.

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 did not get any of the flashing sequences that the instructions describe.  At this point, tftp fails, and I see very strange pings:

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
cp:61 62 63 64 65 66 67 68 
	69 6a 6b 6c 6d 6e 6f 70 71 72 73 74 75 76 77 61 
	62 63 64 65 66 67 68 69  0  0  0  0  0  0  0  0 
	 0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0 
dp:4d a6 8c 35  0  d 19 93 
	 8  9  a  b  c  d  e  f 10 11 12 13 14 15 16 17 
	18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 
	28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37 
40 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=-331079122350.903 ms

So, at this point, I am stuck.

-Nick

             reply	other threads:[~2011-04-15  0:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  5:58 Nick Feamster [this message]
2011-04-15 17:32 ` Dave Taht
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=323A8B55-1A33-4D13-90EE-CED6CC8934C7@cc.gatech.edu \
    --to=feamster@cc.gatech.edu \
    --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