From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net, mleitner@redhat.com
Subject: Re: [patch net] ipv6: do not create neighbor entries for local delivery
Date: Wed, 30 Jan 2013 20:26:39 -0500 (EST) [thread overview]
Message-ID: <20130130.202639.978642110493467876.davem@davemloft.net> (raw)
In-Reply-To: <20130130082608.GA1604@minipsycho.orion>
From: Jiri Pirko <jiri@resnulli.us>
Date: Wed, 30 Jan 2013 09:26:08 +0100
> From: Marcelo Ricardo Leitner <mleitner@redhat.com>
>
> They will be created at output, if ever needed. This avoids creating
> empty neighbor entries when TPROXYing/Forwarding packets for addresses
> that are not even directly reachable.
>
> Note that IPv4 already handles it this way. No neighbor entries are
> created for local input.
>
> Tested by myself and customer.
>
> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
> Signed-off-by: Marcelo Ricardo Leitner <mleitner@redhat.com>
Applied and queued up for -stable, thanks.
next prev parent reply other threads:[~2013-01-31 1:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 8:26 [patch net] ipv6: do not create neighbor entries for local delivery Jiri Pirko
2013-01-31 1:26 ` David Miller [this message]
2013-08-08 18:45 ` Debabrata Banerjee
2013-08-08 19:01 ` Hannes Frederic Sowa
2013-08-08 19:02 ` Marcelo Ricardo Leitner
2013-08-08 19:06 ` Hannes Frederic Sowa
2013-08-08 19:11 ` Marcelo Ricardo Leitner
2013-08-08 19:16 ` Hannes Frederic Sowa
2013-08-08 19:23 ` Marcelo Ricardo Leitner
2013-08-08 19:19 ` Debabrata Banerjee
2013-08-08 19:47 ` Hannes Frederic Sowa
2013-08-08 20:16 ` Hannes Frederic Sowa
2013-08-08 20:45 ` Marcelo Ricardo Leitner
2013-08-08 20:46 ` Marcelo Ricardo Leitner
2013-08-12 18:09 ` Marcelo Ricardo Leitner
2013-08-12 22:26 ` Hannes Frederic Sowa
2013-08-13 12:48 ` Marcelo Ricardo Leitner
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=20130130.202639.978642110493467876.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).