From: Stephen Hemminger <stephen@networkplumber.org>
To: Kyeyoon Park <kyeyoonp@qca.qualcomm.com>
Cc: davem@davemloft.net, jouni@qca.qualcomm.com, netdev@vger.kernel.org
Subject: Re: [PATCH] bridge: Add support for IEEE 802.11 Proxy ARP
Date: Mon, 27 Oct 2014 18:20:32 -0700 [thread overview]
Message-ID: <20141027182032.1c5dcffa@urahara> (raw)
In-Reply-To: <1414100957-8288-1-git-send-email-kyeyoonp@qca.qualcomm.com>
On Thu, 23 Oct 2014 14:49:17 -0700
Kyeyoon Park <kyeyoonp@qca.qualcomm.com> wrote:
> From: Kyeyoon Park <kyeyoonp@codeaurora.org>
>
> This feature is defined in IEEE Std 802.11-2012, 10.23.13. It allows
> the AP devices to keep track of the hardware-address-to-IP-address
> mapping of the mobile devices within the WLAN network.
>
> The AP will learn this mapping via observing DHCP, ARP, and NS/NA
> frames. When a request for such information is made (i.e. ARP request,
> Neighbor Solicitation), the AP will respond on behalf of the
> associated mobile device. In the process of doing so, the AP will drop
> the multicast request frame that was intended to go out to the wireless
> medium.
>
> It was recommended at the LKS workshop to do this implementation in
> the bridge layer. vxlan.c is already doing something very similar.
> The DHCP snooping code will be added to the userspace application
> (hostapd) per the recommendation.
>
> This RFC commit is only for IPv4. A similar approach in the bridge
> layer will be taken for IPv6 as well.
>
> Signed-off-by: Kyeyoon Park <kyeyoonp@codeaurora.org>
Looks good. Maybe at some point VXLAN and bridge should share
more code or at least the same options.
I a little worried that this could be DoS'd.
prev parent reply other threads:[~2014-10-28 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 21:49 [PATCH] bridge: Add support for IEEE 802.11 Proxy ARP Kyeyoon Park
2014-10-27 23:02 ` David Miller
2014-10-28 1:20 ` Stephen Hemminger [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=20141027182032.1c5dcffa@urahara \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=jouni@qca.qualcomm.com \
--cc=kyeyoonp@qca.qualcomm.com \
--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