Thank you for everybody. Bonding is indeed the best solution for interface
backup.
For my case I looking something more simpler. For my project the best
solution is to set IP of disconnected IF to 0.0.0.0 and restore on
connection.
On Jan 16, 2008 9:31 PM, Marc Volovic <[EMAIL PROTECTED]> wrote:
>
This is indeed teaming. In your case, teaming does not even require
teaming on the other side of the cable pair since you do not actively
intend to run the paired cables active/active.
The specific kernel module is "bonding"
Marc
On Jan 16, 2008, at 16:33 PM, Dotan Shavit wrote:
You just
You just described "teaming" of your network interfaces.
#
On Wednesday 16 January 2008, Constantine Shulyupin wrote:
> Hi,
>
> I have a computer connected with two interfaces to same network. Each
> one backups another.
> When eth0 is down, eth1 have to work.
> When eth1 is down, eth0 have to wo
Constantine Shulyupin
Sent: Wednesday, January 16, 2008 4:12 PM
To: IGLU List
Subject: managing two interfaces
Hi,
I have a computer connected with two interfaces to same network. Each
one backups another.
When eth0 is down, eth1 have to work.
When eth1 is down, eth0 have to work.
The most sutable
Hi,
I have a computer connected with two interfaces to same network. Each
one backups another.
When eth0 is down, eth1 have to work.
When eth1 is down, eth0 have to work.
The most sutable solution I've found is to monitor RUNNING status of
interfaces and change the routing table from my program.
C
