Lines Matching refs:outgoing

299 outgoing interface.  To configure the default outgoing interface, use
519 outgoing interface through another API, which can disambiguate the
532 ambiguous destination, but it still tries to get the outgoing
534 the outgoing packet using in6_selectsrc().  If the interface is
570 the outgoing interface of a packet.  Similarly, the IPV6_PKTINFO or
577 they are too strong for outgoing packets.  For example, consider a
580 we can only specify one of the interfaces for the outgoing packet with
609   + To disambiguate scoped addresses of outgoing packets,
610     * if it is okay to just specify the outgoing interface, use the
627 syntax, as documented in RFC4007.  You can specify the outgoing link,
628 by using the name of the outgoing interface as the link, like
640 syntax.  In this case, you can specify outgoing link, by using the name
641 of the outgoing interface like "fe80::1%ne0" (sorry for the duplicated
652 specify the outgoing interface).  However, you can't always expect such
653 options.  Additionally, specifying the outgoing "interface" is in
654 theory an overspecification as a way to specify the outgoing "link"
656 described above.  This should apply to the case where the outgoing
814 The KAME kernel chooses the source address for an outgoing packet
824 3. otherwise, the kernel first tries to find the outgoing interface of
854    destination, or addresses whose zone do not contain the outgoing
1144 If you would like to use AF_INET6 socket for both IPv4 and IPv6 outgoing
1152 When writing applications that make outgoing connections, story goes much
1190 KAME/FreeBSD3x supports outgoing connection to IPv4 mapped address
1236 When getsockopt(IPV6_V6ONLY) is 0 for a socket, you can make an outgoing
1241 address for outgoing traffic.
1320 - By enabling kernel support for IPv4 mapped address (outgoing direction),
2163   normal routing table, and C (global side) will be picked for any outgoing