Lines Matching refs:behavior

192     * IPv4 mapped address (3.7) and special behavior of IPv6 wildcard bind
257 behavior when DAD fails (i.e., duplicate is detected): if the
282 IFF_SIMPLEX behavior.  For example, you may need to check source MAC
297 assumptions in BSD IPv4 network code.  To implement the behavior in
340   behavior in RFC2461.
342   SHOULD behavior in RFC2461.
389 debug behavior during bootstrap).  nd6_debug configuration should
421 underway to define behavior of routers at site border, but, we have
599 support the behavior above at this moment.
604   kernel behavior described above.
716 is in operation.  IPv6 specification defines behavior for "host" and "router"
725 behavior can be controlled by the net.inet6.ip6.accept_rtadv sysctl
741 Additionally, ndp(8) command can be used to control the behavior
1078 RFC2553/3493 describes IPv4 mapped address (3.7) and special behavior
1093 code from different origin.  The following table summarizes the behavior.
1111 configure the behavior.
1117 between AF_INET/INET6 wildcard bind like ordering constraint, and (4) behavior
1121 about the behavior in the kernel.  Using getaddrinfo() is the safest way.
1126 We supply a tool called "bindtest" that explores the behavior of
1143 the section (itojun) dislikes special behavior of AF_INET6 wildcard bind.
1191 option to disable it.  You can enable/disable the behavior with sysctl
1222 wildcard bind (disabled by default).  Kernel behavior can be summarized as
1229   separate.  The behavior is similar to what described in 1.12.1.
1233 configuration at in6pcb creation time.  To change per-socket behavior, you
1235 will not change the behavior or sockets that are already opened.
1266 NRL inpcb layer supports special behavior of AF_INET6 wildcard socket.
1267 There is no way to disable the behavior.
1288 KAME/OpenBSD disables special behavior on AF_INET6 wildcard bind for
1291 stack as well, however, the behavior is different due to OpenBSD's security
1294 As a result the behavior of KAME/OpenBSD is similar to KAME/BSDI3 and
1536 There are few (or couple of) incompatible behavior in RFC2292 binary backward
1816 difference in behavior.
2017 Note that the behavior is configurable in per-node manner, not per-SA manner
2021 The behavior is summarized as follows (see source code for more detail):
2038 - if both IPsec tunnel endpoint are capable of ECN-friendly behavior,
2043 The default behavior is "ECN forbidden" (sysctl value 0).
2112 to recompile your kernel to switch the behavior.