linux.git/net/bridge/br_input.c, branch v3.13

bridge: pass correct vlan id to multicast code

2013-10-29T21:40:08+00:00

Currently multicast code attempts to extrace the vlan id from
the skb even when vlan filtering is disabled.  This can lead
to mdb entries being created with the wrong vlan id.
Pass the already extracted vlan id to the multicast
filtering code to make the correct id is used in
creation as well as lookup.

Signed-off-by: Vlad Yasevich 
Acked-by: Toshiaki Makita 
Signed-off-by: David S. Miller

bridge: separate querier and query timer into IGMP/IPv4 and MLD/IPv6 ones

2013-08-30T19:24:37+00:00

Currently we would still potentially suffer multicast packet loss if there
is just either an IGMP or an MLD querier: For the former case, we would
possibly drop IPv6 multicast packets, for the latter IPv4 ones. This is
because we are currently assuming that if either an IGMP or MLD querier
is present that the other one is present, too.

This patch makes the behaviour and fix added in
"bridge: disable snooping if there is no querier" (b00589af3b04)
to also work if there is either just an IGMP or an MLD querier on the
link: It refines the deactivation of the snooping to be protocol
specific by using separate timers for the snooped IGMP and MLD queries
as well as separate timers for our internal IGMP and MLD queriers.

Signed-off-by: Linus Lüssing 
Signed-off-by: David S. Miller

bridge: disable snooping if there is no querier

2013-08-01T00:40:21+00:00

If there is no querier on a link then we won't get periodic reports and
therefore won't be able to learn about multicast listeners behind ports,
potentially leading to lost multicast packets, especially for multicast
listeners that joined before the creation of the bridge.

These lost multicast packets can appear since c5c23260594
("bridge: Add multicast_querier toggle and disable queries by default")
in particular.

With this patch we are flooding multicast packets if our querier is
disabled and if we didn't detect any other querier.

A grace period of the Maximum Response Delay of the querier is added to
give multicast responses enough time to arrive and to be learned from
before disabling the flooding behaviour again.

Signed-off-by: Linus Lüssing 
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: add missing vid to br_mdb_get()

2013-03-07T21:32:19+00:00

Obviously, vid should be considered when searching for multicast
group.

Cc: Vlad Yasevich 
Cc: Stephen Hemminger 
Cc: "David S. Miller" 
Signed-off-by: Cong Wang 
Acked-by: Vlad Yasevich 
Signed-off-by: David S. Miller

bridge: Add vlan to unicast fdb entries

2013-02-14T00:42:15+00:00

This patch adds vlan to unicast fdb entries that are created for
learned addresses (not the manually configured ones).  It adds
vlan id into the hash mix and uses vlan as an addditional parameter
for an entry match.

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

bridge: Implement vlan ingress/egress policy with PVID.

2013-02-14T00:42:15+00:00

At ingress, any untagged traffic is assigned to the PVID.
Any tagged traffic is filtered according to membership bitmap.

At egress, if the vlan matches the PVID, the frame is sent
untagged.  Otherwise the frame is sent tagged.

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

bridge: Verify that a vlan is allowed to egress on given port

2013-02-14T00:41:46+00:00

When bridge forwards a frame, make sure that a frame is allowed
to egress on that port.

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

bridge: Validate that vlan is permitted on ingress

2013-02-14T00:41:46+00:00

When a frame arrives on a port or transmitted by the bridge,
if we have VLANs configured, validate that a given VLAN is allowed
to enter the bridge.

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