From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jan De Luyck <lkml@kcore.org>
Cc: James Courtier-Dutton <James@superbug.co.uk>,
Steve Iribarne <steve.iribarne@dilithiumnetworks.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org
Subject: Re: ARP routing issue
Date: Sat, 15 Jan 2005 22:51:17 +0000 [thread overview]
Message-ID: <1105829477.16028.0.camel@localhost.localdomain> (raw)
In-Reply-To: <200501151331.04879.lkml@kcore.org>
On Sad, 2005-01-15 at 12:31, Jan De Luyck wrote:
> On Friday 14 January 2005 23:47, James Courtier-Dutton wrote:
> > That arp is perfectly OK.
> > The routing table will cause the icmp echo packet to go from 10.216.0.xx
> > to 10.0.24.xx via the 10.0.24.x network.
> > The icmp echo response will return via the 10.0.22.x network back to the
> > 10.216.0.xx network.
> > So the paths in each direction are different.
>
> Yes, but unfortunately I never ever receive the icmp echo reply, and the arp
> table always lists the ip as "incomplete". Nothing I try to do to with that
> interface (ssh/...) ever works.
If the directions are different does your distro enable rp_filter by
default - that may cause such problems. You might also want to ask on
netdev@oss.sgi.com - the network layer list
next prev parent reply other threads:[~2005-01-15 23:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 16:06 ARP routing issue Steve Iribarne
2005-01-06 16:11 ` Jan De Luyck
2005-01-06 17:53 ` Paul Rolland
2005-01-06 17:57 ` Jan De Luyck
2005-01-14 22:47 ` James Courtier-Dutton
2005-01-15 12:31 ` Jan De Luyck
2005-01-15 22:51 ` Alan Cox [this message]
2005-01-24 10:40 ` ARP routing issue - semi-solved Jan De Luyck
-- strict thread matches above, loose matches on Subject: below --
2005-01-07 1:29 ARP routing issue Zhenyu Wu
2005-01-06 17:51 Steve Iribarne
2005-01-06 17:57 ` Jan De Luyck
2005-01-06 15:47 Jan De Luyck
2005-01-06 17:51 ` Alan Cox
2005-01-07 6:49 ` Jan De Luyck
2005-01-07 7:44 ` Julian Anastasov
2005-01-07 8:06 ` Jan De Luyck
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=1105829477.16028.0.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=James@superbug.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=lkml@kcore.org \
--cc=steve.iribarne@dilithiumnetworks.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