All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Griffioen <arno@attic.nerdnet.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Incorrect source address in ARP request. Anyone seen
Date: Tue, 18 Mar 2003 07:02:54 +0000	[thread overview]
Message-ID: <marc-lartc-104797109823352@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104790862226037@msgid-missing>

> requests with src 17.70.0.1? Linux ARP follows the routing and will
> reply in this case (when used in place of the router).

Yes that's true. Unfortunately it seems that Linux is one of the few
who implement this behaviour. Others seem to hold the view that
ARP is a link-level protocol and as such only has any relevance for
the scope defined on the interface itself.

So even though it's technically possible and legal to do so according
to the RFC, it's unfortunately not often used in practice..

> to handle such case. The problem comes only if "router decides not
> to accept ARP from valid source IP from valid input device".

Which seems to cover almost all dedicated routers (eg. Cisco) and probably 
quite a few other OS'es too.

> 	Take a look at arp_solicit()

Saw that.. I'll mangle it a bit so it will only send out the
link address. That way it's compatible with what other devices expect.

Thanx for the help! At least I know I hadn't screwed up something.

								Bye, Arno.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-03-18  7:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17 13:42 [LARTC] Incorrect source address in ARP request. Anyone seen this? Arno Griffioen
2003-03-17 22:27 ` [LARTC] Incorrect source address in ARP request. Anyone seen Julian Anastasov
2003-03-18  7:02 ` Arno Griffioen [this message]
2003-03-18 11:45 ` Julian Anastasov

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-104797109823352@msgid-missing \
    --to=arno@attic.nerdnet.nl \
    --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.