Seperate Throttle Ques per IP



  • I have been using PFSENSE 1.3 for awhile now and I am now trying to use 2.0 for a new network requirement.  Currently I have one pc on my network which is constantly maxing out the internet connection from everyone else. I was successfully able to use version 1.3 Penalty box filters under firewalls rules to throttle that single user down to a specific speed. I now have 3 users who are causing the same type of problem for us. I am trying to figure out how to use the new throttling feature of 2.0 BETA 2 (Latest snapshot) to setup multiple throttle and penalty box ques by ip address. I looked over the wiki and through the forum and I see several posts about it but I do not see the specific solution in any of the posts. If you could provide some suggestions on setting up multiple throttles I would appreciate it.

    I also have a bug report about 2.0. When you try to use the latest snapshot it will not allow you to enter an ip address or throttle speed when the box is checked to enable penalty box. When you uncheck the penalty box enable it allowed you to enter the info but will not save it when you continue the firewall wizard.



  • I also experience that issue with the traffic shaper, along with enabling device polling with compatible network cards causes CPU to sit at 100% constantly.



  • I can confirm the bug mcamino has; Going through the shaper wizard for 1 LAN multiple WAN, the option boxes are disabled if the feature are enabled. Have to disable the feature before being able to change the options for the feature.
    This happens on all the wizards features (voip, p2p, game, etc).
    Running the 20100529 i386 build



  • Probably better to report 2.0 specific issues on that board.


  • Rebel Alliance Developer Netgate

    @hellsacolyte:

    I also experience that issue with the traffic shaper, along with enabling device polling with compatible network cards causes CPU to sit at 100% constantly.

    Polling uses 100% CPU. That's how polling works (uses normally idle CPU time to look for data on network interfaces), and isn't related to this other issue.


Log in to reply