Hi Luman, Sorry, I have a stupid question - why do you wish to mark the traffic, is it because you wish to allow it internally or is it because you wish to completely drop it? If you wish to mark it, then I can recommend that you take a look at the patch-o-matic module connmark. All packets destined for your internal services or external services where the destination port is above 1024 can then easily be marked and tracked (at least in theory, I haven't played with the connmark module yet). /Kim On Tuesday 25 March 2003 09:08, Luman wrote: > Probably, I'm not the first one who needs solve problem with p2p. > Because, large part of my traffic is eaten by p2p software like KazAA, > e-mule, Direct Connect etc, I'm looking for the way of detection of such > traffic and marking it. However simple way with for instance 1214 port > for KazAA doesn't work because this software uses floating port > technology. This traffic can be send via different ports and these ports > can change in the fly. This is rather well known. > So I'm looking for the stuff working at higher level and analyzing > traffic inside to determine the content and the real protocol. It could > be a patch to the kernel or whatever. It should only be able to mark > packet by a special marker. > > I need this solution not only to prioritizing the traffic (prioritizing > can be achieve in other way) but also to selection the Internet link. I > want to NAT this low quality data for some specific address in order to > send it over cheaper link. > > What do you think is there any solution to do it? Or maybe there is > ongoing project trying to tackle with this global problem with detection > p2p traffic. > > Best regards, > Luman > > > > > _______________________________________________ > LARTC mailing list / LARTC@xxxxxxxxxxxxxxx > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
