QoS on pfSense 2.3.2 64 bit

sideout

No its not correct. You have to have a value under Queue. You need to create Queues then you match traffic to the queue by the floating rules.

For UDP traffic you do not assign the ACK queue . For TCP and TCP/UDP traffic you will assign an ACK queue.

PASS rule do not need a queue and do not allow you shape unless you are using a limiter.

KOM clearly gave you instructions on how to do this in previous posts. if you run the Traffic Shaper wizard and answer the questions ,fill in values , it will create queues for you.

balubeto

@sideout:

No its not correct. You have to have a value under Queue. You need to create Queues then you match traffic to the queue by the floating rules.

For UDP traffic you do not assign the ACK queue . For TCP and TCP/UDP traffic you will assign an ACK queue.

PASS rule do not need a queue and do not allow you shape unless you are using a limiter.

KOM clearly gave you instructions on how to do this in previous posts. if you run the Traffic Shaper wizard and answer the questions ,fill in values , it will create queues for you.

I run the Dedicated Links wizard to configure the Traffic Shaper and I left all options with the default values. This wizard has created these rules:

Now, what should I do?

Thanks

Bye

KOM

Now, what should I do?

Delete it all and run the correct wizard, the Multiple LAN/WAN wizard.

balubeto

@KOM:

Now, what should I do?

Delete it all and run the correct wizard, the Multiple LAN/WAN wizard.

I run the Multiple Lan/Wan wizard to configure the Traffic Shaper and I left all options with the default values. This wizard has created these rules:

Now, what should I do?

Thanks

Bye

KOM

Now, what should I do?

What you should do now is examine the rules and the queues to wrap your brain around how it all works. Then you can create your own rules that do what you want.

balubeto

@KOM:

Now, what should I do?

What you should do now is examine the rules and the queues to wrap your brain around how it all works. Then you can create your own rules that do what you want.

So, what did I do wrong?

Thanks

Bye

KOM

So, what did I do wrong?

Everything. You just don't seem to understand. The wizard has already defined your queues. Now you just need floating rules to manage your traffic. Anything going to the TV gets top priority. Anything coming from the TV gets top priority. Here is what you want:

Protocol Source Port Destination Port Gateway Queue
IPv4 * * * SmartTVs * * qACK/qOthersHigh
IPv4 * SmartTVs * * * * qACK/qOthersHigh

balubeto

@KOM:

So, what did I do wrong?

Everything. You just don't seem to understand. The wizard has already defined your queues. Now you just need floating rules to manage your traffic. Anything going to the TV gets top priority. Anything coming from the TV gets top priority. Here is what you want:

Protocol Source Port Destination Port Gateway Queue
IPv4 * * * SmartTVs * * qACK/qOthersHigh
IPv4 * SmartTVs * * * * qACK/qOthersHigh

Now, these rules are right?

The first rule is to give priority to all packets that from the WAN go to Smart TVs.

While, the second rule is to give priority to all packets on the LAN that from the Smart TVs go to the WAN.

Correct?

Thanks

Bye

KOM

Close. Do your shaping on WAN. The rate that data leaves the WAN is directly linked to the data that comes back in, so the key to shaping is to control what goes out so that you can deal with the return traffic. Traffic already at your WAN can't be shaped as it is too late by that point. Once you have changed your rule to use the WAN interface both ways, then you can try it out. Go to Status - Queues and watch your queues in realtime. Turn your TV on and watch to see if qOthersHigh starts getting packets. Make sure that queue has no drops.

balubeto

@KOM:

Close. Do your shaping on WAN. The rate that data leaves the WAN is directly linked to the data that comes back in, so the key to shaping is to control what goes out so that you can deal with the return traffic. Traffic already at your WAN can't be shaped as it is too late by that point. Once you have changed your rule to use the WAN interface both ways, then you can try it out. Go to Status - Queues and watch your queues in realtime. Turn your TV on and watch to see if qOthersHigh starts getting packets. Make sure that queue has no drops.

Sorry again but I can not understand what I should change.

So what's this small change?

Thanks

Bye

KOM

Change your second rule so that the Interface is WAN, not LAN.