[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Unable to ping gateway

Sergio Basurto wrote:
When bonding is set up with the ARP monitor, it is
important that the
slave devices not have routes that supercede routes of
the master (or,
generally, not have routes at all).  For example,
suppose the bonding
device bond0 has two slaves, eth0 and eth1, and the
routing table is
as follows:

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface U 40 0 0 eth0 U 40 0 0 eth1 U 40 0 0 bond0 U 40 0 0 lo

In this case, the ARP monitor (and ARP itself) may
become confused,
because ARP requests will be sent on one interface
(bond0), but the
corresponding reply will arrive on a different
interface (eth0).  This
reply looks to ARP as an unsolicited ARP reply (because
ARP matches
replies on an interface basis), and is discarded.  This
will likely
still update the receive/transmit times in the driver,
but will lose

The resolution here is simply to insure that slaves do
not have routes
of their own, and if for some reason they must, those
routes do not
supercede routes of their master.  This should
generally be the case,
but unusual configurations or errant manual or
automatic static route
additions may cause trouble.

From:"Linux Ethernet Bonding Driver mini-howto"

So the solution is to not set a gateway for eth0 and eth1, but only set it for bond0?


Reply to: