#
0b3745db |
| 08-Mar-2021 |
christos <christos@NetBSD.org> |
no need for ip6_id.c...
|
#
63ecc40c |
| 08-Feb-2018 |
maxv <maxv@NetBSD.org> |
Move udp6_output() into udp6_usrreq.c, and remove udp6_output.c. This is more consistent with IPv4, and there is no good reason for keeping a separate file only for one function. FreeBSD did the same.
|
#
48235e82 |
| 02-Aug-2016 |
knakahara <knakahara@NetBSD.org> |
ip6flow refactor like ipflow.
- move ip6flow sysctls into ip6_flow.c like ip_flow.c:r1.64 - build ip6_flow.c only if GATEWAY kernel option is enabled
|
#
8c2654ab |
| 13-Oct-2015 |
rjs <rjs@NetBSD.org> |
Add core networking support for SCTP.
|
#
65278823 |
| 10-Feb-2015 |
rjs <rjs@NetBSD.org> |
Add DCCP protocol support from KAME.
|
#
a5009781 |
| 02-Dec-2014 |
christos <christos@NetBSD.org> |
add routines to print in6_addr and sockaddr_in6 (in6_print, sin6_print)
|
#
6e869e40 |
| 25-Jan-2008 |
joerg <joerg@NetBSD.org> |
Refactor in_cksum/in4_cksum/in6_cksum implementations: - All three functions are included in the kernel by default. They call a backend function cpu_in_cksum after possibly computing the checksum
Refactor in_cksum/in4_cksum/in6_cksum implementations: - All three functions are included in the kernel by default. They call a backend function cpu_in_cksum after possibly computing the checksum of the pseudo header. - cpu_in_cksum is the core to implement the one-complement sum. The default implementation is moderate fast on most platforms and provides a 32bit accumulator with 16bit addends for L32 platforms and a 64bit accumulator with 32bit addends for L64 platforms. It handles edge cases like very large mbuf chains (could happen with native IPv6 in the future) and provides a good base for new native implementations. - Modify i386 and amd64 assembly to use the new interface.
This disables the MD implementations on !x86 until the conversion is done. For Alpha, the portable version is faster.
show more ...
|
#
8aa640da |
| 07-Mar-2007 |
liamjfoy <liamjfoy@NetBSD.org> |
Add IPv6 Fast Forward - the IPv4 counterpart:
If ip6_forward successfully forwards a packet, a cache, in this case a ip6flow struct entry, will be created. ether_input and friends will then be able
Add IPv6 Fast Forward - the IPv4 counterpart:
If ip6_forward successfully forwards a packet, a cache, in this case a ip6flow struct entry, will be created. ether_input and friends will then be able to call ip6flow_fastforward with the packet which will then be passed to if_output (unless an issue is found - in that case the packet is passed back to ip6_input).
ok matt@ christos@ dyoung@ and joerg@
show more ...
|
#
401e606d |
| 25-Nov-2006 |
yamt <yamt@NetBSD.org> |
move tso-by-software code to their own files. no functional changes.
|
#
de8db475 |
| 05-May-2006 |
rpaulo <rpaulo@NetBSD.org> |
Add support for RFC 3542 Adv. Socket API for IPv6 (which obsoletes 2292). * RFC 3542 isn't binary compatible with RFC 2292. * RFC 2292 support is on by default but can be disabled. * update ping6, te
Add support for RFC 3542 Adv. Socket API for IPv6 (which obsoletes 2292). * RFC 3542 isn't binary compatible with RFC 2292. * RFC 2292 support is on by default but can be disabled. * update ping6, telnet and traceroute6 to the new API.
From the KAME project (www.kame.net). Reviewed by core.
show more ...
|
#
78678b13 |
| 21-Jan-2006 |
rpaulo <rpaulo@NetBSD.org> |
Better support of IPv6 scoped addresses.
- most of the kernel code will not care about the actual encoding of scope zone IDs and won't touch "s6_addr16[1]" directly. - similarly, most of the kerne
Better support of IPv6 scoped addresses.
- most of the kernel code will not care about the actual encoding of scope zone IDs and won't touch "s6_addr16[1]" directly. - similarly, most of the kernel code will not care about link-local scoped addresses as a special case. - scope boundary check will be stricter. For example, the current *BSD code allows a packet with src=::1 and dst=(some global IPv6 address) to be sent outside of the node, if the application do: s = socket(AF_INET6); bind(s, "::1"); sendto(s, some_global_IPv6_addr); This is clearly wrong, since ::1 is only meaningful within a single node, but the current implementation of the *BSD kernel cannot reject this attempt. - and, while there, don't try to remove the ff02::/32 interface route entry in in6_ifdetach() as it's already gone.
This also includes some level of support for the standard source address selection algorithm defined in RFC3484, which will be completed on in the future.
From the KAME project via JINMEI Tatuya. Approved by core@.
show more ...
|
#
95e1ffb1 |
| 11-Dec-2005 |
christos <christos@NetBSD.org> |
merge ktrace-lwp.
|
#
32e3deae |
| 06-Sep-2003 |
itojun <itojun@NetBSD.org> |
randomize IPv4/v6 fragment ID and IPv6 flowlabel. avoids predictability of these fields. ip_id.c is from openbsd. ip6_id.c is adapted by kame.
|
#
5b2b587c |
| 10-Oct-2002 |
thorpej <thorpej@NetBSD.org> |
Move netinet, netinet6, ipsec, and ipfilter config defns to netinet/files.ipfilter, etinet/files.netinet, netinet6/files.netinet6, and netinet6/files.netipsec.
XXX There are still a few stragglers i
Move netinet, netinet6, ipsec, and ipfilter config defns to netinet/files.ipfilter, etinet/files.netinet, netinet6/files.netinet6, and netinet6/files.netipsec.
XXX There are still a few stragglers in conf/files, which are entangled with other network protocols.
show more ...
|