linux-toradex.git/net/bridge/br_sysfs_if.c, branch v4.1.5

bridge: Extend Proxy ARP design to allow optional rules for Wi-Fi

2015-03-05T19:52:23+00:00

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 
Signed-off-by: David S. Miller

bridge: Add support for IEEE 802.11 Proxy ARP

2014-10-27T23:02:04+00:00

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 
Signed-off-by: David S. Miller

bridge: Keep track of ports capable of automatic discovery.

2014-05-16T21:06:33+00:00

By default, ports on the bridge are capable of automatic
discovery of nodes located behind the port.  This is accomplished
via flooding of unknown traffic (BR_FLOOD) and learning the
mac addresses from these packets (BR_LEARNING).
If the above functionality is disabled by turning off these
flags, the port requires static configuration in the form
of static FDB entries to function properly.

This patch adds functionality to keep track of all ports
capable of automatic discovery.  This will later be used
to control promiscuity settings.

Acked-by: Michael S. Tsirkin 
Signed-off-by: Vlad Yasevich 
Signed-off-by: David S. Miller

bridge: Turn flag change macro into a function.

2014-05-16T21:06:32+00:00

Turn the flag change macro into a function to allow
easier updates and to reduce space.

Acked-by: Michael S. Tsirkin 
Signed-off-by: Vlad Yasevich 
Signed-off-by: David S. Miller

bridge: change "foo* bar" to "foo *bar"

2013-12-20T00:27:26+00:00

"foo * bar" should be "foo *bar".

Signed-off-by: Tan Xiaojun 
Signed-off-by: David S. Miller

bridge: add space before '(/{', after ',', etc.

2013-12-20T00:27:26+00:00

Spaces required before the open parenthesis '(', before the open
brace '{', after that ',' and around that '?/:'.

Signed-off-by: Tan Xiaojun 
Signed-off-by: David S. Miller

bridge: Add a flag to control unicast packet flood.

2013-06-11T09:04:32+00:00

Add a flag to control flood of unicast traffic.  By default, flood is
on and the bridge will flood unicast traffic if it doesn't know
the destination.  When the flag is turned off, unicast traffic
without an FDB will not be forwarded to the specified port.

Signed-off-by: Vlad Yasevich 
Reviewed-by: Michael S. Tsirkin 
Signed-off-by: David S. Miller

bridge: Add flag to control mac learning.

2013-06-11T09:04:32+00:00

Allow user to control whether mac learning is enabled on the port.
By default, mac learning is enabled.  Disabling mac learning will
cause new dynamic FDB entries to not be created for a particular port.

Signed-off-by: Vlad Yasevich 
Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

bridge: implement multicast fast leave

2012-12-05T21:24:45+00:00

V3: make it a flag
V2: make the toggle per-port

Fast leave allows bridge to immediately stops the multicast
traffic on the port receives IGMP Leave when IGMP snooping is enabled,
no timeouts are observed.

Cc: Herbert Xu 
Cc: Stephen Hemminger 
Cc: "David S. Miller" 
Signed-off-by: Cong Wang

bridge: implement multicast fast leave

2012-12-05T21:01:27+00:00

V2: make the toggle per-port

Fast leave allows bridge to immediately stops the multicast
traffic on the port receives IGMP Leave when IGMP snooping is enabled,
no timeouts are observed.

Cc: Herbert Xu 
Cc: Stephen Hemminger 
Cc: "David S. Miller" 
Signed-off-by: Cong Wang 
Signed-off-by: David S. Miller