From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: proxy arp behaviour
Date: Thu, 25 Mar 2004 12:45:20 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0403251238570.2717@chaos> (raw)
In-Reply-To: <DAV6695HfqR77bieLYC00007982@hotmail.com>
On Thu, 25 Mar 2004, Marco Berizzi wrote:
> Hello everybody,
>
> I would like some info about proxy arp behaviour.
> I have a firewall linux running kernel 2.4.25
> with 3 NIC. Proxy arp is enabled on two of them
> (eth0 and eth1).
>
> eth1 configuration is here:
>
> ifconfig eth1 10.77.77.1 broadcast 10.77.77.3 netmask 255.255.255.252
> ip route del 10.77.77.0/30 dev eth1
> ip route add 172.17.1.0/24 dev eth1
>
> echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp
>
> Hosts connected to eth1 are all 172.17.1.0/24.
> The linux box is now replying to arp requests
> that are sent by 172.17.1.0/24 hosts on the eth1
> network segment. Is this because ip on eth1 is
> 10.77.77.1?
>
> I think that linux should not reply to arp request
> for 172.17.1.0/24 because of:
>
> ip route add 172.17.1.0/24 dev eth1
>
> Is this a bug?
This problem comes up periodically and when it does there
results in a bunch of noise to show that "Linux works perfectly...",
but never with any resolution.
What needs to be answered by persons who know the network
code is how one "connects" a particular response to a
particular device.
This has become a FAQ and needs to have some written documentation
somewhere.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-03-25 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 17:14 Marco Berizzi
2004-03-25 17:45 ` Richard B. Johnson [this message]
2004-03-25 18:46 ` Chris Friesen
2004-03-26 8:07 ` Marco Berizzi
2004-03-29 16:30 Marco Berizzi
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=Pine.LNX.4.53.0403251238570.2717@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pupilla@hotmail.com \
/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
all inboxes | Powered by JetHome®