From: James Courtier-Dutton <James@superbug.co.uk>
To: dean gaudet <dean@arctic.org>
Cc: netdev@vger.kernel.org
Subject: Re: gratuitous arp
Date: Sun, 26 Nov 2006 02:05:23 +0000 [thread overview]
Message-ID: <4568F663.7090805@superbug.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0611251526040.8068@twinlark.arctic.org>
dean gaudet wrote:
> hi...
>
> i ran into some problems recently which would have been avoided if my box
> did a gratuitous arp as it brought up all interfaces (the router took
> forever to timeout the ARP entries for interface aliases). so i set about
> looking to see why that wasn't happening.
>
> i either missed it, or there's no code in the kernel to do it -- but
> that's cool, because it's easy enough to do from userland. i'm guessing
> this is the intention.
>
> however my debian and ubuntu boxes aren't doing grat arp and don't seem to
> have options to do it (i do know about using various other tools such as
> arping, send_arp, garp to do it manually).
>
> before i go opening bugs with the distribution folks, could someone chime
> in as to what is the recommended approach these days? did grat arp fall
> out of favour, or is it just a case of userland not keeping up?
>
> thanks
> -dean
Are you 100% sure about this?
Have you done a packet sniff on the network?
A lot of routers ignore gratuitous arp for security reasons.
James
next prev parent reply other threads:[~2006-11-26 2:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-25 23:33 gratuitous arp dean gaudet
2006-11-26 2:05 ` James Courtier-Dutton [this message]
2006-11-26 2:31 ` dean gaudet
2006-11-26 2:53 ` Martin Josefsson
2006-11-26 13:08 ` James Courtier-Dutton
2006-11-26 13:52 ` Krzysztof Oledzki
2006-11-26 17:46 ` dean gaudet
2006-11-26 20:55 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 21:24 Gratuitous ARP Krishna Kumar
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=4568F663.7090805@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=dean@arctic.org \
--cc=netdev@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 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).