netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos Velasco" <carlosev@newipnet.com>
To: "Carlos Velasco" <carlosev@newipnet.com>, "Julian Anastasov" <ja@ssi.bg>
Cc: "Bart De Schuymer" <bdschuym@pandora.be>, netdev@oss.sgi.com
Subject: Re: Bug? ARP with wrong src IP address
Date: Thu, 24 Jul 2003 20:11:42 +0200	[thread overview]
Message-ID: <200307242011420101.00BC642D@192.168.128.16> (raw)
In-Reply-To: <200307241836060226.006FACEB@192.168.128.16>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 973 bytes --]

On 24/07/2003 at 18:36 Carlos Velasco wrote:

>>	There are some exceptions for the src IP. Even Linux will
>>not reply if the src IP in incoming probe matches local IP. But
>>may be only Linux preserves the src IP in outgoing probes.

Tested these platforms:

Solaris 8 -> sends src IP address of INTERFACE
Cisco -> sends src IP address of INTERFACE
Windows 2000, XP -> sends src IP address of INTERFACE
Linux 2.6.0-pre1, 2.4.20, 2.4.21 -> sends src IP address of LOOPBACK

Question: ¿What would be the implications of applying my patch or similar to do linux behave like other OS?

>Will open a TAC case tomorrow. I'm interested on testing this in Solaris.

Same tests:

Solaris 8 -> replies the ARP request
Windows 2000, XP -> replies the ARP request
Linux 2.4.21 -> replies the ARP request
Cisco -> NOT replies the ARP request

I will contact Cisco to see why they don't do and if it can be fixed in future releases.

Regards,
Carlos Velasco

  reply	other threads:[~2003-07-24 18:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 15:12 Bug? ARP with wrong src IP address Carlos Velasco
2003-07-23 15:25 ` Carlos Velasco
2003-07-23 23:01 ` Julian Anastasov
2003-07-23 23:34   ` Carlos Velasco
2003-07-24  9:30     ` Bart De Schuymer
2003-07-24 10:38       ` Carlos Velasco
2003-07-24 11:04         ` Julian Anastasov
2003-07-24 15:28           ` Carlos Velasco
2003-07-24 15:54             ` Julian Anastasov
2003-07-24 16:04               ` Carlos Velasco
2003-07-24 16:32                 ` Julian Anastasov
2003-07-24 16:36                   ` Carlos Velasco
2003-07-24 18:11                     ` Carlos Velasco [this message]
2003-07-24 18:37                       ` David S. Miller
2003-07-24 18:54                         ` Carlos Velasco
2003-07-24 16:10               ` David S. Miller
2003-07-25 18:24                 ` Carlos Velasco
2003-07-25 18:46                   ` David S. Miller
2003-07-25 18:36                     ` Carlos Velasco
2003-07-25 18:59                       ` David S. Miller
2003-07-25 19:23                         ` Carlos Velasco

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=200307242011420101.00BC642D@192.168.128.16 \
    --to=carlosev@newipnet.com \
    --cc=bdschuym@pandora.be \
    --cc=ja@ssi.bg \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).