Thank you, after disabling the antilockout rule, the WebGUI is no longer being put into the default queue. It is now being grabbed by the normal HTTP traffic rules.

Just got a report back from the users that it is not perfect, but a lot better!  These problems may not be relating to shaping though.  I'm thinking my PSTN gateway provider may not be perfect.

http://forum.pfsense.org/index.php/topic,3201.msg19386.html#msg19386 has a pretty short but still true for version 1.2 answer. This will probably change for the next version. Ermal is working on some huge trafficshaper improvements.

I think I can … that's good point  ;) Michael

The easiest thing to do is run the trafficshaper wizard and enter the alias when it asks you if you want to give priority to voip (unless you run voipapplications). This will put all IPs of that alias into a very high serviceclass.

Thank for the answer. I have been very please with this firewalls progression over the last 4 years. Will donate money as soon as I have some  :) I will have to sort me out a jetway main board when I have the money for that.

@hoba: Download your config.xml from diagnostics>backup/restore. Strip the trafficshaper section from it and replace it by a virgin part of the default config.xml. Reupload the modified config.xml and restart from scratch. Just tried to do it, but RRD's queue graphs are still empty, whilst in queue status there are multiple items. Don't understand why this happens. If there aren't any files to edit/remove, I will update to final 1.2. It is an embedded install and I need to reflash it completely and reupload config with no shaper section in it.

Wow, i think it's working now! The problem must have been that i didn't reset states previously when testing…

@hoba: That's rather strange. What version are you running currently? Maybe you should try to use the embedded image with a cf-card as these are mounted read only most of the time if you happen to have so many powerfailures (at least if you are not using any packages). Hey Hoba, thanks for your reply. I'm currently using 1.2RC4, but I use a some packages very usefull as squidguard and this way cannot use it on a CF. The powerfailures here are not very frequent and I would like to install a new ups system with lots of batteries, so, one day this will be easier, but for now I need to make it work fine again, even that I have to install and reconfigure it from zero… One question: pfsense filesystem should be some bsd one; is it possible to install pfsense on a reiser or ext3 filesystem?? But I keep saying, pfsense is a fantastic tool! Thanks again.

..in it's current reincarnation of pfSense 1.2  Wink Looks like you now have a new featurewish for the 1.3 shaper eri  Grin Heh, sometimes i forget about differences in the shapers :). Though per user limit will be on 1.3, at least i have planned so.

Considering at one point there was around 5,500$ in pledged donations, it would be nice to get close to that. Use your conscious as your guide.

It's just packet that are not matching those rules that's all.

This might be interresting. http://en.wikipedia.org/wiki/Sliding_Window_Protocol http://en.wikipedia.org/wiki/Transmission_Control_Protocol#Flow_control

I got it to work, sort of.  I edited the qlanRoot, and only used the upperlimit 3 fields.  I set the queue to 4096k, m1 to 25%, d to 4000, m2 to 13%.  this way i get 1024k roughly to 4 seconds, and get dropped to 256k after the 4 seconds.  But EVERY SINGLE time i create a new queue to be a parent, so that i don't have to edit the main qlanRoot, i get this error, the "new queue" that i create, with basics of 1024 pipe, and a parent, the error is it has no parent???  weird.  but anyways i got the bursting to work.

If you have the resources why don;t you open a bounty for these features to get implemented. IMHO, squid should not be on the pfSense box cause of they orthogonal issues.

It is possible! How well depends…

Thank you, any general rules to go by perhaps, right off hand?