summaryrefslogtreecommitdiffstats
path: root/net/dns_resolver
diff options
context:
space:
mode:
authorWilliam Manley <william.manley@youview.com>2013-08-06 19:03:13 +0100
committerDavid S. Miller <davem@davemloft.net>2013-08-09 11:27:46 -0700
commitcab70040dfd95ee32144f02fade64f0cb94f31a0 (patch)
tree0deaa52ea74518733b85c0527d57f3e1a3b11d6d /net/dns_resolver
parentb20903f2a9ee5bd9ca80ad72867c8d137aaf4d62 (diff)
downloadop-kernel-dev-cab70040dfd95ee32144f02fade64f0cb94f31a0.zip
op-kernel-dev-cab70040dfd95ee32144f02fade64f0cb94f31a0.tar.gz
net: igmp: Reduce Unsolicited report interval to 1s when using IGMPv3
If an IGMP join packet is lost you will not receive data sent to the multicast group so if no data arrives from that multicast group in a period of time after the IGMP join a second IGMP join will be sent. The delay between joins is the "IGMP Unsolicited Report Interval". Previously this value was hard coded to be chosen randomly between 0-10s. This can be too long for some use-cases, such as IPTV as it can cause channel change to be slow in the presence of packet loss. The value 10s has come from IGMPv2 RFC2236, which was reduced to 1s in IGMPv3 RFC3376. This patch makes the kernel use the 1s value from the later RFC if we are operating in IGMPv3 mode. IGMPv2 behaviour is unaffected. Tested with Wireshark and a simple program to join a (non-existent) multicast group. The distribution of timings for the second join differ based upon setting /proc/sys/net/ipv4/conf/eth0/force_igmp_version. Signed-off-by: William Manley <william.manley@youview.com> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org> Acked-by: Benjamin LaHaise <bcrl@kvack.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/dns_resolver')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud