I am getting the following error (BETA3-PLUS-11548-PLUS-11567):
Acknowledge All .:. 04-21-06 07:34:04 - [filter_load]There were error(s) loading the rules: pfctl: the sum of the child bandwidth higher than parent qwanRootpfctl: linkshare sc exceeds parents sc/tmp/rules.debug:31: errors in queue definitionpfctl: the sum of the child bandwidth higher than parent qlanRootpfctl: linkshare sc exceeds parents sc/tmp/rules.debug:32: Syntax error in config file: pf rules not loaded The line in question reads [ the sum of the child bandwidth higher than parent qwanRootpfctl]: .:.
I have tried re-running the traffic shaper and have reduced the Voip settings to almost nothing but I am still getting it.
Any help would be greatly appreciated
Make sure you put the correct bandwidth in for up/down speeds on the second screen in the wizard.
In Traffic Shaper section, When you press the button "Remove Wizard" or pressing the tab "EZ Shaper wizard"
it will remove your existing shaper rules and queue completely.
Can you please put a messagebox asking the user if they really want to proceed before doing that ?
During the last 3 days, I pressed those button/tab by accident many times and was forced to begin from the beginning.
Sorry about that ... I'm getting the latest from CVS now.
Blaiming newbie status for this :-[
HEAD is not meant to be consumed by non-developers. You should be running code in the RELENG_1 branch. Better yet, unless you find a bug that has been fixed post release, you should really run a released binary. We can't and won't support anything else. I'm marking this thread solved. Thanks
It's up to you to set your bandwidth limit. 20% might have been a bit conservative. However, I recommend running some bandwidth test with the shaper turned off first. Test upstream and downstream. I have not yet seen a line that had exact the advertised speed. Some are a bit slower, some even a bit faster. Don't trust your provider ;)
In case your line is slower than advertised and you use the advertised values shaping won't be successful when reaching your lines limit.
I think what he's looking for is a way to monitor the total throughput for the month….possibly auto-throttle at a certain usage amount so that he doesn't go over on his usage.....ie you get 100gb/month transfer limit then pay large amounts per gig after that.
I have 5 computer connected to my Lintex router trough LAN.
Can I configure pfsense to have low prioritizing computer 1 based on the "IpNumber/Mac Address" and standard prioritizing computer 2 based on the "IpNumber/Mac Address" and high prioritizing computer 3-6 based on their "IpNumber/Mac Address" ?
Yes this can be done but not so easily with the wizard. You will need to run the wizard then create custom queues and rules. I use this setup on my lan where I give piority and 59% of the bandwidth to a set of computers (me only ;)) and 39% to a few others. However you can't use mac addresses so I had to make use of static arp to assign the ipaddress.
Just wanted everyone to know everything is working great. This blows m0n0wall away. Clients are pissed off as they were getting a 10Mbs feed but they were only paying for 3Mb. NTOP Great addition really helps with figuring out where my client traffic is coming from and who to point the finger at.
download: the same as above but
m2 is empty
upload queue - up105105
download queue - down105105 (I found that specifying here qP2Pdown doesn't work)
source: 192.168.105.105 (single host)
rest of fields are empty/default
There's a limit of 256 queues in ALTQ, fyi. We can change that if/when it becomes an issue (at this time pfsense rule generation performance will be a bottleneck long before you get to 256 queues though).
Run the trafficshaper wizard. It has exactly the option you need. You can enter a VOIP IP or an alias. You also have the option to select Vonage as VOIP Povider. Either should work. The choppyness was surely related to the issues the shaper had these days. Give it a go. It should be fine now.
Do not try to import my original config file into your system. It was only posted so as to help others understand a little bit better how the traffic shaper works and what was working for me at that time. If it is too confusing for you to decipher, then you probably need to learn more about TCP/IP, ports, and protocols.
This isn't pfSense, so you don't have fancy hostgroupaliases, queuegraphs and so on. You have to set it up and simulate a maxed out line and do phonecalls and terminalsessions under that condition and tweak it until you are happy with it. ;)
I'll pm you something later when I'm at home. I don't think it makes sense to discuss that public as the m0n0 shaper is completely different compared to pfSense. I suggest closing this thread.
and an lil extra questionL: shaping will only work on upstream data as by the time downstream gets to my box its far to late as the pipe has been saturated and my HTTP traffic for example is sitting at the ISP waiting its turn. is that correct?
Yes, the traffic shaper in pfSense can only shape packets exiting an interface but it can also shape downlaods by shaping the traffic exiting lan card to your pc (you can look at it from the perspective of your box uploading to your pc). In other words, download shaping isnt dependent on your isp alone, pfsense actively shape downloads just the same as uploads.
However if you saturate your link traffic will be queued up in your box and possible at your isp as well (or your isp will drop extra traffic), so its a good idea to set ur max download & upload speed to a fraction below what your isp advertised, that way your box will limit the traffic before your isp policing or shaping kicks in, you sacrifice some bandwidth to gain better control over your traffic.
(ab-)use the voip queue for that. run the shaper and add an IP for the voip queue. after it has finsihed edit the queue and set the traffic limit at upper limit and dump the realtime value. set the priority lower. that's it. then copy these for as many clients as you need. however you have to keep the math in mind or you'll get an alert because of assigning more bandwidth than you have.
Patches accepted (although I know exactly what needs to be done, I backed out the code for this back in June due to other issues) - but be warned the shaper is under heavy development, you will want to coordinate any work you do with me.
Or again, donations are accepted - at this point a quiet machine with Intel FXPs would be appreciated. I can no longer do shaper development on my (silent) Soekris as there's an OS level bug that affects the NICs on this machine.
Here is another thing I observed today.. This rule:
pass out on dc0 from any to 192.168.1.7 keep state tagged unshaped tag qHighDownL (subset of rules posted earlier)
dc0 - LAN interface
Does not work for traffic originating from the firewall itself. Squid and ssh traffic to 192.168.1.7 for example would fall into the default queue instead of qHighDownL, so does all traffic to any ip whos traffic originated at the firewall. It only works for traffic comming through WAN.
Squid is boud to lo 127.0.0.1 while ssh is bound to the any address *. Is there any reason why this rule don't work for such traffic? I though about it and still can figure out why.
tried iperf from firewall to lan pc with ip address 192.168.1.7 -> the traffic found its way into the correct queue. however the others stated above still don't get queued properly. Could it have have something to do with the direction in which the connections were establish?
Well Its killing my upload shaping see thread: http://forum.pfsense.org/index.php?topic=630.0
I understand that when the packet is nat'd u no longer know where its from.. But doesn't the filter policy sort that out, I mean once the packet comes in on lan its tagged and the filter policy will take care of the queuing. so the any -> any rule wouldn't be needed.
when I get time I gonna manually modify /tmp/rules.debug and test that theory. I really need to get upload shaping working by ip addresses.
Actually, you may be on to something, I'll have to think about it a little more. We might not need the "pass out" rules at all as tags are sticky. Looks like a case of overthinking. I'll ponder removing that and if it makes sense (and works) this might see an MFC to 1.0.
Until all the bugs and issues are resolved in the current code I'm not making any other changes, it's too difficult to troubleshoot. And no-one has convinced me that the last changes I made have fixed the issues (nor have I been convinced that they haven't).
One major bug that was just discovered was the shaper no longer subtracted 20% from the upload and download values. If anyone is having trouble with the shaper please re-run the wizard again and subtract 20% from the upload and download values.
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.