From: Jesper Dangaard Brouer <jdb@comx.dk>
To: Thomas Graf <tgraf@suug.ch>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: Don't proxy arp respond if iif == rt->dst.dev if private VLAN is disabled
Date: Fri, 10 Feb 2012 15:54:36 +0100 [thread overview]
Message-ID: <1328885676.13582.18.camel@probook> (raw)
In-Reply-To: <1328882831-15300-1-git-send-email-tgraf@suug.ch>
On Fri, 2012-02-10 at 15:07 +0100, Thomas Graf wrote:
> Commit 653241 (net: RFC3069, private VLAN proxy arp support) changed
> the behavior of arp proxy to send arp replies back out on the interface
> the request came in even if the private VLAN feature is disabled.
>
> Previously we checked rt->dst.dev != skb->dev for in scenarios, when
> proxy arp is enabled on for the netdevice and also when individual proxy
> neighbour entries have been added.
>
> This patch adds the check back for the pneigh_lookup() scenario.
>
> Signed-off-by: Thomas Graf <tgraf@suug.ch>
Acked-by: Jesper Dangaard Brouer <hawk@comx.dk>
next prev parent reply other threads:[~2012-02-10 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 14:07 [PATCH] net: Don't proxy arp respond if iif == rt->dst.dev if private VLAN is disabled Thomas Graf
2012-02-10 14:54 ` Jesper Dangaard Brouer [this message]
2012-02-10 20:13 ` David Miller
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=1328885676.13582.18.camel@probook \
--to=jdb@comx.dk \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).