From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Vincent Guffens <guffens@auto.ucl.ac.be>
Cc: "Christopher Friesen" <cfriesen@nortelnetworks.com>,
Frank Louwers <frank@openminds.be>,
linux-kernel@vger.kernel.org
Subject: Re: BUG: 2 NICs on same network
Date: Tue, 23 Apr 2002 12:38:11 -0400 [thread overview]
Message-ID: <3CC58DF3.A6AB95B1@nortelnetworks.com> (raw)
In-Reply-To: <20020423113935.A30329@openminds.be> <3CC55D62.1501C94A@nortelnetworks.com> <20020423172051.A22111@auto.ucl.ac.be>
Vincent Guffens wrote:
>
> On Tue, Apr 23, 2002 at 09:10:58AM -0400, Chris Friesen wrote:
> > This is actually standards compliant behaviour, as silly as it sounds. However,
> > if you want stricter arp behaviour I *think* that the following will fix it. At
> > least it used to...
> >
> > echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
> I'm looking at that as well and it doesn't look as it solves the problem, in fact I think that the arp_filter is meant to
> insure that the reply will be sent out to the interface where linux would route it, that is to say, the other way around.
Actually, as long as you have your system set up to route based on source
address (which you probably should if you care about strict arp replies)
arp_filter seems to work properly. I just tested with a 2.4.18 box, with the
following address configuration:
[root@pcary1k5 /]# ip add
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:30:65:bf:46:ba brd ff:ff:ff:ff:ff:ff
inet 47.129.82.58/24 brd 47.129.82.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:50:ff:90:04:44 brd ff:ff:ff:ff:ff:ff
inet 47.129.82.107/24 brd 47.129.82.255 scope global eth1
[root@pcary1k5 /]# ip ru
0: from all lookup local
32764: from 47.129.82.107 lookup 101
32765: from 47.129.82.58 lookup 100
32766: from all lookup main
32767: from all lookup 253
[root@pcary1k5 /]# ip ro
47.129.82.0/24 dev eth0 proto kernel scope link src 47.129.82.58
47.129.82.0/24 dev eth1 proto kernel scope link src 47.129.82.107
127.0.0.0/8 dev lo scope link
default via 47.129.82.1 dev eth0
[root@pcary1k5 /]# ip ro li table 100
47.129.82.0/24 dev eth0 scope link
default via 47.129.82.1 dev eth0
[root@pcary1k5 /]# ip ro li table 101
47.129.82.0/24 dev eth1 scope link
default via 47.129.82.1 dev eth1
With this setup, arp requests for 47.129.82.58 will only be answered by eth0,
and similarly for 47.129.82.107 and eth1.
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 17:27 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 [this message]
2002-04-23 20:54 ` Vincent Guffens
2002-04-23 19:19 ` Chris Friesen
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=3CC58DF3.A6AB95B1@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=frank@openminds.be \
--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