Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-3.7.3-2 released
Date: Mon, 21 Jan 2013 16:47:39 -0500 (EST)	[thread overview]
Message-ID: <1358804859.167924837@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw7uG_2-JvOkv1t3MubdsAqeSpLQ8JuoS_KiOmcjXC6JiA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2008 bytes --]


How random do you need things to be?   Security needs true randomness, but there is nothing else I know of where you need "entropy" sources to achieve sufficient unpredictability to meet the need of some algorithm.  A simple pseudo-random sequence is good enough.
 
-----Original Message-----
From: "Dave Taht" <dave.taht@gmail.com>
Sent: Monday, January 21, 2013 2:47pm
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] cerowrt-3.7.3-2 released



And is at:

[http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.7.3-2] http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.7.3-2

+ resync with openwrt
+ uftp4 alpha 
+ quagga update
 + Hopefully the last ipv6 instruction traps killed (thx ketan and robert!)
- I see rngd eating a ton of cpu on a given transfer. I'd been meaning to look at the quality of the new entropy stuff for ages, and have long hoped to be rid of that daemon

After we do a bit more testing I'll tag and push the source to this version, and then get cracking on higher layers in the stack again.

A bit about uftp4 support. My intent with getting uftp into cerowrt 18 months ago was to have an easy multicast test, which would let someone (for example) set a rate of 1Mbit and observe what happens to a wireless network, observe packet loss at various distances from the AP, etc, as well as get a grip on the timing delays induced by the power save mode in wifi (basically storing all multicast content and broadcasting it as "content after beacon", (CAP, also known colloquially as "crap after beacon"))...

Anyway, while I was thinking that as my basic use case in this project... 

Dennis Bush was actually off making a new version do more useful things. We got to talking last week... I've tried the ipv4 support and it's nifty. Ipv6 didn't work but perhaps my x86 build is bad.

-- 
Dave Täht

Fixing bufferbloat with cerowrt: [http://www.teklibre.com/cerowrt/subscribe.html] http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 2404 bytes --]

  reply	other threads:[~2013-01-21 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 19:47 Dave Taht
2013-01-21 21:47 ` dpreed [this message]
2013-01-26 10:57   ` Maciej Soltysiak

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=1358804859.167924837@apps.rackspace.com \
    --to=dpreed@reed.com \
    --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