Historic archive of defunct list bismark-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Nick Feamster <feamster@cc.gatech.edu>
To: Brian Poole <bpoole@cc.gatech.edu>, Dave Taht <d@taht.net>,
	Srikanth Sundaresan <srikanth@gatech.edu>,
	Walter de Donato <walter.dedonato@unina.it>
Cc: bismark-devel@lists.bufferbloat.net
Subject: [Bismark-devel] Fwd: Bismark flash success! + 5 GHz radio issue
Date: Wed, 20 Apr 2011 10:06:25 -0400	[thread overview]
Message-ID: <0C8DBEE9-C292-44ED-9E74-A21976CCC0C7@cc.gatech.edu> (raw)
In-Reply-To: <3BFD72FA-D352-4B3C-A743-6393A77603B8@cc.gatech.edu>

I didn't see this go out to the list, so I am re-sending.

Begin forwarded message:

> From: Nick Feamster <feamster@cc.gatech.edu>
> Date: April 20, 2011 1:49:24 AM EDT
> To: bismark-devel@lists.bufferbloat.net
> Subject: Bismark flash success! + 5 GHz radio issue
> 
> Just flashed with Brian's new bismark-enabled image.  Hot!  Everything (mostly) worked.  I encountered an issue with the 5Ghz radio, which seems to be a known issue related to this:
> http://code.google.com/p/x-wrt/issues/detail?id=169
> 
> Has anyone else encountered this?
> 
> A few other points
> - strangely, telnet didn't work after flash, but I was able to set the root password by going to the web interface instead
> - it would be nice if we could enable the radios by default, perhaps as part of a startup script
> 
> To idiot-proof the instructions, we should tell people when to connect the WAN port to the uplink (perhaps right before a reboot, after configuring the root password?  that seems to be a fool-proof place)
> 
> -Nick


  reply	other threads:[~2011-04-20 20:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20  5:49 [Bismark-devel] " Nick Feamster
2011-04-20 14:06 ` Nick Feamster [this message]
2011-04-20 21:24 ` Dave Taht
2011-04-20 21:36   ` Dave Taht
2011-04-20 21:38     ` Dave Taht
2011-04-20 22:00   ` Nick Feamster
2011-04-20 22:12   ` Dave Taht
2011-04-20 22:14     ` Nick Feamster
2011-04-20 22:24       ` Dave Taht
2011-04-20 22:25         ` 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=0C8DBEE9-C292-44ED-9E74-A21976CCC0C7@cc.gatech.edu \
    --to=feamster@cc.gatech.edu \
    --cc=bismark-devel@lists.bufferbloat.net \
    --cc=bpoole@cc.gatech.edu \
    --cc=d@taht.net \
    --cc=srikanth@gatech.edu \
    --cc=walter.dedonato@unina.it \
    /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