Per IP bandwidth limit

[Peter Booth]

Why do you want to do this at all? 
What is the real underlying problem that you are attempting to solve?



> On Nov 11, 2019, at 8:29 AM, Kostya Velychkovsky <velychkovsky at gmail.com> wrote:
> 
> I use Linux, and had a bad experience with Linux shaper (native kernel QoS mechanism - tc ), it consumed a lot of CPU and worked unstable. So I rejected the idea to keep using it. 
> 
> пн, 11 нояб. 2019 г. в 15:23, Christos Chatzaras <chris at cretaforce.gr <mailto:chris at cretaforce.gr>>:
> 
> > On 11 Nov 2019, at 15:09, Kostya Velychkovsky <velychkovsky at gmail.com <mailto:velychkovsky at gmail.com>> wrote:
> > 
> > Hello, is it the correct way to limit download/upload speed per client IP,  at the same time ignore how many connections it opens and request rate produced?
> > 
> > I need just limit bandwidth for example  100 mbit/s per IP, and no matter it opens 1 connection or 100 simulation connections. 
> > 
> 
> Maybe it's better to do this with firewall. For example in FreeBSD this can be done with IPFW + Dummynet.
> _______________________________________________
> nginx mailing list
> nginx at nginx.org <mailto:nginx at nginx.org>
> http://mailman.nginx.org/mailman/listinfo/nginx <http://mailman.nginx.org/mailman/listinfo/nginx>
> 
> 
> -- 
> Best Regards 
> 
> Kostiantyn Velychkovsky 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20191111/b3ed8cb9/attachment-0001.htm>