Problem with Qos and P2P traffic

sideout · Jun 4, 2014, 12:46 PM

From what I understand about PRIQ you can have the same thing happen as a higher priority queue gets processes ahead of a lower priority queue. So if your higher priority queues are always full then the packets for the lower queues get dropped.

I would be interested in seeing how you have the queues setup with PRIQ.

KOM · Jun 4, 2014, 1:28 PM

Yes, PRIQ can be harsh to lower queues, but unless you've got a link that's saturated much of the time and you don't need to guarantee a minimum service level for the low queues, it shouldn't be a problem in reality. In my config, I have only a few queues: VoIP is top (7), ACK next (6), HTTP/S, DNS and RTSP next (4), everything else last (3). I have a low queue configured with a limiter, but I don't use it. Having a default queue handle non-classified traffic is good enough for my needs at the moment.

rtpmomo · Jun 4, 2014, 2:37 PM

I've tried with PRIQ, but same as before :(

The detection of the traffic type works just fine with HFSC and PRIQ

I've got LAN Side:

1% P2P
61% HTTP
20% ACK
4% Voip
4% Games
10% Other

In this configuration when there is only P2P, they get all the BW -> perfectly normal
But when there is P2P and HTTP, p2p still get all the BW if there is lot of connections(HFSC and PRIQ)

BW download: 5000kbit/s

sideout · Jun 4, 2014, 2:56 PM

You could try setting a limiter for TCP traffic coming from your LAN similar to https://forum.pfsense.org/index.php?topic=63531.0

I did this in my setup and it does work. Does it limit all TCP streams , yes it does but at least it gets you a starting point to limit bandwidth and not let torrent's take it all.

rtpmomo · Jun 4, 2014, 3:11 PM

But the problem is, I want the torrent to have full BW when there is no other DL.

The p2p traffic get drop a little, but still get all BW. Maybe it's impossible to do that?

sideout · Jun 4, 2014, 3:22 PM

Why are you applying the floating rule to the LAN interface? From what I understand of floating rules you dont want to apply them there.

rtpmomo · Jun 4, 2014, 3:31 PM

To match the download traffic. I've got only 5Mbit/s.

I use pfsense for home usage that way:
internet->modem->pfsense->lan

The Upperlimit from HFSC Service Curve works fine.. i don't now why the bandwidth share doesn't.

sideout · Jun 4, 2014, 3:45 PM

I understand that you only have 5Mbit of download but for Floating rules I think you want to select the WAN interface not the LAN. Maybe try that and see if it makes a difference?

rtpmomo · Jun 4, 2014, 4:30 PM

Because the WAN side have no LAN ip address, i need to match a LAN ip address and not port. The only way is to put the floating rule on the LAN side.

sideout · Jun 4, 2014, 4:48 PM

You dont have the quick option checked on the rules. Have you done that? If you do not have that option checked it still processes the rest of the rules.

rtpmomo · Jun 4, 2014, 5:25 PM

I've try but nothing change.

sideout · Jun 4, 2014, 6:11 PM

sorry i can't be of more help. I dont worry about P2P in my setup as I have the limiter defining a hard set bandwidth that all TCP streams share equally. I dont care if it is P2P or straight HTTP download , they only get x% of the bandwidth to share among all the clients requesting it.

I would search this forum and others to see what other people have tried.

KOM · Jun 4, 2014, 6:16 PM

Are you really on 2.1? You might want to consider upgrading to current. No use wasting time trying to work with a bug that may have already been fixed.

I also noticed that you have drops on your P2P queue but not many others. This shows me that your other queues are getting higher priority as expected. Sideout is right in that your floating rules shouldn't target a particular interface. That's what makes them floating rules.

Did you go through the wizard or did you build your queues manually?

rtpmomo · Jun 4, 2014, 7:10 PM

Thanks sideout for your help!

I've this version:
2.1.2-RELEASE (amd64)
built on Thu Apr 10 05:42:41 EDT 2014

I create the rules via the wizard then change manually some speed settings.

sideout · Jun 4, 2014, 7:14 PM

I am on 2.1.3 built on May 10th.

rtpmomo · Jun 4, 2014, 7:28 PM

I will try to do it again via the wizard and see what append.

KOM · Jun 4, 2014, 7:42 PM

Make sure you delete any rules you manually added to WAN, LAN or Floating Rules tabs since they won't get removed when you remove your traffic shaper.

rtpmomo · Jun 4, 2014, 9:37 PM

I've follow the wizzard and delete custum floating rules, wan, lan

add 2 floating rules to catch IP from the p2p computer(Interface LAN dest: IP and Interface LAN source: IP)(The computer as a Port forward) With WAN interface enable, no traffic is catch
qOtherHigh 60%
qP2P 2%
etc..

Result: Packets get drops as before, but not enough.

I think the problem is how to match floating rules with LAN IP address instead of ports

cheonne · Jun 5, 2014, 5:35 AM

is the lan address 192.168.0.210 of a particular PC set to static ip?
if not then did you set static ip+mac address in dhcp server?

rtpmomo · Jun 5, 2014, 5:39 PM

The PC is set with an static IP address

This guy have exactely the same problem.
Maybe it's just a bug..
https://forum.pfsense.org/index.php?topic=73570.msg401784#msg401784

openSUSE-13.1 torrent and ubuntu 14.04 HTTP dl

no http dl, torrent 5 connexion: full speed

5 connexion: no problem the torrent get drop to almost no speed 10-20ko/s
10 connexion : 140ko/s
15 connexion : 230ko/s
20 connexion: almost full speed

The traffic shapper need to drop the speed to 10-20ko/s even with 1000 connexion on the p2p queue