On Friday 14 May 2004 13:26, Andreas Klauer wrote: > Am Friday 14 May 2004 17:18 schrieb GoMi: > > I am network administrator for my university dorm. We are about 300 > > users, and we have 2 ADSL connections doing load balancing with 300kbits > > upstream and 2Mbit downstream. > > That's not much bandwidth if there are a lot of p2p users. Indeed. > > and with ipp2p I mark p2p traffic allocating it under the > > non-interactive queue. > > That's good - but you didn't write anything about your setup. > Make sure that p2p traffic is in a class that gets restricted > aggressively. If you're using HTB, the P2P class should have > to borrow everything and have lower ceil and prio than other classes. Precisely. I have mine limited to 8kbit on a 256kbit connection. The HTB manual mentions some interesting results[1] when you mess with prio, though. (I just lowered the ceil for my p2p bulk class to 16kbit less than my max, 192kbit, and I'm experiencing a significant decrease in lag. Thanks Andreas!) [1] http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm#prio When using IPP2P[2] with 2.4.24 I found that, at least with the edonkey2000 network, it frequently missed enough packets to kill interactivity on my link. Packets that should not have were finding their way into the class for TCP ACKs and ICMP and into the default class, indicating packets were being missed. I was using CONNMARK was suggested to maintain state on which connections were edonkey2000. I upgraded to 2.6.6 last night and patched my kernel and IPTables with L7-Filter[3]. I'm using the edonkey2000 layer 7 match and it's proving to be extremely effective, even with the Overnet protocol for edonkey2000 enabled which is when I started having problems with IPP2P[2]. A quick snippet of the pattern match[4] for edonkey2000 from L7 indicates just how nasty the match is, and why IPP2P[2] might be missing some packets: rebecca:~# cat /etc/l7-protocols/edonkey.pat ... ^[\xe3\xc5\xe5\xd4].?.?.?.? \ ([\x01\x02\x05\x14\x15\x16\x18\x19\x1a\x1b\x1c\x20\x21\x32\x33\x34 \ \x35\x46\x38\x40\x41\x42\x43\x46\x47\x48\x49\x4a\x4b\x4c\x4d\x4e\x4f \ \x50\x51\x52\x53\x54\x55\x56\x57\x58\x5b\x5c\x60\x81\x82\x90\x91\x93 \ \x96\x97\x98\x99\x9a\x9b\x9c\x9e\xa0\xa1\xa2\xa3\xa4]| \ \x59................?[ -~]|\x96....$) ... #ipp2p essentially uses "\xe3....\x47", which doesn't seem at all right to me. ... EOF [2] http://rnvs.informatik.uni-leipzig.de/ipp2p/index_en.html [3] http://l7-filter.sourceforge.net/ [4] http://sourceforge.net/project/showfiles.php?\ group_id=80085&package_id=81756 <snip> > Andreas _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
