From: Martin Volf <mv@inv.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Does anyone have a working proxyARP setup?
Date: Tue, 12 Oct 2004 16:55:45 +0000 [thread overview]
Message-ID: <416C0C91.5090108@inv.cz> (raw)
In-Reply-To: <41676C12.72F7D09D@iswest.com>
gypsy wrote:
>>Could you please post the output of 'route -n', 'ip route' and 'ip neigh
>>show' as well as any 'ip route [add|del|*]' commands you run?
>
> I guess not. Martin, is there some reason you do not wish to post these
> things?
Hello,
sorry for the delay. I have used something like this:
router:
ifconfig eth0 172.16.7.42 netmask 255.255.255.0 broadcast 172.16.7.255
route add default gw 172.16.7.1
ifconfig eth1 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255
ifconfig eth2 192.168.1.1 netmask 255.255.255.255 -broadcast
route add -host 192.168.1.17 device eth2
route add -host 192.168.1.18 device eth2
route add -host 192.168.1.19 device eth2
echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp
echo 1 > /proc/sys/net/ipv4/conf/eth2/proxy_arp
The network 192.168.1.0/24 is divided into two parts, ip addresses
192.168.1.17, .18, .19 are connected to eth2, other ip addresses to eth1.
192.168.1.17:
ifconfig eth0 192.168.1.17 netmask 255.255.255.0 broadcast 192.168.1.255
route add default gw 192.168.1.1
traceroute from 192.168.1.17 do 192.168.1.2:
1 192.168.1.1 1.08 ms 0.73 ms 0.723 ms
2 192.168.1.2 0.85 ms 0.77 ms 0.715 ms
"arp -an" at 192.168.1.17:
? (192.168.1.1) at 00:00:B4:9F:A4:58 [ether] on eth0
? (192.168.1.2) at 00:00:B4:9F:A4:58 [ether] on eth0
(note the same MAC address)
HTH,
--
Martin
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-10-12 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 4:41 [LARTC] Does anyone have a working proxyARP setup? gypsy
2004-10-09 8:05 ` Martin Volf
2004-10-09 17:46 ` gypsy
2004-10-12 13:33 ` gypsy
2004-10-12 16:55 ` Martin Volf [this message]
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=416C0C91.5090108@inv.cz \
--to=mv@inv.cz \
--cc=lartc@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.