summaryrefslogtreecommitdiffstats
path: root/drivers/net/wan/pc300too.c
diff options
context:
space:
mode:
authorKyeyoon Park <kyeyoonp@codeaurora.org>2014-10-23 14:49:17 -0700
committerDavid S. Miller <davem@davemloft.net>2014-10-27 19:02:04 -0400
commit958501163ddd6ea22a98f94fa0e7ce6d4734e5c4 (patch)
tree5559ec9c425fc5e8092961a2b82b2cafd8239c75 /drivers/net/wan/pc300too.c
parentb8901ac319768cdd3afa060787503e0c405f9607 (diff)
downloadlinux-958501163ddd6ea22a98f94fa0e7ce6d4734e5c4.tar.bz2
bridge: Add support for IEEE 802.11 Proxy ARP
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> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/wan/pc300too.c')
0 files changed, 0 insertions, 0 deletions