linux-toradex.git/include/linux/igmp.h, branch v4.6-rc6

igmp: Namespacify igmp_qrv sysctl knob

2016-02-11T14:59:22+00:00

Signed-off-by: Nikolay Borisov 
Signed-off-by: David S. Miller

igmp: Namespaceify igmp_llm_reports sysctl knob

2016-02-11T14:59:22+00:00

This was initially introduced in df2cf4a78e488d26 ("IGMP: Inhibit
reports for local multicast groups") by defining the sysctl in the
ipv4_net_table array, however it was never implemented to be
namespace aware. Fix this by changing the code accordingly.

Signed-off-by: David S. Miller

igmp: Namespaceify igmp_max_msf sysctl knob

2016-02-11T14:59:22+00:00

Signed-off-by: Nikolay Borisov 
Signed-off-by: David S. Miller

igmp: Namespaceify igmp_max_memberships sysctl knob

2016-02-11T14:59:22+00:00

Signed-off-by: Nikolay Borisov 
Signed-off-by: David S. Miller

net/ipv4: Pass proto as u8 instead of u16 in ip_check_mc_rcu

2015-09-29T23:27:47+00:00

This patch updates ip_check_mc_rcu so that protocol is passed as a u8
instead of a u16.

The motivation is just to avoid any unneeded type transitions since some
systems will require an instruction to zero extend a u8 field to a u16.
Also it makes it a bit more readable as to the fact that protocol is a u8
so there are no byte ordering changes needed to pass it.

Signed-off-by: Alexander Duyck 
Signed-off-by: David S. Miller

IGMP: Inhibit reports for local multicast groups

2015-08-28T20:28:47+00:00

The range of addresses between 224.0.0.0 and 224.0.0.255 inclusive, is
reserved for the use of routing protocols and other low-level topology
discovery or maintenance protocols, such as gateway discovery and
group membership reporting.  Multicast routers should not forward any
multicast datagram with destination addresses in this range,
regardless of its TTL.

Currently, IGMP reports are generated for this reserved range of
addresses even though a router will ignore this information since it
has no purpose.  However, the presence of reserved group addresses in
an IGMP membership report uses up network bandwidth and can also
obscure addresses of interest when inspecting membership reports using
packet inspection or debug messages.

Although the RFCs for the various version of IGMP (e.g.RFC 3376 for
v3) do not specify that the reserved addresses be excluded from
membership reports, it should do no harm in doing so.  In particular
there should be no adverse effect in any IGMP snooping functionality
since 224.0.0.x is specifically excluded as per RFC 4541 (IGMP and MLD
Snooping Switches Considerations) section 2.1.2. Data Forwarding
Rules:

    2) Packets with a destination IP (DIP) address in the 224.0.0.X
       range which are not IGMP must be forwarded on all ports.

IGMP reports for local multicast groups can now be optionally
inhibited by means of a system control variable (by setting the value
to zero) e.g.:
    echo 0 > /proc/sys/net/ipv4/igmp_link_local_mcast_reports

To retain backwards compatibility the previous behaviour is retained
by default on system boot or reverted by setting the value back to
non-zero e.g.:
    echo 1 >  /proc/sys/net/ipv4/igmp_link_local_mcast_reports

Signed-off-by: Philip Downey 
Signed-off-by: David S. Miller

net: Export IGMP/MLD message validation code

2015-05-04T18:49:23+00:00

With this patch, the IGMP and MLD message validation functions are moved
from the bridge code to IPv4/IPv6 multicast files. Some small
refactoring was done to enhance readibility and to iron out some
differences in behaviour between the IGMP and MLD parsing code (e.g. the
skb-cloning of MLD messages is now only done if necessary, just like the
IGMP part always did).

Finally, these IGMP and MLD message validation functions are exported so
that not only the bridge can use it but batman-adv later, too.

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

ipv4: implement igmp_qrv sysctl to tune igmp robustness variable

2014-09-05T05:26:14+00:00

As in IPv6 people might increase the igmp query robustness variable to
make sure unsolicited state change reports aren't lost on the network. Add
and document this new knob to igmp code.

RFCs allow tuning this parameter back to first IGMP RFC, so we also use
this setting for all counters, including source specific multicast.

Also take over sysctl value when upping the interface and don't reuse
the last one seen on the interface.

Cc: Flavio Leitner 
Signed-off-by: Hannes Frederic Sowa 
Acked-by: Flavio Leitner 
Signed-off-by: David S. Miller

net: convert resend IGMP to notifier event

2013-07-23T23:52:47+00:00

Until now, bond_resend_igmp_join_requests() looks for vlans attached to
bonding device, bridge where bonding act as port manually. It does not
care of other scenarios, like stacked bonds or team device above. Make
this more generic and use netdev notifier to propagate the event to
upper devices and to actually call ip_mc_rejoin_groups().

Signed-off-by: Jiri Pirko 
Acked-by: Veaceslav Falico 
Signed-off-by: David S. Miller

igmp: hash a hash table to speedup ip_check_mc_rcu()

2013-06-12T07:25:23+00:00

After IP route cache removal, multicast applications using
a lot of multicast addresses hit a O(N) behavior in ip_check_mc_rcu()

Add a per in_device hash table to get faster lookup.

This hash table is created only if the number of items in mc_list is
above 4.

Reported-by: Shawn Bohrer 
Signed-off-by: Eric Dumazet 
Tested-by: Shawn Bohrer 
Reviewed-by: Cong Wang 
Signed-off-by: David S. Miller