From: David Koski <david@kosmosisland.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] proxy arp and routing
Date: Mon, 04 Feb 2002 17:58:54 +0000 [thread overview]
Message-ID: <marc-lartc-101284561510920@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101260332616001@msgid-missing>
On Mon, 4 Feb 2002 15:59:44 +0100
Ard van Breemen <ard@telegraafnet.nl> wrote:
> On Fri, Feb 01, 2002 at 02:41:49PM -0800, David Koski wrote:
> > Given the network map below, I am able to ping any ip on all networks from
the
> > linux box. However, from the cisco router, I cannot ping past eth1 on the
linux
> > box. The reverse is also true; I cannot ping past eth0 from a host on LAN.
> > proxy-arp is enabled on the linux box and the route to a.b.c.0/24 is added
to
> > the cisco router. I haven't a clue why either way, I can only get to the
far
> > side of the linux box but no further.
> I do not care about your ascii art, just about the following:
> ip route show
> /proc/sys/net/ipv4/conf/eth[012]/proxy_arp
> /proc/sys/net/ipv4/conf/eth[012]/rp_filter
> /proc/sys/net/ipv4/ip_forward
> 1) proxy_arp must be set to 1
> 2) rp_filter: you might start with 0
> 3) ip_forward should be set to 1
> 4) all routes must be sane:
> ip route add a.b.c.0/28 dev eth0
> ip route add a.b.c.0/24 dev eth1
> ip route add 192.168.1.0 dev eth2
> ip route add default via a.b.c.1
>
> Then you should be able to arp-ping the whole world from anywhere inside
> your network.
You did not mention:
/proc/sys/net/ipv4/conf/eth[012]/forwarding
It is set to 1 also. The only difference I have with your settings above is
rp_filter. I'll change it to 0 and see what happens. Since the settings were
reverted back and I don't have access to it right now, I cannot dump the routing
table. But it was verified to be correct and consistant with the above
settings.
Thank you,
David Koski
david@KosmosIsland.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-02-04 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 22:41 [LARTC] proxy arp and routing David Koski
2002-02-02 5:13 ` David Koski
2002-02-02 17:44 ` David Koski
2002-02-02 19:19 ` David Koski
2002-02-04 14:59 ` Ard van Breemen
2002-02-04 17:58 ` David Koski [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=marc-lartc-101284561510920@msgid-missing \
--to=david@kosmosisland.com \
--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.