QOS/tcb on linux for particular host on particular port

blason · 02-08-2016, 11:15 AM

Hi Guys,

can someone guide me how do I configure QOS/traffic shaping policy on mu linux box for one IP or network for one port?

e.g. I have my linux box which is at 192.168.50.2 and have other server 192.168.50.30. I need to restrict 192.168.50.30 to talk to 192.168.50.2 on port 25 with bandwidth 2mbit and burst rate 2.5mbit

can someone guide me pls?

TB0ne · 02-08-2016, 11:22 AM

Quote:

Originally Posted by blason

Hi Guys,
can someone guide me how do I configure QOS/traffic shaping policy on mu linux box for one IP or network for one port?

e.g. I have my linux box which is at 192.168.50.2 and have other server 192.168.50.30. I need to restrict 192.168.50.30 to talk to 192.168.50.2 on port 25 with bandwidth 2mbit and burst rate 2.5mbit

can someone guide me pls?

Please see the LQ Rules about text-speak, and about not using it.

QOS is typically done on the network (router/switch), not on the system itself. That said, many of the SERVICES on your system can be configured to restrict access to a specific port/address, and may be able to do bandwidth throttling for that service as well. However, you don't tell us what service is running on port 25, or tell us what version/distro of Linux you're using. Without details, there isn't much we can tell you.

blason · 02-08-2016, 11:34 AM

Well, I have postfix server running on port 25 and have CentOS 6.4. I just need to restrict bandwidth for port 25 and else should run fine.

Would it be possible for one port then?

TB0ne · 02-08-2016, 01:16 PM

Quote:

Originally Posted by blason

Well, I have postfix server running on port 25 and have CentOS 6.4. I just need to restrict bandwidth for port 25 and else should run fine.

Would it be possible for one port then?

Again, QOS is done on routers/switches, not on the server. There are four directives in Postfix that let you limit *THROUGHPUT*, but not bandwidth.
The initial_destination_concurrency, default_destination_concurrency_limit, local_destination_concurrency_limit, and default smtp_destination_concurrency_limit do those things, to a point, but that's not what you're asking. You might be able to use wondershaper to limit bandwidth, but that *IS NOT* QOS.

http://www.mdash.net/traffic-shaping-using-wondershaper