Lines Matching refs:outgoing

298 outgoing interface.  To configure the default outgoing interface, use
518 outgoing interface through another API, which can disambiguate the
531 ambiguous destination, but it still tries to get the outgoing
533 the outgoing packet using in6_selectsrc().  If the interface is
569 the outgoing interface of a packet.  Similarly, the IPV6_PKTINFO or
576 they are too strong for outgoing packets.  For example, consider a
579 we can only specify one of the interfaces for the outgoing packet with
608   + To disambiguate scoped addresses of outgoing packets,
609     * if it is okay to just specify the outgoing interface, use the
626 syntax, as documented in RFC4007.  You can specify the outgoing link,
627 by using the name of the outgoing interface as the link, like
639 syntax.  In this case, you can specify outgoing link, by using the name
640 of the outgoing interface like "fe80::1%ne0" (sorry for the duplicated
651 specify the outgoing interface).  However, you can't always expect such
652 options.  Additionally, specifying the outgoing "interface" is in
653 theory an overspecification as a way to specify the outgoing "link"
655 described above.  This should apply to the case where the outgoing
813 The KAME kernel chooses the source address for an outgoing packet
823 3. otherwise, the kernel first tries to find the outgoing interface of
853    destination, or addresses whose zone do not contain the outgoing
1143 If you would like to use AF_INET6 socket for both IPv4 and IPv6 outgoing
1151 When writing applications that make outgoing connections, story goes much
1189 KAME/FreeBSD3x supports outgoing connection to IPv4 mapped address
1235 When getsockopt(IPV6_V6ONLY) is 0 for a socket, you can make an outgoing
1240 address for outgoing traffic.
1319 - By enabling kernel support for IPv4 mapped address (outgoing direction),
2162   normal routing table, and C (global side) will be picked for any outgoing