| commit | c142b4b7b6138bcd94afae86c3ed1cc84858752c | |
| author | Hasso Tepper <hasso@dragonflybsd.org> | |
| Sun, 14 Oct 2007 18:15:19 +0000 (14 18:15 +0000) | ||
| committer | Hasso Tepper <hasso@dragonflybsd.org> | |
| Sun, 14 Oct 2007 18:15:19 +0000 (14 18:15 +0000) | ||
| tree | 938bdcdcfd5e4b7bd1b70029a1a56eefdf004ee1 | treesnapshot (tar.gz zip) |
| parent | b454a4b7f3ef8880e2fb685da8ef54f29d960010 | commitdiff |
According to RFC2711 routers shouldn't treat all packets with a Router
Alert hop-by-hop option as 'ours', but examine this datagram more closely -
if the router isn't interested in particular protocol it should ignore the
packet and forward it as normal. So, treat packets as 'ours' if they are
for MLD only.
Reported-by: Andrew McDonald <andrew@mcdonald.org.uk>
Obtained-from: KAME
Alert hop-by-hop option as 'ours', but examine this datagram more closely -
if the router isn't interested in particular protocol it should ignore the
packet and forward it as normal. So, treat packets as 'ours' if they are
for MLD only.
Reported-by: Andrew McDonald <andrew@mcdonald.org.uk>
Obtained-from: KAME
| sys/netinet6/ip6_input.c | diffblobblamehistory |