Limiter not working



  • can any1 else confirm that limter isnt working, it works but after a while all clients stop getting dhcp lease and if they do also, all internet traffic stops so non of the clients r able to surf



  • I'm on april 4 snapshot, running 24hs and limiter works as expected.

    The only thing that do not work for me is connecting to pfsente with PPTP-VPN from outside (it connect but no traffic)



  • i think its either im doing something wrong or actually there is some issue so let me post my config to better understand it

    first i got a group of clients placed under a single alias called 3rd floor as shown below, then i have created the limiter with the default advanced options, just the download and upload speed as shown and then i have the firewall rule under LAN and the in/out as upload/download limiter queues and as soon as i apply them all, all 3rd floor clients r connected to firewall but they r not able to access the internet, as soon as i clear the in/out from the firewall rule and apply them and everything is back to normal.








  • Hi Xbipin,

    This sounds like the issue I am having here http://forum.pfsense.org/index.php/topic,24059.msg125590.html#msg125590

    However I am using the limiter used by the captive portal.

    Regards

    Slam



  • @xbipin:

    i think its either im doing something wrong or actually there is some issue so let me post my config to better understand it

    first i got a group of clients placed under a single alias called 3rd floor as shown below, then i have created the limiter with the default advanced options, just the download and upload speed as shown and then i have the firewall rule under LAN and the in/out as upload/download limiter queues and as soon as i apply them all, all 3rd floor clients r connected to firewall but they r not able to access the internet, as soon as i clear the in/out from the firewall rule and apply them and everything is back to normal.

    For limiter(or AKA virtual interface) to work you should:
    1. apply "source" mask to your upload traffic, and assign it to "IN" traffic in LAN interface
    2. apply "destination" mask to your download traffic, and assign it to "OUT" traffic in LAN interface

    In your configuration the limiter lacks the mask.

    If you only need to limit the queue traffic (not limit per IP) then I think you should use a queue,not a limiter



  • tried ur suggesstion by changing the source and destination mask but still the same.

    basically what i have done is, create an alias for all those clients i want to limit and created a rule to first put all their traffic as p2p traffic and not evaluate it based on the type and then im trying to limit their upload and download using limiter.

    the reason i dont wanna create a queue in the traffic shaper is then it will mess up other stuff for other clients and secondly mayb im just lazy to sue the limiter as a easy way out.



  • If you need to limit per user (or per IP) to 600Kbps* you use limiter, and with the configuration I provided works fine, at least in my setup.
    If you need to limit all users to 600Kbps* you use queue.

    You can create a new queue and that should not affect other users in others queues.

    *: 600Kbps is just an example based in your config.



  • yes true but if mask is set to none then u can limit all users to a specific upload and download.



  • any progress on this coz i see some dummynet patches lately


Log in to reply