From SourceForge - the mother-of-all-L7-rules: http://l7-filter.sourceforge.net/protocols
The fix I wrote below works nicely because it keeps the Skype queue clean of P2P traffic. I don't know if the P2P stuff is intentionally trying to masquerade it's traffic as Skype, but the bottom line is it was getting tagged by the L7 regex tests as Skype traffic when it wasn't. The good news is there was enough telltale P2P activity which was positively getting flagged as P2P to show me without a doubt who's the offender. In a perfect world the traffic would be identified and queued perfectly. The the real world it's not but a perfect solution is to not give the P2Pers access to the Skype queue, which keeps their P2P traffic out of that high priority queue. There's also some penalty there for the P2Pers, their Skype isn't going to work as good. It's win-win as I see it. Greg On Sep 14, 2011, at 3:47 PM, Josh Luthman wrote: > If the p2p is acting like Skype traffic there is nothing you can do. If the > two protocols are getting similar, a finer Skype match will work. If Skype > changed their methodology then you'll need to come up with a layer 7 rule. > > Where did you get the rules you have now? > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > > On Wed, Sep 14, 2011 at 4:11 PM, Greg Ihnen <[email protected]> wrote: > Yeah, on the high latency, high jitter low bandwidth connection we have here > the prioritization and bandwidth limiting of the various protocols and kinds > of traffic makes all the difference between Skype being unusable to being > almost perfect. > > On a side now, I had to downgrade from ROS 5.6 to 4.17 because the log was > full of error relating to the L7 processing. There's a thread over on the MT > forum. > > Greg > On Sep 14, 2011, at 3:05 PM, Josh Luthman wrote: > >> >MT's L7 Skype regex >> >> The rules inside of this monster? >> >> http://wiki.mikrotik.com/wiki/Basic_traffic_shaping_based_on_layer-7_protocols >> >> Do you have to prioritize Skype? >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> >> On Wed, Sep 14, 2011 at 3:28 PM, Greg Ihnen <[email protected]> wrote: >> Guys, >> >> I've gotten so much out of these forums. I appreciate you letting me >> be a part of them. I had an idea which I don't know if it would be of >> interest to anyone here but I hope it is. It has to do with bandwidth >> management and P2P and Skype and their interaction in MT's RouterOS. >> >> I've noticed some P2P traffic gets picked up by the L7 regex for >> Skype. Since anyone doing bandwidth management for both Skype and P2P is >> probably trying to prioritize Skype and de-prioritize P2P and MT's confusing >> the two is going to have negative consequences. Having the P2P traffic get >> into Skype's queue does the exact opposite of what I'm trying to do. >> >> You'll see when MT's L7 Skype regex is misidentifying P2P traffic as >> Skype traffic is the inbound and outbound traffic will be greatly >> unbalanced, much more so than even if one side was doing voice and video and >> the other side was just doing voice. I was seeing hundreds of Kbps down and >> one or two Kbps up on the Skype queues. I knew that wasn't right. I looked >> and sure enough there was bit torrent activity going on. I wonder if some of >> these bit torrent clients don't try to make their traffic appear to be >> traffic of legit apps. >> >> I'm using a modified version of Butch's script. What I'm doing with >> regard to Skype and P2P to correct this problem is the part of the script >> that detects P2P traffic keeps a list of the local users's IPs. I have the >> part of the script that prioritizes Skype ignore the user's traffic if >> they're one of the P2P'ers. That means not only does their P2P work poorly >> but their Skyping is not going to be as good as it would if they weren't >> messing around with P2P. I'm very heavily trying to discourage P2P here. >> >> Greg >> ----------------------------------------------- >> Wireless Users Group [email protected] >> >> >> >> >> -------------------------------------------------------------------------------- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> -------------------------------------------------------------------------------- >> >> WISPA Wireless List: [email protected] >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/
-------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
