Having read many of the posts relating to P2P and ways of effective management it seems that session limiting at the client is the best way.
Almost all P2P employs encryption so as to go undetected making packet sniffing and rules a waste of resources, especially at the AP or somewhere central where the damage has already been done.
Not everybody uses P2P but you can bet on any given wireless AP there will be more than one.
Why should user A who is downloading Debbie Does Dallas or something make user Bs telephone call to her cousin in Australia sound like a conversation between Daleks?
Giving highest priority to “normal” users who just want to browse the Internet, check their emails and make VoIP calls seems to be a bit of a Holy Grail.
In my opinion at least by limiting sessions during reasonable hours of the day these standard users will get a fighting chance of experiencing a quality service.
For every sophisticated technique introduced to combat P2P the developers will quickly release a work around and so a perpetual game of cat and mouse ensues while the wireless network grinds to a halt.
Limit in the day - open at night.
Seems simple but maybe this is the best way.
I’d love to hear what the pros on the forum think.
Maybe even the MT chaps could chip in?
There is a QoS setup that enables TCP/IP bursting, high priority for the first 2MB and low priority for the rest, works great. Set your system to identify SIP and give it higher priority and the the rest fall where they may.
Right now, my system is working great with or without P2P filtering. Even when I only had 1.5Mb and the pipe was saturated, my pings stayed relatively constant. If I could just get the trees to give priority to SIP, I’d be in great shape.
Search TCP bursting on the forum, if you can’t find it, I’ll post some info when I have more time.
Hi, I’ve had a look around for TCP bursting but cannot find out much information about it. If you have any further details it would be great if you could share.