I don't think I pushed out the 6in4 patch into the build. Hell, I
forgot to tag it too. Remind me to take a vacation next vacation?
If these patches aren't in your build, it looks like we are indeed
only using one class for fq_codel 6in4 traffic and thus are reverting
to nearly pure codel
ok, 3.8.13-7 committed, tagged, and pushed. Sorry about that...
If you could redo that test with simplest.qos or with the
rrul_noclassification test, it would be interesting, then with the
patches, again...
TIA.
On Sun, Jun 16, 2013 at 12:13 PM, Dave Taht dave.t...@gmail.com wrote:
I don't
You have this huge latency spike late in your test... (?)
On Sun, Jun 16, 2013 at 11:56 AM, Toke Høiland-Jørgensen t...@toke.dk wrote:
Dave Taht dave.t...@gmail.com writes:
I am curious: Is there a current user of cero using simplest.qos,
tunneling ipv6 via hurricane or 6to4, that can hammer
simplest.qos would be less noisy. ;)
On Sun, Jun 16, 2013 at 12:21 PM, Toke Høiland-Jørgensen t...@toke.dk wrote:
Dave Taht dave.t...@gmail.com writes:
I might be getting good at reading the patterns here - it looks like
this is fq_codel rather than nfq_codel?
It is.
ns2_codel is tighter
Dave Taht dave.t...@gmail.com writes:
You have this huge latency spike late in your test... (?)
Yeah, not sure why. I must add that this is with other traffic running
in the background, though.
-Toke
signature.asc
Description: PGP signature
___
Dave Taht dave.t...@gmail.com writes:
Well, that result is mildly puzzling. netperf-wrapper -6 throughout?
no ipv4?
There's some ipv4 traffic in the background. Dunno exactly how much.
You are on a dsl line, too? There has been some fixes to the overhead
issue that have landed but
Toke Høiland-Jørgensen t...@toke.dk writes:
There's some ipv4 traffic in the background. Dunno exactly how much.
Seems there's some torrenting going on. Will re-run the tests at some
time where the network is quiet (or where I won't have to disturb my
roommates to make it so). :)
-Toke
I have been gradually sorting through the mess of change introduced to
sch_htb since the set of patches that broke it... it seems to be
getting better (aside from atm encapsulation) but it also looks like
more patches than just these are required for a backport to 3.8.13
Hi Toke,
On Jun 16, 2013, at 21:36 , Toke Høiland-Jørgensen t...@toke.dk wrote:
Dave Taht dave.t...@gmail.com writes:
Well, that result is mildly puzzling. netperf-wrapper -6 throughout?
no ipv4?
There's some ipv4 traffic in the background. Dunno exactly how much.
You are on a dsl
On Sun, Jun 16, 2013 at 1:55 PM, Toke Høiland-Jørgensen t...@toke.dk wrote:
Sebastian Moeller moell...@gmx.de writes:
As far as I can tell at least VDSL typically means VDSL2 and that
probably means PTM instead of ATM. In essence this means you do not
have to deal with ATMs 48 payload bytes
There is a lot of interesting work coming up on babel, and I've not
got around to trying to merge the homenet work into quagga. I am
thinking of switching back (at least temporarily) to the standalone
babeld daemon rather than quagga-babeld to test out the algorithms
there. Any objections?
--
In my modified pie a rounding error is introduced with the HZ values
cerowrt uses (I think it's 250, but would have to check)
target=20 becomes target=23
target=10 becomes target=11
I still haven't got around to checking the code against the paper,
which I'll start doing this week.
root@CMTS:
In looking over the htb mess, I noticed that htb has an internal pfifo
queue, which is controllable via new stuff in net-next.
http://snapon.lab.bufferbloat.net/~cero2/htb_mess/11256-htb-add-HTB_DIRECT_QLEN-attribute.patch
I have no idea what, if anything, it affects. I was under the
impression,
Dave Taht dave.t...@gmail.com writes:
There is a lot of interesting work coming up on babel, and I've not
got around to trying to merge the homenet work into quagga. I am
thinking of switching back (at least temporarily) to the standalone
babeld daemon rather than quagga-babeld to test out
Dave Taht dave.t...@gmail.com writes:
Hmm. Does this mean you have 6in4 working correctly in your build of
cero? I'm still just doing it with a script, not netifd.
Yeah. I have this in /etc/config/network:
config interface sixxs
option 'proto' '6in4'
option 'ifname' 'sixxs'
Folks,
I installed 3.8.13-7 on my WNDR3800. I used TFTP, not the default web GUI to
upload the firmware. (Note - the recommendation is now to use the web GUI.)
I then ran two installation scripts to complete the custom configuration (see
these pages for passwords, time zones, SSIDs, and also
On Sun, Jun 16, 2013 at 3:29 PM, Toke Høiland-Jørgensen t...@toke.dk wrote:
Rich Brown richb.hano...@gmail.com writes:
As noted above, 6in4 addresses seem to work, however, I did see a lot
of error messages as a result of running the 6in4 tunnel configuration
script. I've attached it to see
I had a chance to test out the raspberri pi and beaglebone black over
the past week.
the raspberry is really well supported out there, but the beaglebone
black is capable of easily saturating its
100Mbit ethernet link where the raspberry peaks out at about 75Mbit.
Both have os's with fq_codel
Toke,
Warning: Option @defaults[0].synflood_rate has invalid value '200'
This is because the value is wrong. It should be '200/s' and not '200'.
That's a bug, I believe (though a minor one). Fixed in git; you can
manually add the /s in your /etc/config/firewall if you want to shut it
up.
The table numbers are generated sequientally for each logical interface in
/etc/config/network starting with 1001. You can override them by setting e.g.:
option ip6table 1234 in that interface (e.g. the tunnel).
Cheers,
Steven
Toke Høiland-Jørgensen t...@toke.dk schrieb:
Dave Taht
20 matches
Mail list logo
