How to Limit Bandwidth per IP?



  • Hello. I'm really new on pfSense, and this is my first post here. My first question, could we limit bandwidth per IP (client) on pfSense?

    Thank you.
    djohan.



  • You can use the traffic shaper.



  • Search the forum please.



  • @hoba:

    Search the forum please.

    I've tried to search the forum. And I see it's hard to find it. If you don't mind telling me, would you please direct me to the links which tell about limiting bandwidth per IP?

    Thank you.



  • Short story is: It can't be done easily in 1.2 but it's on it's way for the new completely reworked trafficshaper in the upcoming 1.3 version. See http://forum.pfsense.org/index.php/topic,2718.0.html if you want to follow developement and what's in the pipe regarding the shaper (you might want to skip the first few pages).



  • Short story is: It can't be done easily in 1.2

    What is the long story?  How can it be done the hard way?

    I really need the ability to control bandwidth based on IPs.

    If pfSense does not do this, I have to find another solution. AN I really think pfSense if the best choice for all my other needs.

    Does anybody know if there is a Beta version of 1.3 that will do bandwidth based on IPs?

    How can I get the Beta?

    Thanks, Greg



  • You could maybe set up a proxy behind pf in the meantime. The side benefit of this is that if multiple users are requesting msn.com or whathaveyou those requests will stop at the proxy for static content.

    Sorry thats all the help I have right now as I haven't had to implement this. You'll have to think creatively or purchase a solution like Sonicwall.



  • I am pretty sure you can do this with Squid if we are talking about http traffic.



  • Or, if you require authorization, you can do this with any RADIUS server supporting sending bandwidth parameters in RADIUS attributes (e.g., UTM5 RADIUS, freeRADIUS, etc.).

    @Sh4:

    I am pretty sure you can do this with Squid if we are talking about http traffic.


Log in to reply