From: Timo Teras <timo.teras@iki•fi>
To: "David Laight" <David.Laight@ACULAB•COM>
Cc: <netdev@vger•kernel.org>
Subject: Re: [PATCH net-next 2/2] arp: flush arp cache on IFF_NOARP change
Date: Thu, 23 May 2013 15:01:02 +0300 [thread overview]
Message-ID: <20130523150102.43010d84@vostro> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B7249@saturn3.aculab.com>
On Thu, 23 May 2013 11:23:28 +0100
"David Laight" <David.Laight@ACULAB•COM> wrote:
> > IFF_NOARP affects what kind of neighbor entries are created
> > (nud NOARP or nud INCOMPLETE). If the flag changes, flush the arp
> > cache to refresh all entries.
>
> Might someone want to use this to stop further arp table
> entries being created?
> In which case you don't want anything flushed.
I don't think that would make any sense. The entries we have would
expire soon, and the other hosts would not be able to get arp replies
for our host.
Normally this flag is not changed. My use case is with ip gre tunnels,
and starting opennhrp daemon. Opennhrp enables address resolution via
netlink for gre tunnels - it turns off NOARP flag and configures real
ARP off and enables netlink ARPD requests. If before startup there was
traffic to gre tunnel, there will be stale NOARP entries preventing
traffic after daemon is started.
- Timo
next prev parent reply other threads:[~2013-05-23 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 9:58 [PATCH net-next 1/2] net: inform NETDEV_CHANGE callbacks which flags were changed Timo Teräs
2013-05-23 9:58 ` [PATCH net-next 2/2] arp: flush arp cache on IFF_NOARP change Timo Teräs
2013-05-23 10:23 ` David Laight
2013-05-23 12:01 ` Timo Teras [this message]
2013-05-23 16:31 ` [PATCH net-next 1/2] net: inform NETDEV_CHANGE callbacks which flags were changed Ben Hutchings
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=20130523150102.43010d84@vostro \
--to=timo.teras@iki$(echo .)fi \
--cc=David.Laight@ACULAB$(echo .)COM \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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