[SOLVED] traffic shaper queues bug
-
I can't tell. I just guess that it cannot be undone simply by reverting a single patch.
-
wouldnt it be possible to edit the config file manually to change the behavior temporarily till its fixed?
-
I have no clue on manual config file editing. A temporary workaround (that appears to work for me) is to simply ignore the Floating tab and to select queues directly on LAN, WAN and all OPTx tabs. It is not comfortable, but doable.
-
i have the below rule which i tried match as well as pass but still download traffic doesnt go to the proper queue
<rule><id><type>pass</type> <tag><tagged><direction>out</direction> <quick>yes</quick> <floating>yes</floating> <max><max-src-nodes><max-src-conn><max-src-states><statetimeout><statetype>keep state</statetype> <os><protocol>udp</protocol> <source> <any><destination><address>mysip</address></destination> <defaultqueue>qVoIP</defaultqueue></any></os></statetimeout></max-src-states></max-src-conn></max-src-nodes></max></tagged></tag></id></rule> <rule><id><type>pass</type> <tag><tagged><direction>in</direction> <quick>yes</quick> <floating>yes</floating> <max><max-src-nodes><max-src-conn><max-src-states><statetimeout><statetype>keep state</statetype> <os><protocol>udp</protocol> <source> <address>mysip</address> <destination><any></any></destination> <defaultqueue>qVoIP</defaultqueue></os></statetimeout></max-src-states></max-src-conn></max-src-nodes></max></tagged></tag></id></rule>can u plz mention this above rules how do i recreate using wan and lan tabs to make it work
-
Following is my config for a teleconference device that use TCP for control channels and UDP for data channels. Not sure if it works for you.
– on the LAN interface add new pass rules before the default rule with source IP = any, destination IP = any, destination port = 1720 TCP and 3230-3279 UDP. Select queue = qVoIP.
– repeat the same procedure on the WAN and OPTx interfaces. (Note: my WAN + OPTx are all connected to Internet. I've started setting up the shaper using the single-LAN-multi-WAN wizard.)
I've configured the shaper this way only for teleconference. In my system there are so many Internet links and so many types of traffics that I must rely on the (now unreliable) Floating Tab for the other traffic types. At least untill we replace pfsense with an other shaper.
-
i think it wont work as im using rules that match based on the server ip rather than any particular or range of ports but ill still give it a try
-
I am posting here but this is in general.
Traffic shaper behaviour should be ok on latest snapshots. -
@ermal:
I am posting here but this is in general.
Traffic shaper behaviour should be ok on latest snapshots.I updated to the latest available (built on Mon Jul 4 16:48:37 EDT 2011) but didint change nothing to me.
-
Thanks, Ermal. I will try to update tonight after my wife goes to bed :) Currently running snap from June 22nd. This is one reason I love having pfsense virtualized on my ESXi server.
1. Take snapshot of virtual machine on the ESXi box.
2. Do the upgrade, and reboot pfsense.
3. Test things out.
4a. If all is well, delete the snapshot.
4b. If something is pooched, roll back to the snapshot and reboot pfsense. -
@Ermal: I updated to Mon Jul 4 16:48:37 EDT 2011 snapshot but still it does not seem to work. I have an NTP server for testing. With the Floating Tab alone using pass out on any interface rules (with queueing), only NTP requests to my server are shaped, NTP replies are not.
-
No detectable change at all. I wiped the shaper. Created the same trivial shaper config as before. e.g. 10.0.0.7 is the voip host. Set for PRIQ. Save the config. Call my office phone and leave a message. No activity on the qVOIP queue. Finally, out of desperation, I deleted the 10.0.0.7, and saw the one floating rule replaced by two rules: one for the SIP ports and one for the RTP ports. I called my office phone again, and started leaving a voicemail. Looking at the queues as I did, I saw about 86kb/sec going out via qVOIP, so it is clearly the source IP address matching that was hosing me. Sigh…
-
Oh yeah, and the failure to use qACK at all outbound is still there…
-
i guess the last snapshot built was 04-Jul-2011 18:11 and in that its not fixed but mayb if a new snap is built then need to test on that
-
You have to wait for a new snapshot to have those changes :)
-
@ermal:
You have to wait for a new snapshot to have those changes :)
I tried the last snapshot (built on Thu Jul 7 00:25:19 EDT 2011) but didnt work…
nevermind, is working on the last snapshot (built on Thu Jul 7 16:08:10 EDT 2011) , tnx ermal :D
-
same here, finally works fine
-
Wish I could say the same. The two issues I've been reporting all along are still in the snapshot from 22:58 last night. e.g. VOIP with a host IP: still broken. qACK not being used: still broken :(
-
mayb u could post ur rule set if that might have some issue, try also ticking the quick match box for the rule.
-
No rule set other than created by the wizard. This is an absolutely trivial config. PRIQ. 22mb/sec inbound and outbound. Stepping thru the wizard, I default everything except for the voip section, where I selected "generic (lowdelay)" and put 10.0.0.7 (my asterisk box) as the IP. I get no LAN queues, and nothing goes into the qACK queue (occasional packets do go into qVOIP, but none of the audio, since the bit rate never gets more than a couple of kb/sec).
-
mayb u could post ur rule set if that might have some issue, try also ticking the quick match box for the rule.
This seems wrong. The shaper rules are non-quick (I thought) because all they do is queue the packet, there is no pass, which is handled (presumably) by the default LAN outbound rule, no? If I marked this as quick, wouldn't it not to be processed by the LAN out rule? Or am I confused? Besides which, the change I made yesterday (which does work, specifying asterisk/vonage, causing a rule for the SIP packets and a rule for the RTP packets), doesn't have quick and it works :(