All LANs share the same shaping queues?
-
I used the single-WAN / multi-LAN wizard to set up shaping queues. The wizard created the following which seems unexpected to me:
The three LAN interfaces are "Mytel_VOIP", "GuessWireless", and "LAN".
The WAN is just "WAN".I do not know why the wizard set up these three separate LAN interfaces to all share the same identical queue names. I can not change the shaping parameters of any one LAN interface without it affecting the other two. I did select all of them while doing the wizard.
We have a separate dedicated LAN interface port for all the phones. This is handled by a VLAN on the building switches.
Although I set the VOIP packet priority and P2P downrating in the wizard, these don't actually seem to be important.
All phone traffic is already isolated to the "Mytel_VOIP", so separate packet prioritizing seems unnecessary. and all I care about is setting that interface to the highest performance above all else.
The pfSense RRD logs for the "Mytel_VOIP" interface never exceed 50 kilobit, while our WAN is 93 megabit, so giving it top priority over all else should basically never affect anything else.
If an interface does not have a queue associated with it, is it automatically assigned a lower priority? Can I remove the shared shaping queues from "GuestWireless" and "LAN" so that they are just unconfigured?
-
Just to clarify a few things
- Interfaces don't have priorities
- All interfaces have at least one queue
- Priorities of queues are only relative to other queues on the same interface, but not queues on another interface.
- Traffic shaping only affects egress, which means you can shape traffic leaving your WAN and traffic leaving your LAN, but not traffic coming to your LAN.
I don't have time right now for a better response.
-
- Traffic shaping only affects egress, which means you can shape traffic leaving your WAN and traffic leaving your LAN, but not traffic coming to your LAN.
MMh… is this really true? What about the limiter with in/out field in advanced options in firewall rules? These are not supposed to limit bandwith for inbound and outbound?
Thanks
-
- Traffic shaping only affects egress, which means you can shape traffic leaving your WAN and traffic leaving your LAN, but not traffic coming to your LAN.
MMh… is this really true? What about the limiter with in/out field in advanced options in firewall rules? These are not supposed to limit bandwith for inbound and outbound?
Thanks
'Tis true. You can only fully control what you send.
You can only request that a sender modify his sending rate (TCP), and this is not immediately obeyed. With UDP, you have literally no control over the rate a sender transmits at.
My favorite analogy is the Postal Service. You can control what you send, when to send, and how often you send it, but you have very little (or zero) control over when you will receive replies.
-
Unless you're running a VoIP call center, rate limiting UDP is not an issue. Except for BitTorrent, then UDP is sensitive to to rate limiting and will function similarly to TCP.