From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Vincent Guffens <guffens@auto.ucl.ac.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: 2 NICs on same network
Date: Tue, 23 Apr 2002 15:19:40 -0400 [thread overview]
Message-ID: <3CC5B3CC.22366C2B@nortelnetworks.com> (raw)
In-Reply-To: <20020423113935.A30329@openminds.be> <3CC55D62.1501C94A@nortelnetworks.com> <20020423172051.A22111@auto.ucl.ac.be> <3CC58DF3.A6AB95B1@nortelnetworks.com> <20020423225432.A9021@auto.ucl.ac.be>
Vincent Guffens wrote:
> ok, I see, so both interfaces are replying to the arp request but this time, the first interface to reply, eth0, will have its
> arp reply filtered by the arp_filter as ip_route_output will indicate eth1 as the outgoing interface for a packet that has its
> source set to the ip to resolve, which has a source route policy entry to point to eth1, is it ?
Correct. Both NICs receive the arp request, only one of them actually sends a
reply.
> But then, by curiosity, is there some reasons why two different interfaces shouldn't be in the same subnet ? I was in this
> impression having configured some cisco routers which don't even accept this configuration. Is it possible on other network
> devices ? Is there any theoretical justification ?
I don't think there are any theoretical objections. I'm pretty sure windows
will let you do it, but they don't give you nearly as much control over the
routing.
Without source routing or arp filter, traffic to any of the interfaces on the
same subnet can go through any of the interfaces on that subnet--whichever arp
reply gets there last is the winner. This can be useful for quasi-redundant
type communications, but causes big problems if you're trying to monitor the
state of your network communications paths. This is where the more strict
behaviour becomes useful.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2002-04-23 20:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 9:39 BUG: 2 NICs on same network Frank Louwers
2002-04-23 10:53 ` rpm
2002-04-23 10:52 ` Frank Louwers
2002-04-23 11:12 ` rpm
[not found] ` <20020423124756.A3572@auto.ucl.ac.be>
[not found] ` <20020423115710.A31456@openminds.be>
[not found] ` <20020423134135.A7941@auto.ucl.ac.be>
2002-04-23 10:57 ` Frank Louwers
2002-04-23 13:10 ` Chris Friesen
2002-04-23 15:20 ` Vincent Guffens
2002-04-23 16:38 ` Chris Friesen
2002-04-23 20:54 ` Vincent Guffens
2002-04-23 19:19 ` Chris Friesen [this message]
2002-04-23 13:40 ` Jeff Garzik
2002-04-23 13:45 ` J.A. Magallon
2002-04-23 13:51 ` Frank Louwers
2002-04-23 13:58 ` Harley Stenzel
2002-04-23 16:05 ` Denis Vlasenko
2002-04-23 11:11 ` Frank Louwers
2002-04-23 16:21 ` Denis Vlasenko
2002-04-23 13:20 ` Jesse Pollard
2002-04-23 17:04 ` dean gaudet
2002-04-23 22:18 ` Bill Davidsen
2002-04-25 12:09 ` Roland Kuhn
-- strict thread matches above, loose matches on Subject: below --
2002-04-23 14:55 Dag Bakke
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=3CC5B3CC.22366C2B@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=guffens@auto.ucl.ac.be \
--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