some notes regarding actually USING this stuff

[Dave Taht]

So, as of tuesday, the bloody code finally started working on the cpe
emulator box (ida)
And of this morning, it started working on the actual cpe gear.

I am deeply uncomfortable delivering a demo that can't stay up all
day, without any serious testing, so in a fit of self inflicted QA,
I've been running myself behind sd-cpe2 all day.

Worst case, actually using the stuff will help you avoid pitfalls in
front of potential customers.

Things I've noticed that are different from my normal experience:

1) long term ssh connections time out fairly quickly by my standards

2) I can easily do bad things to the thing by starting my browser with
it's usual number of tabs (several dozen) open.

3) Doing stuff from multiple machines makes it worse, rapidly. I
basically assume that I'm rapidly running out of available ports and
they are in an unusable state (by design of tcp!!!) for 2 minutes(? 30
seconds?) before they can be reused.

4) Certain web sites have had problems with lots of links and/or javascript.

One confirmed problem is definately with *disquis*, which doesn't work
on anything I've tried it on.

Example sites (Which I think are mostly disquis enabled)

http://brizzled.clapper.org/blog/2012/02/18/a-case-for-coffeescript-in-the-browser/
http://twit.tv/show/security-now/345
http://www.reviewlinux.com/whats-new-in-linux-3-3-5039.html
http://www.windley.com/
http://politics.blogs.foxnews.com/2012/03/21/ron-bulldog-paul-foregoes-secret-service-welfare

This is a somewhat random selection from the 40+ tabs my browser has
in it that fail, and consistently fail, even after I've had the
network idle for longer than a few minutes.

Also things like youtube acted up (total video halts once in a while),
as well as fairly often things like google's interactive stuff would
get messed up or noticiably delayed (spellchecking for example)

-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net