Sniffing out Bittorrent and Skype traffic in Squid.

2 posts / 0 new
Last post
#1 Fri, 01/29/2010 - 16:55

Sniffing out Bittorrent and Skype traffic in Squid.

I'm trying to set up delay pools for certain traffic; the two that I have not been able to crack are Bittorent and Skype.

I've hunted and hunted through forums etc and the best I have found (well, I think it's the best) are the following ...

acl bit_torrent req_mime_type application/x-bittorent acl bit_torrent req_mime_type ^application/x-bittorent$


acl numeric_IPs URL Regexp ^(([0-9]+.[0-9]+.[0-9]+.[0-9]+)|([([0-9af]+)?:([0-9af:]+)?:([0-9af]+)?])):443 acl Skype_UA Browser Regexp ^skype^

but no matter how hard I try I can not get these understood. My typical lines for a delay pool are ...

delay_access 1 allow numeric_IPs delay_access 1 allow Skype_UA delay_access 1 deny all

Can anyone point me in the correct direction when it comes to my dilemma.

Many Thanks - Nigel.

p.s. Don't forget to sign the "Keep MySQL - GPL compliant"

Wed, 02/10/2010 - 00:45
Joe's picture

While Squid isn't really on-topic here, I do happen to have some experience in the area (I was one of the developers for several years)...

Bittorrent and Skype are not HTTP protocol traffic. Squid is an HTTP proxy. Nothing you do in Squid is going to effect these protocols, unless the Bittorrent and Skype clients are capable of, and are explicitly configured to use an HTTP proxy.

The Linux network stack does have the ability to shape traffic, so you might consider going that's not as powerful/flexible as delay pools in Squid, but it does work with protocols other than HTTP.


Check out the forum guidelines!

Topic locked