-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Folks,

I've got an ADSL connection and for the past few months
have been working out an ALTQ  (well pf.conf) config to
allow me to manage my upstream b/w. Sometimes the behaviour
I'm seeing doesn't jibe with how I'd expect it to work and
I'm wondering if this is something specific to my config
versus the rest of the pf universe.

I should really be asking this question on the FreeBSD
list since I'm using Max Laier's port of altq/pf, but
what I'd also like to determine is if perhaps that port
is broken in some fundamental way ..

So here goes ...

Here's what I have today, that looks to be working well -


altq on $ext_if cbq bandwidth 100Mb queue { output_ext }
queue output_ext bandwidth 850Kb cbq { std_ext,  known_ext, torrent_ext, 
tcp_ack_ext }
queue std_ext     bandwidth 75%  priority 1 cbq(default red) qlimit 100
queue torrent_ext bandwidth 75%  priority 1 cbq(red) qlimit 1
queue known_ext   bandwidth 90% priority  3 cbq(borrow) qlimit 100
queue tcp_ack_ext bandwidth 10% priority  7 cbq(borrow) qlimit 100


Notice the percentages don't add up ?

I *thought* I should be doing something like -

altq on $ext_if cbq bandwidth 100Mb queue { output_ext }
queue output_ext bandwidth 850Kb cbq { std_ext,  known_ext, torrent_ext, 
tcp_ack_ext }
queue std_ext     bandwidth 5%  priority 1 cbq(default red borrow) qlimit 100
queue torrent_ext bandwidth 5%  priority 1 cbq(red borrow) qlimit 1
queue known_ext   bandwidth 80% priority  3 cbq(borrow) qlimit 100
queue tcp_ack_ext bandwidth 10% priority  7 cbq(borrow) qlimit 100

But with this config torrent uploads *crawl*, at most using 6 or 7 % of the 
available
bandwidth - lots of dropped packets are preventing tcp from ramping up the 
connection
speed, this regardless of whether or not the bw is being used by the other 
queues.

I've tried various combinations and permutations with ecn and it doesn't appear 
to
make a whole of difference.


So, which of these two configs looks more correct ?  If it's the second one, 
then
it might mean there's some kind of bug in the FreeBSD port. If it's the first 
then
the examples I've found on openbsd.org might be misleading ....

As I noted at the beginning, I've been 'tuning' altq/pf for months and have 
lots of
empirical data.

Andrew.
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD6j3C8It2CaCdeMwRAgujAJ9t5O44PYBwmuToH1S1QAdSivwL0ACfVO25
b/Nx3+204yVDup5fpJl2FRw=
=29kX
-----END PGP SIGNATURE-----

Reply via email to