public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Jan De Luyck <lkml@kcore.org>
Cc: Steve Iribarne <steve.iribarne@dilithiumnetworks.com>,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: ARP routing issue
Date: Fri, 14 Jan 2005 22:47:57 +0000	[thread overview]
Message-ID: <41E84C1D.9060505@superbug.co.uk> (raw)
In-Reply-To: <200501061711.59301.lkml@kcore.org>

Jan De Luyck wrote:
> On Thursday 06 January 2005 17:06, Steve Iribarne wrote:
> 
>>Hi Jan,
>>
>>
>>-> default gateway is set to 10.0.22.1, on eth0.
>>->
>>-> Problem is, if I try to ping from another network
>>-> (10.216.0.xx) to 10.0.24.xx, i see the following ARP request:
>>->
>>-> arp who-has 10.0.22.1 tell 10.0.24.xx
>>->
>>
>>You see that coming out the eth0 interface??
>>
>>If that is the case it is most definately wrong.  Assuming that your
>>masks are setup properly.  But I haven't worked on the 2.4 kernel for a
>>long time so I'm not so sure if what you are seeing is a bug that has
>>been fixed.
> 
> 
> The network information is:
> eth0 10.0.22.xxx mask 255.255.255.0
> eth1 10.0.24.xxx mask 255.255.255.0
> 
> routing:
> 10.0.22.0 0.0.0.0 255.255.255.0 eth0
> 10.0.24.0 0.0.0.0 255.255.255.0 eth1
> 0.0.0.0  10.0.22.1 0.0.0.0  eth0
> 
> Jan
> 

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.

the "arp who-has 10.0.22.1 tell 10.0.24.xx", you can safely ignore the 
"10.0.24.xx" bit, as that will be ignored by the device responding to 
the ARP.
It is just highlighting the point that you have 2 paths to the same 
destination.

Cheers

James


  parent reply	other threads:[~2005-01-14 22:50 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 [this message]
2005-01-15 12:31     ` Jan De Luyck
2005-01-15 22:51       ` Alan Cox
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=41E84C1D.9060505@superbug.co.uk \
    --to=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