Message-ID: <41E82129.3020403@candelatech.com>
Date: Fri, 14 Jan 2005 11:44:41 -0800
From: Ben Greear <greearb@candelatech.com>
Organization: Candela Technologies
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3) Gecko/20041020
MIME-Version: 1.0
To: jyri.poldre@artecdesign.ee
CC: linux-kernel@vger.kernel.org
Subject: Re: Ethernet driver link state propagation to ip stack
References: <JJEGJLLALGANNBPNAIMMOEGLDGAA.jyri.poldre@artecdesign.ee>
In-Reply-To: <JJEGJLLALGANNBPNAIMMOEGLDGAA.jyri.poldre@artecdesign.ee>
Content-Type: text/plain; charset=ISO-8859-4; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1388
Lines: 35

J?ri P?ldre wrote:
> All,
> 
> I am experiencing issues with connecting two network adapters to the same
> subnet, eg.
> 
> eth0 192.168.100.200
> eth1 192.168.100.201
> 
> The task is to have redundant connections to two different hubs. In case one
> link goes down the connection should go through the other. The driver
> handles link events with netif_carrier_ok and netif_carrier_on from
> linux/netdevice.h. These eventually send messages to networking stack with
> netdev_change_state from net/core/dev.c
> 
> My question is:  Does the kernel handle  the interface state/routing tables
> modifications due to link changing automatically or is there some external
> daemon required to do that. Any links are greatly appreciated.

As far as I know, you have to handle this sort of thing in user-space.  You may
also have ARP issues with having two interfaces on the same subnet.  Often people
will use two private, non-related IP addresses and then migrate a virtual IP back
and forth, placing it on the preferred (ie, link-ok) interface.

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/