Newbie needs help about traffic shaping
-
Hello,
I've been trying to correctly setup traffic shaping. I've read pages both on the forum and on the wiki, but I've still questions about it. Unfortunately, sticky topics in this section didn't help me much. I wouldn't write this topic if all users promised to write a tutorial, would have do it. I hope my questions and your answers will be useful for all newbies.
My network has the following configuration:Asymmetric DSL Connection
|
PPPoE
|
WAN
|
pfSense
| | |
| | +- OPT1
| |
| +–-- LAN
|
+------ WIFI (hostap)My aims by using traffic shaping are:
- P2P programs don't monopolize traffic, they get a low priority
- keep a good experience while surfing on the web (no annoying delay during webpages loading)
- keep VoIP phone attached to an ATA working fine even if there is an high load
I've confused ideas about some features/limits of the current implementation of the traffic shaper implemented in the 1.2 release:
1- is it possible to limit upload/download speed on a specific IP which use WIFI (hostap) interface (note that wifi interface is bridged to LAN and doesn't use DHCP)?
2- ermal in a topic said that it is better not to use parent queues. Is it true for pfSense 1.2 or 1.3?
3- do you advice to use traffic shaper wizard or you setup traffic shaper on another way?
4- are there side-effects if queue length are increased? I've noticed there are less drops when default setting (50) is increased manually in the xml config.
5- What and how settings did you tune in the config produced by the shaper wizard?
6- I read about "IP Type of Service (TOS)" in rule's page. What is the decimal value of low delay? I need to write it in the setup page of the VOIP ATA ("Type of Service: Indicate SIP and RTP packets values").I've already tried to use the traffic shaper wizard in the 1.2RC4, but I didn't get the expected performance from the traffic shaper, because I notice that Firefox stuck at "Waiting for <sitename>…" for several seconds, instead it should be faster in my opinion. I gave 40% to qwanACKS, but I think I have to reflash the CF and load the fresh 1.2 release, but I need your help/advice, otherwise I risk to waste time again.
Thank you in advance! ;)</sitename>
-
Hello,
I've been trying to correctly setup traffic shaping. I've read pages both on the forum and on the wiki, but I've still questions about it. Unfortunately, sticky topics in this section didn't help me much. I wouldn't write this topic if all users promised to write a tutorial, would have do it. I hope my questions and your answers will be useful for all newbies.
My network has the following configuration:Asymmetric DSL Connection
|
PPPoE
|
WAN
|
pfSense
| | |
| | +- OPT1
| |
| +–-- LAN
|
+------ WIFI (hostap)My aims by using traffic shaping are:
- P2P programs don't monopolize traffic, they get a low priority
- keep a good experience while surfing on the web (no annoying delay during webpages loading)
- keep VoIP phone attached to an ATA working fine even if there is an high load
Doable even in 1.2 for 2 interfaces.
I've confused ideas about some features/limits of the current implementation of the traffic shaper implemented in the 1.2 release:
1- is it possible to limit upload/download speed on a specific IP which use WIFI (hostap) interface (note that wifi interface is bridged to LAN and doesn't use DHCP)?
you can do these through upperlimit settings. Though you can not shape WIFI even in bridge mode since you need to filter/shape on bridge interface and am not sure if you can do that on 1.2.
2- ermal in a topic said that it is better not to use parent queues. Is it true for pfSense 1.2 or 1.3?
true for every version of pfSense.
3- do you advice to use traffic shaper wizard or you setup traffic shaper on another way?
start with the wizard and move on to the specialized config.
Though the wizard is toward home users mostly and does not produce the correct results for true seemles VoIP session. You need to remove its realtime settings from all other than VoIP queue.4- are there side-effects if queue length are increased? I've noticed there are less drops when default setting (50) is increased manually in the xml config.
With this paramter yuo are sacrificing latency with drops most of the time but not only.
5- What and how settings did you tune in the config produced by the shaper wizard?
6- I read about "IP Type of Service (TOS)" in rule's page. What is the decimal value of low delay? I need to write it in the setup page of the VOIP ATA ("Type of Service: Indicate SIP and RTP packets values").Search google. But you need DSCP which is on 1.3
I've already tried to use the traffic shaper wizard in the 1.2RC4, but I didn't get the expected performance from the traffic shaper, because I notice that Firefox stuck at "Waiting for <sitename>…" for several seconds, instead it should be faster in my opinion. I gave 40% to qwanACKS, but I think I have to reflash the CF and load the fresh 1.2 release, but I need your help/advice, otherwise I risk to waste time again.</sitename>
The best way for this if you cannot categorize traffic propperly, as in p2p going on http protocol, the best way is to go with bursts. Search the forum on how to configure it.
Thank you in advance! ;)
Hope to have been at least somewhat helpful.
-
Today I have turned off traffic shaping on my 1.2RC4 pfSense box, because all activities in my network were bad with traffic shaping enabled. Now web-surfing it is ok even if there is a high load due to a http download. I did several tests in a month period, but nothing went as expected. I don't know why, may be WIFI and OPT2 interfaces bridged to LAN don't work well with implementation in 1.2RC4. I'd like to try the 1.3, which seems to support bridged interfaces and DSCP for VoIP (am I right? Does it would fit my needs described in my thread?), but I'm unsure if it is avaiable also on the embedded platform I'm currently using.
Thanks for your help, ermal.
-
Yes, for embedded and yes for fitting your needs.
Though the issue of configuring it still remains. Meaning there are 4 wizards till now in there but still do not feet everybody setups.