netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jouni@codeaurora.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] bridge: Extend Proxy ARP design to allow optional rules for Wi-Fi
Date: Thu, 05 Mar 2015 14:52:48 -0500 (EST)	[thread overview]
Message-ID: <20150305.145248.37517018117219982.davem@davemloft.net> (raw)
In-Reply-To: <1425466461-1371-1-git-send-email-jouni@codeaurora.org>

From: Jouni Malinen <jouni@codeaurora.org>
Date: Wed,  4 Mar 2015 12:54:21 +0200

> This extends the design in commit 958501163ddd ("bridge: Add support for
> IEEE 802.11 Proxy ARP") with optional set of rules that are needed to
> meet the IEEE 802.11 and Hotspot 2.0 requirements for ProxyARP. The
> previously added BR_PROXYARP behavior is left as-is and a new
> BR_PROXYARP_WIFI alternative is added so that this behavior can be
> configured from user space when required.
> 
> In addition, this enables proxyarp functionality for unicast ARP
> requests for both BR_PROXYARP and BR_PROXYARP_WIFI since it is possible
> to use unicast as well as broadcast for these frames.
> 
> The key differences in functionality:
> 
> BR_PROXYARP:
> - uses the flag on the bridge port on which the request frame was
>   received to determine whether to reply
> - block bridge port flooding completely on ports that enable proxy ARP
> 
> BR_PROXYARP_WIFI:
> - uses the flag on the bridge port to which the target device of the
>   request belongs
> - block bridge port flooding selectively based on whether the proxyarp
>   functionality replied
> 
> Signed-off-by: Jouni Malinen <jouni@codeaurora.org>

Applied to net-next, thanks.

      reply	other threads:[~2015-03-05 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 10:54 [PATCH] bridge: Extend Proxy ARP design to allow optional rules for Wi-Fi Jouni Malinen
2015-03-05 19:52 ` David Miller [this message]

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=20150305.145248.37517018117219982.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jouni@codeaurora.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).