I think you need policy routing:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/htm...

https://doc.lagout.org/network/inetdoc/Policy_Routing_in_Linux_ENG.pdf

Although it may be tempting to use some sort of round-robin, it would be safer to have specific rules based on the destination, so for example you send all web traffic to one ISP and add exceptions to route specific traffic to the second ISP (e.g. streaming platforms), with each rule having a "backup route" to the other ISP.

Cheers, Lorenzo

Il giorno ven 12 mar 2021 alle ore 08:31 Thomas Stephen Lee < lee.iitb@gmail.com> ha scritto:

On Wed, Feb 17, 2021 at 2:04 AM Kenneth Porter shiva@sewingwitch.com wrote:

...

--On Tuesday, February 16, 2021 12:00 PM +0530 Thomas Stephen Lee lee.iitb@gmail.com wrote:

...

The solution should be a software one without acquiring new hardware. What is ideal is the bandwidth of two connections and half bandwidth when one link is down.

The search term you're looking for is "NIC bonding". Here's the first

hit I

...

get from Google:

<

https://www.enterprisenetworkingplanet.com/linux_unix/article.php/3850636/Un...

...

Hi,

I tried

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/htm...

without success

I have a feeling that bonding is for interfaces on the same network, not two internet routers. Please correct me if I'm wrong.

---

Lee _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos