…the node is in MLDv1-compatible mode
…) when the requested MSF is same as the one stored in kernel.
* kame/sys/netinet6/ip6_output.c (ip6_ctloutput): simplified the fix to FreeBSD-SA-04:06.ipv6 (merged from FreeBSD to KAME on 040406). The previous one worried too much about parameters even though we actually validate them in subroutines. This code also is more compatible with other *BSDs, which do copyin within setsockopt().
…oo much even though we actually validate the parameters. This code also is more compatible with other *BSDs, which do copyin within setsockopt().
- we should catch an error from explore_null immediately (behavior change) - we can ignore an intermediate error from explore_numeric_scope (just comment on it) - we should catch an error from explore_copy in the "globcopy" loop; otherwise, we could return an incomplete chain, e.g., even if we saw EAI_MEMORY. (behavior change)
…n't be a target of MSF, although draft-vida-mld-v2-08.txt says only MLDv2 is such exception. (otherwise multicast routing process cannot receive such packets, which prevents it from shifting to MLDv1-compatible-mode)
…roup is newly created via advanced-MSF-API
…mincation of layer2 multicast listening. (ToDo: same fix is necesary for freebsd/sys/netinet/in.c)
- sync qid assignment with openbsd - backout changes to pfaltq_running that didn't go into openbsd-3.5
…ned as "ff02::16"
…nce an MLD packet always has a Router-Alert option
* kame/kame/libinet6/getaddrinfo.c (explore_numeric): re-enabled the special case for AF_INET (use inet_aton instead of inet_pton) as required in RFC3493. getaddrinfo now accepts the "classful" form of IPv4 addresses.