Lines Matching +refs:test +refs:current +refs:scope

119     * KAME supports node required addresses, and conforms to the scope
206     * zone indices that contain scope types have not been supported yet.
217     * kame/mdnsd has test implementation, which will not be built in
389 only be used for test/debug purposes - for a production environment,
396 specify the scope zone index (link index for a link-local address, or
404 One non-trivial point of the architecture is that the link scope is
405 (theoretically) larger than the interface scope.  That is, two
409 links and interfaces in the same scope type.  The current KAME
428 In the kernel, the link index for a link-local scope address is
479   Embed zone ID determined by the address scope type for 'in6' and the
500 and could be ambiguous with regard to scope.
511 the appropriate scope zone of the destination address by the
514 below), or at least the default scope zone(s) must be configured as a
516 ambiguous address with regard to scope, expecting it is disambiguated
519 unspecified scope zone.  Such a usage is not recommended, but the
534 detected, and the scope zone was originally ambiguous, in6_setscope()
763 					out-of-scope)
765 					(out-of-scope of spec)
852    In any case, addresses that break the scope zone of the
901 	options		"LARGE_LOMTU"		#To test jumbo payload
904 Then you can test jumbo payloads by the ping6 command with -b and -s
934 we have no medium (other than loopback) to test this.  Contact us if you
1017 The current KAME has escaped from the IPv4 netinet logic.  While
2040 at several interoperability test events, and it is known to interoperate
2071 IPsec/IKE implementations.  Their test results are available at
2109 	???: IPv6 scope zone is kept the same
2121 	???: IPv6 scope zone is likely to be different from the real ethernet
2298   Thus, we should write a code to test if a bit-flag is set for a