* Re: [Bismark-devel] Bismark flash success! + 5 GHz radio issue
2011-04-20 21:24 ` [Bismark-devel] " 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
2 siblings, 1 reply; 10+ messages in thread
From: Dave Taht @ 2011-04-20 21:36 UTC (permalink / raw)
To: bismark-devel
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bismark-devel] Bismark flash success! + 5 GHz radio issue
2011-04-20 21:24 ` [Bismark-devel] " Dave Taht
2011-04-20 21:36 ` Dave Taht
@ 2011-04-20 22:00 ` Nick Feamster
2011-04-20 22:12 ` Dave Taht
2 siblings, 0 replies; 10+ messages in thread
From: Nick Feamster @ 2011-04-20 22:00 UTC (permalink / raw)
To: Dave Taht; +Cc: bismark-devel
Excellent! I will try re-flashing my box tonight to see if my issues are resolved in the new version.
Thanks!
-Nick
On Apr 20, 2011, at 5: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.
>
> 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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bismark-devel] Bismark flash success! + 5 GHz radio issue
2011-04-20 21:24 ` [Bismark-devel] " Dave Taht
2011-04-20 21:36 ` Dave Taht
2011-04-20 22:00 ` Nick Feamster
@ 2011-04-20 22:12 ` Dave Taht
2011-04-20 22:14 ` Nick Feamster
2 siblings, 1 reply; 10+ messages in thread
From: Dave Taht @ 2011-04-20 22:12 UTC (permalink / raw)
To: bismark-devel
On 04/20/2011 03:24 PM, Dave Taht wrote:
>> 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
>
hmm
>> - it would be nice if we could enable the radios by default, perhaps
>> as part of a startup script
>>
The problem here is that there is a script ("wifi") that runs on first
boot that has to dynamically determine the mac addresses. I otherwise
mostly agree, it would be nice if the radios went up by default, but
that is "insecure" by default....
So maybe there is a way to get wifi to run with a reasonable default for
encryption etc?
>> 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)
It's a wiki, anybody can change it. If you think something can be
improved or changed, go right ahead and *do* it. Someone can always
change it differently on you later. There are no trees to be killed,
only electrons to be burnt. Do try to call people's attention to dubious
changes in email...
>>
>> -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
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [Bismark-devel] Bismark flash success! + 5 GHz radio issue
2011-04-20 22:12 ` Dave Taht
@ 2011-04-20 22:14 ` Nick Feamster
2011-04-20 22:24 ` Dave Taht
0 siblings, 1 reply; 10+ messages in thread
From: Nick Feamster @ 2011-04-20 22:14 UTC (permalink / raw)
To: Dave Taht; +Cc: bismark-devel
Cool... I'll change instructions. Just wanted to run my experience by folks first (and for my own benefit, before I forgot :-)
On Apr 20, 2011, at 6:12 PM, Dave Taht wrote:
> On 04/20/2011 03:24 PM, Dave Taht wrote:
>>> 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
>>
> hmm
>
>>> - it would be nice if we could enable the radios by default, perhaps as part of a startup script
>>>
> The problem here is that there is a script ("wifi") that runs on first boot that has to dynamically determine the mac addresses. I otherwise mostly agree, it would be nice if the radios went up by default, but that is "insecure" by default....
>
> So maybe there is a way to get wifi to run with a reasonable default for encryption etc?
>
>>> 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)
>
> It's a wiki, anybody can change it. If you think something can be improved or changed, go right ahead and *do* it. Someone can always change it differently on you later. There are no trees to be killed, only electrons to be burnt. Do try to call people's attention to dubious changes in email...
>
>>>
>>> -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
>
> _______________________________________________
> Bismark-devel mailing list
> Bismark-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-devel
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [Bismark-devel] Bismark flash success! + 5 GHz radio issue
2011-04-20 22:14 ` Nick Feamster
@ 2011-04-20 22:24 ` Dave Taht
2011-04-20 22:25 ` Nick Feamster
0 siblings, 1 reply; 10+ messages in thread
From: Dave Taht @ 2011-04-20 22:24 UTC (permalink / raw)
To: bismark-devel
On 04/20/2011 04:14 PM, Nick Feamster wrote:
> Cool... I'll change instructions. Just wanted to run my experience by folks first (and for my own benefit, before I forgot :-)
On a wiki, it is always better to ask forgiveness than permission.
(and I note that only people that are registered on the website as
contributors or higher to this project have write access to the bismark
wiki)
You can "watch" certain pages...
And you can also passively subscribe to several RSS feeds, if you like
RSS feeds, to see changes go by.
I use sometimes rss2email to do that myself (this is better for blog
postings than this purpose, under Linux, for example, liferea is pretty
good. Here's how I keep track of all activities going on, after clicking
on the wiki edit checkbox on the activities page:
http://www.bufferbloat.net/projects/bismark/activity
http://www.bufferbloat.net/projects/bismark/activity.atom?key=fd2181feb4c417f4dd140e1a3e64a8f11e4de234&show_changesets=1&show_documents=1&show_files=1&show_issues=1&show_news=1&show_wiki_edits=1
You can filter down significantly as well.
For new issues, you can subscribe to various feeds (or I can add you to
the mailing list)
http://www.bufferbloat.net/projects/bloat/issues.atom
http://www.bufferbloat.net/projects/bismark/issues.atom
And so on.
Email is GREAT, as are searchable archives of email, but...
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bismark-devel] Bismark flash success! + 5 GHz radio issue
2011-04-20 22:24 ` Dave Taht
@ 2011-04-20 22:25 ` Nick Feamster
0 siblings, 0 replies; 10+ messages in thread
From: Nick Feamster @ 2011-04-20 22:25 UTC (permalink / raw)
To: Dave Taht; +Cc: bismark-devel
Thanks!
On Apr 20, 2011, at 6:24 PM, Dave Taht wrote:
> On 04/20/2011 04:14 PM, Nick Feamster wrote:
>> Cool... I'll change instructions. Just wanted to run my experience by folks first (and for my own benefit, before I forgot :-)
>
> On a wiki, it is always better to ask forgiveness than permission.
>
> (and I note that only people that are registered on the website as contributors or higher to this project have write access to the bismark wiki)
>
> You can "watch" certain pages...
>
> And you can also passively subscribe to several RSS feeds, if you like RSS feeds, to see changes go by.
>
> I use sometimes rss2email to do that myself (this is better for blog postings than this purpose, under Linux, for example, liferea is pretty good. Here's how I keep track of all activities going on, after clicking on the wiki edit checkbox on the activities page:
>
> http://www.bufferbloat.net/projects/bismark/activity
>
> http://www.bufferbloat.net/projects/bismark/activity.atom?key=fd2181feb4c417f4dd140e1a3e64a8f11e4de234&show_changesets=1&show_documents=1&show_files=1&show_issues=1&show_news=1&show_wiki_edits=1
>
> You can filter down significantly as well.
>
> For new issues, you can subscribe to various feeds (or I can add you to the mailing list)
>
> http://www.bufferbloat.net/projects/bloat/issues.atom
>
> http://www.bufferbloat.net/projects/bismark/issues.atom
>
> And so on.
>
> Email is GREAT, as are searchable archives of email, but...
> _______________________________________________
> Bismark-devel mailing list
> Bismark-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bismark-devel
^ permalink raw reply [flat|nested] 10+ messages in thread