I know why the IPv6 rule was not matching, my aliases was only targeting IPv4 addresses!

Confused about this one thing, with a 290 main queue and a 225 queue for everything else, why do I still get latency? Even if the 225 is saturated, there should be enough bandwidth where the main queue isn’t jammed no?

Or another way to put it, shouldn’t the queue only take into effect if the threshold is exceeded? I mean that literally and not literally, I don’t know how it technically works, but I would assume the queue would flow naturally, if I have 10 checkout lanes in a supermarket, and I have 8 people waiting, that shouldn’t cause a jam?

Use Captive Portal along with FreeRadius. Create a user and restrict no of simultaneous devices to 3. Share the username and password with all the users.... at a time only 3 will be able to connect.

Regards,
Ashima

@maguve said in "Limiters" no limita.:

Saludos desde Venezuela, he tratado de limitar mis clientes

no se si falta alguna opcion en los limiters, si pudieran darme una ayuda o indicio de la falla.

Imposible saber/poder decir, si No Muestras lo que estás haciendo

@ibbetsion

You must have something stuck in there somewhere. I just looked on a spare pfsense box I've got, with no traffic shaping setup at all, and this is the result I see in Diagnostics->Limiter Info

Limiters: No limiters were found on this system.

If you set pfBlocker to "native alias" instead of block, that will just create an alias and you can create your own block/allow rules however you want them.

@bobbenheim said in How to limit incoming packets per second per ip?:

@NogBadTheBad Doing bandwidth limiting i can understand, packet limiting i can not :)

Yup I'm not sure he actually means packet limiting ☺

So, I think I found the source of my issue: my DNS setting.

I had shut off and uninstalled SquidGuard, Squid and Snort (in that order) and still had no luck. As soon as I changed my DNS settings to Google (for example), I no longer have any latency issues. Put back Squid and Snort and still no latency.

So, it looks like something with OpenDNS is causing my problem.

Off to try another DNS to see if it's still running ok.