From: "Marco Berizzi" <pupilla@hotmail.com>
To: "Chris Friesen" <cfriesen@nortelnetworks.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: proxy arp behaviour
Date: Mon, 29 Mar 2004 18:30:50 +0200 [thread overview]
Message-ID: <Sea2-DAV28PFR6sKBEr0001522a@hotmail.com> (raw)
My apologies Chris.
I haven't full explained my configuration.
Here is:
ifconfig eth0 172.17.1.1 netmask 255.255.255.0
ifconfig eth1 10.77.77.1 netmask 255.255.255.252
ip route del 172.17.1.0/24 dev eth0
ip route del 10.77.77.0/30 dev eth1
ip route add 172.17.1.254 dev eth0
ip route add 172.17.1.0/24 dev eth1
ip rule add iif eth1 table dmz-ipsec priority 504
ip route add default via 172.17.1.254 dev eth0 table main metric 1
ip route add default via 172.17.1.254 dev eth0 table dmz-ipsec metric 1
ip route flush cache
echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp
Now, hosts connected to eth1 are all 172.17.1.0/24.
The linux box is now replying to arp requests for
172.17.1.0/24 hosts, sent by 172.17.1.0/24 hosts,
on the eth1 network segment.
Chris Friesen wrote:
> Marco Berizzi wrote:
>
> > 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.
>
> Arp requests for what IP addresses?
The linux box is replying to arp requests for 172.17.1.0/24, sent
by 172.17.1.0/24 systems (windoze 2000 and Linux 2.4.25).
next reply other threads:[~2004-03-29 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 16:30 Marco Berizzi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-25 17:14 proxy arp behaviour Marco Berizzi
2004-03-25 17:45 ` Richard B. Johnson
2004-03-25 18:46 ` Chris Friesen
2004-03-26 8:07 ` 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=Sea2-DAV28PFR6sKBEr0001522a@hotmail.com \
--to=pupilla@hotmail.com \
--cc=cfriesen@nortelnetworks.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.