Lines Matching refs:IPv6
16 1. IPv6
36 1.12 IPv4 mapped address and IPv6 wildcard socket
69 3.2 IPv6-to-IPv4 header translator
82 6. Mobile IPv6
85 6.3 Old Mobile IPv6 code
89 1. IPv6
93 The KAME kit conforms, or tries to conform, to the latest set of IPv6
107 RFC1886: DNS Extensions to support IPv6
109 RFC1981: Path MTU Discovery for IPv6
110 RFC2080: RIPng for IPv6
115 RFC2292: Advanced Sockets API for IPv6
119 RFC2373: IPv6 Addressing Architecture
122 RFC2374: An IPv6 Aggregatable Global Unicast Address Format
124 RFC2375: IPv6 Multicast Address Assignments
126 RFC2428: FTP Extensions for IPv6 and NATs
129 RFC2460: IPv6 specification
130 RFC2461: Neighbor discovery for IPv6
132 RFC2462: IPv6 Stateless Address Autoconfiguration
134 RFC2463: ICMPv6 for IPv6 specification
136 RFC2464: Transmission of IPv6 Packets over Ethernet Networks
137 RFC2465: MIB for IPv6: Textual Conventions and General Group
138 * Necessary statistics are gathered by the kernel. Actual IPv6 MIB
140 RFC2466: MIB for IPv6: ICMPv6 group
141 * Necessary statistics are gathered by the kernel. Actual IPv6 MIB
143 RFC2467: Transmission of IPv6 Packets over FDDI Networks
144 RFC2472: IPv6 over PPP
145 RFC2492: IPv6 over ATM Networks
147 RFC2497: Transmission of IPv6 packet over ARCnet Networks
148 RFC2545: Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
157 RFC2675: IPv6 Jumbograms
159 RFC2710: Multicast Listener Discovery for IPv6
160 RFC2711: IPv6 router alert option
161 RFC2732: Format for Literal IPv6 Addresses in URL's
164 RFC2874: DNS Extensions to Support IPv6 Address Aggregation and Renumbering
168 RFC2893: Transition Mechanisms for IPv6 Hosts and Routers
174 RFC2894: Router renumbering for IPv6
175 RFC3041: Privacy Extensions for Stateless Address Autoconfiguration in IPv6
176 RFC3056: Connection of IPv6 Domains via IPv4 Clouds
181 RFC3142: An IPv6-to-IPv4 transport relay translator
186 the ip6.arpa domain (with the nibble format) for IPv6 reverse
188 RFC3484: Default Address Selection for IPv6
191 RFC3493: Basic Socket Interface Extensions for IPv6
192 * IPv4 mapped address (3.7) and special behavior of IPv6 wildcard bind
200 RFC3542: Advanced Sockets API for IPv6 (revised)
204 RFC4007: IPv6 Scoped Address Architecture
209 draft-ietf-ipngwg-icmp-name-lookups-09: IPv6 Name Lookups Through ICMP
215 A revised version of RFC2362, which includes the IPv6 specific
221 draft-ietf-ipngwg-icmp-v3-02.txt: ICMPv6 for IPv6 specification (revised)
224 Disconnecting TCP connection toward IPv6 anycast address
225 draft-ietf-ipv6-rfc2462bis-06.txt: IPv6 Stateless Address
228 Possible abuse against IPv6 transition technologies (expired)
236 draft-itojun-ipv6-flowlabel-api-01.txt: Socket API for IPv6 flow label field
247 Duplicated Address Detection (DAD) will be performed when an IPv6 address
260 uniquely assigned (e.g., EUI-64 for an Ethernet interface), IPv6
264 structure for the interface. Every IPv6 I/O operation in the kernel
266 being sent to the "disabled" interface. Whether the IPv6 operation is
296 IPv6 on-link determination rule (RFC2461) is quite different from
308 consider a destination that has both IPv4 and IPv6 addresses but is
309 only reachable via IPv4. Since our getaddrinfo(3) prefers IPv6 by
311 tries to connect to the IPv6 address. If we turn on RFC 2461 6.3.6
396 IPv6 uses scoped addresses. It is therefore very important to
398 site index for a site-local address) with an IPv6 address. Without a
399 zone index, a scoped IPv6 address is ambiguous to the kernel, and
430 embedded into the 2nd 16bit-word (the 3rd and 4th bytes) in the IPv6
438 implementation). The embedded index enables us to identify IPv6
614 * otherwise, sorry but you lose. Please rush the IETF IPv6
621 will return IPv6 addresses with the 2nd 16bit-word filled in. The
626 getaddrinfo(3) and getnameinfo(3) support an extended numeric IPv6
639 Most of user applications now support the extended numeric IPv6
645 the IPv6 default route by hand, you can type like
666 The KAME kit implements most of the IPv6 stateless address
676 IPv6 link-local address is generated from IEEE802 address (ethernet MAC
677 address). Each of interface is assigned an IPv6 link-local address
696 If an interface is not capable of handling IPv6 (such as lack of multicast
710 In IPv6 specification, nodes are separated into two categories:
716 is in operation. IPv6 specification defines behavior for "host" and "router"
746 Note that the IPv6 specification assumes the following items and that
806 If you would like to configure an IPv4-in-IPv6 tunnel with gif interface,
807 read gif(4) carefully. You may need to remove IPv6 link-local address
893 KAME supports the Jumbo Payload hop-by-hop option used to send IPv6
911 The IPv6 specification requires that the Jumbo Payload option must not
917 If KAME kernel receives an IPv6 packet, it checks the frame length of
919 length field of the IPv6 header or in the value of the Jumbo Payload
948 IPv6 header + link-layer header. Therefore, it must be expanded to at least
953 - We mistakingly check for ip6_plen field of IPv6 header for packet payload
961 IPv6 specification allows arbitrary number of extension headers to
962 be placed onto packets. If we implement IPv6 packet processing
970 (including the IPv6 header) in each incoming packet, in order to
979 number of IPsec headers, kernel stack may blow up. IPsec-over-IPv6 is okay.
1005 For userland programming, we support IPv6 socket API as specified in
1008 TCP/UDP over IPv6 is available and quite stable. You can enjoy "telnet",
1010 independent. That is, they automatically chooses IPv4 or IPv6
1020 if_output() since routers must not divide IPv6 packets into fragments.
1062 1.12 IPv4 mapped address and IPv6 wildcard socket
1065 of IPv6 wildcard bind socket (3.8). The spec allows you to:
1075 between IPv4 and IPv6. You can perform wildcard bind on both of the address
1115 If a server application would like to accept IPv4 and IPv6 connections,
1121 and IPv6 connections will be accepted by AF_INET6 socket (NOTE: KAME/BSDI4
1124 If you try to support IPv6 traffic only and would like to reject IPv4
1133 Advise to application implementers: to implement a portable IPv6 application
1134 (which works on multiple IPv6 kernels), we believe that the following
1141 - Some of the IPv6 stack is shipped with buggy getaddrinfo(). Ship a minimal
1144 If you would like to use AF_INET6 socket for both IPv4 and IPv6 outgoing
1148 it does not handle scoped IPv6 addresses at all. For IPv6 name resolution
1246 which was derived from NRL IPv6/IPsec stack. We guess it supports IPv4 mapped
1267 which was derived from NRL IPv6/IPsec stack.
1298 - If a protocol on top of IPv4 is defined differently with IPv6, we need to be
1305 use EPSV/EPRT or LPSV/LPRT; /*IPv6*/
1314 use EPSV/EPRT or LPSV/LPRT; /*IPv6*/
1321 servers on the kernel can be hosed by IPv6 native packet that has IPv4
1322 mapped address in IPv6 header source, and can generate unwanted IPv4 packets.
1330 This is to avoid malicious use of IPv4 mapped address in IPv6 native
1345 (1) SIIT translators require end nodes in the SIIT cloud to be IPv6-only.
1348 dual stack network. (3) KAME stack filters out IPv6 packets with IPv4
1354 things. For example, SIIT document asks IPv6-only (meaning no IPv4 code)
1356 construct IPv4 IPsec headers, that is not an IPv6-only node, it is a dual-stack
1388 If you look at multiple IPv6 implementations, you will be able to see
1401 Some of IPv6 transition technologies embed IPv4 address into IPv6 address.
1408 To name a few, these address ranges can be used to hose an IPv6 implementation,
1411 IPv4 address (if they are in IPv6 native packet header, they are malicious)
1420 IPv4 address (if they are in IPv6 native packet header, they are malicious).
1428 If we see IPv6 packets with IPv4 mapped address (::ffff:0.0.0.0/96) in the
1432 IPv6 specifications do not talk very much about IPv6 unspecified address (::)
1433 in the IPv6 source address field. Clarification is in progress.
1435 - IPv6 unspecified address can be used in IPv6 source address field, if and
1437 include, but may not be limited to, (1) MLD while no IPv6 address is assigned
1439 - If IPv6 TCP packet has IPv6 unspecified address, it is an attack attempt.
1443 consensus among ipngwg for those. (1) Mobile IPv6 home address option,
1448 KAME kernel will reject packets with certain source/destination address in IPv6
1449 base header, or IPv6 routing header. Also, KAME default configuration file
1458 RFC2373 section 2.8 talks about required addresses for an IPv6
1527 Background: RFC2292 document is based on RFC1883 IPv6, and it uses
1528 strict/loose bitmap. RFC3542 document is based on RFC2460 IPv6, and it has
1530 RFC2460 IPv6, and lacks support for strict/loose bitmap.
1546 - IPv6 transport support (queries/responses over IPv6). Most of BSD official
1730 We categorize IPv4/IPv6 translator into 4 types.
1733 it possible to establish a connection from an IPv6 host in an IPv6
1738 ocean to an IPv6 host in an IPv6 island.
1742 to an IPv6 host in the IPv6 ocean.
1745 possible to establish a connection from an IPv6 host in the IPv6 ocean
1754 FAITH will reserve an IPv6 address prefix, and relay TCP connection
1757 For example, if the reserved IPv6 prefix is 3ffe:0501:0200:ffff::, and
1758 the IPv6 destination for TCP connection is 3ffe:0501:0200:ffff::163.221.202.12,
1766 | IPv6 TCP toward 3ffe:0501:0200:ffff::163.221.202.12
1767 source IPv6 node
1773 3.2 IPv6-to-IPv4 header translator
1788 to replace it. IPv6 support for IPsec is, therefore, lacking on KAME/OpenBSD.
1830 IPsec module is implemented as "hooks" to the standard IPv4/IPv6
1856 - Path MTU discovery does not work across IPv6 IPsec tunnel gateway due to
1989 IPv4 TOS field (or, IPv6 traffic class field) will be copied from inner
2110 ???: IPv6 scope zone is kept the same
2122 ???: IPv6 scope zone is likely to be different from the real ethernet
2208 ALTQ in KAME supports IPv6.
2227 6. Mobile IPv6