From: Ben Greear <greearb@candelatech.com>
To: jyri.poldre@artecdesign.ee
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ethernet driver link state propagation to ip stack
Date: Fri, 14 Jan 2005 11:44:41 -0800 [thread overview]
Message-ID: <41E82129.3020403@candelatech.com> (raw)
In-Reply-To: <JJEGJLLALGANNBPNAIMMOEGLDGAA.jyri.poldre@artecdesign.ee>
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
next prev parent reply other threads:[~2005-01-14 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 16:42 Ethernet driver link state propagation to ip stack Jüri Põldre
2005-01-14 18:54 ` Peter Buckingham
2005-01-15 5:14 ` Paul Jakma
2005-01-14 19:44 ` Ben Greear [this message]
2005-01-15 12:10 ` Paul Jakma
2005-01-15 12:17 ` Amir Guindehi
2005-01-17 6:49 ` Stefan Seyfried
2005-01-17 10:03 ` Mark Watts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41E82129.3020403@candelatech.com \
--to=greearb@candelatech.com \
--cc=jyri.poldre@artecdesign.ee \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox