Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] if you can't tell
Date: Thu, 14 Nov 2013 21:11:29 +0100	[thread overview]
Message-ID: <56478B0D-9DF1-4067-BDEB-ACEFE049CB60@gmx.de> (raw)
In-Reply-To: <CAA93jw7vWk7Eni+6aC4h6u8AEhgT32v-S6bO81DcuvvOU+H=Tg@mail.gmail.com>

Hi Dave,


On Nov 14, 2013, at 20:57 , Dave Taht <dave.taht@gmail.com> wrote:

> On Thu, Nov 14, 2013 at 11:36 AM, Richard E. Brown
> <richb.hanover@gmail.com> wrote:
>> Dave,
>> 
>> The flurry of comments on 3.10.18 that I posted were partially caused because I used sysupgrade (the first time ever! Previously, I had used tftp.) and I think some problems were caused because I kept the configuration. I’m looking for a bit of time to re-flash, this time not keeping the configs and running my config.sh script to set things up.
>> 
>> Rich
>> 
>> PS I don’t see a 3.10.19 posted on http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/ yet.
> 
> You guys are so eager to subject yourselves to new releases! take a
> weekend off! It's lovely in california right now…

	;) it happens to be cold wet and foggy in Germany, a really nice autumn as it should be in that part of the world, but I sure miss California (I always loved how the rain season made SoCal green again) 

> 
> I didn't see anything in 3.10.19 that is truly needed right now. there
> is some good work being done on fixing random number generation in the
> mainline, dnsmasq has an update, pie is 99.999999999% ready for
> mainline, but there's nothing I can do to push those faster...
> 
> and I am ashamed to admit that the big reason why I haven't dug in to
> fix sysupgrade was because I haven't cleaned up the yurt in a while.
> Somewhere in it is buried the bus pirate
> 
> http://dangerousprototypes.com/docs/Bus_Pirate
> 
> that I need to get to the serial port to get to see what the heck is
> going wrong at the command line. So I'm going to shovel out and reorg
> the place while the weather is good and hopefully that will show up.
> 
> I have a feature request for the aqm gui - in that many fields don't
> need to be exposed if the encapsulation is ethernet. I fear in making
> the dsl users happy we will confuse the others.

	Okay, unless more skilled hands take this over, I will have a go at this (most likely next week, as I expect visitors over the weekend). Interestingly are all options also valid for ethernet, so what about putting all those commands on a second tab that it easier to ignore? Anyway, I see what I can do...

> 
> What other open questions do we have?
> 
> Firewall rules good?
> minissd working?
> upnp working?

	I have not yet tested anything in particular, but then I see no problems either, so my (current) take is 3.11.18 is a keeper :)

Best Regards & enjoy the weekend
	Sebastian


> 
> 
> 
> -- 
> Dave Täht
> 
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel


  reply	other threads:[~2013-11-14 20:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 19:04 Dave Taht
2013-11-14 19:31 ` Sebastian Moeller
2013-11-14 19:36 ` Richard E. Brown
2013-11-14 19:57   ` Dave Taht
2013-11-14 20:11     ` Sebastian Moeller [this message]
2013-11-17 21:59     ` Sebastian Moeller
     [not found] <52852256.3010401@imap.cc>
2013-11-14 19:20 ` Fred Stratton
2013-11-14 19:21   ` Fred Stratton

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=56478B0D-9DF1-4067-BDEB-ACEFE049CB60@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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