This sounds quite a bit like what I've been trying to do regarding IM clients. The solution, if you're trying to shape P2P traffic anyway, would probably best be solved by the layer7 filter and some appropriate tc rules. http://l7-filter.sourceforge.net But if you're trying to block them altogether, then you've just opted yourself into the 'Find a way to block layer 7 packets with tc' club. We don't have many members, and we haven't even come close to attaining the goal, but the picnics are fun. The card problem is definately a fun one, although in my experience linux assigns iface names in the following fashion: PCI (from top (closest to AGP/CPU) to bottom), then Onboard. so usually I just play around with the order of the cards, although I'm sure theres a better way to do it. The networking HOWTO and appropriate mailing lists located here: https://secure.linuxports.com/ will probably help a bit, too. Hope it helps, Derek On Friday 26 September 2003 04:01 pm, Jacek Bilski wrote: > Hello! > > I've read this list for almost one month, learnt a lot, solved some of > my problems, time to ask. > > I've set up traffic control using iptables with CONNMARK extension, IMQ > and HTB. Works quite well for now, but doesn't recognize P2P. I tried to > base selecting this traffic on src/dst ports to no effect. Is there any > simple way to detect such traffic? I thought of stringmatch extension > for iptables, but I don't know what to look for. Any suggestions? I'd > prefer to have those connections marked for future `tc filter ... handle > 54 fw classid 1:154`. > > And off-topic, but I know some of you can help. I have two 3c905 card in > my Linux box. How can I tell 3c59x module, that card on IRQ9 should be > eth0 ant that on IRQ11 eth1? Now I have it the other way. > > Greetings _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
