From: Dave Taht <d@taht.net>
To: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] Bismark flash success! + 5 GHz radio issue
Date: Wed, 20 Apr 2011 15:36:54 -0600 [thread overview]
Message-ID: <4DAF51F6.7090103@taht.net> (raw)
In-Reply-To: <4DAF4F0E.6080909@taht.net>
On 04/20/2011 03:24 PM, Dave Taht wrote:
> My assumption is that this is a queued up mail.
>
> There was a new build done earlier today which:
>
> Removed the time applet from busybox (gnu time needs to be packaged up
> correctly and included in the image at some point soon)
>
> Points to a temporarily correct opkg database
>
> Turns on ECN, SACK, and DSACK
>
> Enabled the ATH_USER_REG parameter.
>
> Is built from openwrt head and openwrt package head.
It also applies the following patches to gain us more insight into the
behavior of the wireless interface(s).
(and the pfifo_fast fix is in there from git head)
so the sum of these things are that you will need to reflash from
scratch to see all this stuff.
PLEASE See also the open and closed issues on:
http://www.bufferbloat.net/issues/
notably 94,92,88
(to see the closed issues, uncheck the filter for open and apply)
I disabled mountd (#93) in the last build, also got ECN in there by
default...
>
> On 04/19/2011 11:49 PM, Nick Feamster wrote:
>> 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
>> _______________________________________________
>> Bismark-devel mailing list
>> Bismark-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bismark-devel
>
> _______________________________________________
> Bismark-devel mailing list
> Bismark-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-devel
next prev parent reply other threads:[~2011-04-20 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 5:49 Nick Feamster
2011-04-20 14:06 ` [Bismark-devel] Fwd: " Nick Feamster
2011-04-20 21:24 ` [Bismark-devel] " Dave Taht
2011-04-20 21:36 ` Dave Taht [this message]
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=4DAF51F6.7090103@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