an INITIAL-CONTACT if we have contacted the peer. This matches the Sun IKE behavior, and makes rekeying work much better when the peer restarts.
create/update routing entry with the same value in rt_key and rt_gateway. response to NetBSD PR 4827. experimental.
routing entry with rt_key == rt_gateway. this case happens only with: - bogus host route entry toward onlink destination (like on 10.0.0.1/24, 10.0.0.2 -> outgoing router) - bogus ntework route entry toward (part of) onlink destinations (like on 10.0.0.1/24, 10.0.0.128/25 -> outgoign router). not sure if it is mandatory to do this, but there was NetBSD PR on this with report of kernel panic (not sure if the issue still persists)
* kame/sys/netinet6/nd6.c (nd6_p2p_rtrequest): removed. It was introduced long long ago, and is not necessary any more, especially after the recent clarification on the address/prefix management.
(embedscope uses in6pcb *, but is more like non-pcb function)
the recent clarification on address/prefix management.
XXX maybe we should move prototypes to in6_var.h, if it is not just for pcb?
generic on scopes. - clear embedded scope ID under !SCOPEDROUTING cases only.
(not only consider link-local addresses, but consider other scoped addresses as well)
packet processing path, to avoid /var from get filluped with with bogus packet storms. * sys/netinet6/icmp6.c: supply new sysctl net.inet6.icmp6.nd6_debug, to turn on/off error/warning messages on inbonud ND/ICMPv6 packets. disabled by default, can be enabled by default if you have "options ND6_DEBUG". * sys/netinet6: OLD_LOOPBACK_IF is no longer supported (see changelog on 2000/7/30).
bogus packet storms). supply a variable nd6_debug so that we can change logging at runtime.
* kame/sys/netinet6/in6.c (in6_update_ifa): always set the destination address when specified regardless of the type of the interface. This would solve a problem that bsdi3 could not add a route that has ::1 as the gateway (bsdi3 specific, maybe). This fix was in response to a report from Tomomi Suzuki <email@example.com>.
the type of the interface. this would solve a problem that bsdi3 could not add a route that has ::1 as the gateway (bsdi3 specific, maybe). in response to a report from Tomomi Suzuki <firstname.lastname@example.org>.