| #
2fd9c36d |
| 28-Oct-2022 |
ozaki-r <ozaki-r@NetBSD.org> |
Remove in_pcb_hdr.h
|
| #
3761620b |
| 20-Sep-2022 |
ozaki-r <ozaki-r@NetBSD.org> |
tcp: separate syn cache stuffs into tcp_syncache.[ch] files
No functional change.
|
| #
f922b0f6 |
| 06-Sep-2018 |
maxv <maxv@NetBSD.org> |
Remove the network ATM code.
|
| #
c935a86e |
| 11-Jul-2018 |
kre <kre@NetBSD.org> |
Fix build. pf_ioctl.c needs netinet/in_offload.h (after previous change). Because this is in a module, apparently, that means that netinet_in_offload.h needs to get installed in /usr/include, so do
Fix build. pf_ioctl.c needs netinet/in_offload.h (after previous change). Because this is in a module, apparently, that means that netinet_in_offload.h needs to get installed in /usr/include, so do that as well.
Feel free to fix this in a better way...
show more ...
|
| #
939a415a |
| 16-Feb-2017 |
knakahara <knakahara@NetBSD.org> |
add l2tp(4) L2TPv3 interface.
originally implemented by IIJ SEIL team.
|
| #
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.
|
| #
69b4eb72 |
| 15-Sep-2012 |
plunky <plunky@NetBSD.org> |
install header files from IPF 5.1.2 (sys/external/bsd/ipf) instead of older IPF (sys/dist/ipf).
This adds ipf_rb.h
|
| #
84f52095 |
| 25-Jun-2012 |
christos <christos@NetBSD.org> |
rename rfc6056 -> portalgo, requested by yamt
|
| #
f8a1d797 |
| 15-Feb-2012 |
riz <riz@NetBSD.org> |
Back out the recent import of IPFilter 5.1.1 for the upcoming branch, which will now have IPFilter 4.1.34. IPFilter 5.1.1 will be restored post-branch.
ok: core, releng.
|
| #
ee0161be |
| 30-Jan-2012 |
darrenr <darrenr@NetBSD.org> |
Patch to include ipf_rb.h missed from merge.
|
| #
afa44705 |
| 24-Sep-2011 |
christos <christos@NetBSD.org> |
install the header.
|
| #
c2e43be1 |
| 03-May-2011 |
dyoung <dyoung@NetBSD.org> |
Reduces the resources demanded by TCP sessions in TIME_WAIT-state using methods called Vestigial Time-Wait (VTW) and Maximum Segment Lifetime Truncation (MSLT).
MSLT and VTW were contributed by Coyo
Reduces the resources demanded by TCP sessions in TIME_WAIT-state using methods called Vestigial Time-Wait (VTW) and Maximum Segment Lifetime Truncation (MSLT).
MSLT and VTW were contributed by Coyote Point Systems, Inc.
Even after a TCP session enters the TIME_WAIT state, its corresponding socket and protocol control blocks (PCBs) stick around until the TCP Maximum Segment Lifetime (MSL) expires. On a host whose workload necessarily creates and closes down many TCP sockets, the sockets & PCBs for TCP sessions in TIME_WAIT state amount to many megabytes of dead weight in RAM.
Maximum Segment Lifetimes Truncation (MSLT) assigns each TCP session to a class based on the nearness of the peer. Corresponding to each class is an MSL, and a session uses the MSL of its class. The classes are loopback (local host equals remote host), local (local host and remote host are on the same link/subnet), and remote (local host and remote host communicate via one or more gateways). Classes corresponding to nearer peers have lower MSLs by default: 2 seconds for loopback, 10 seconds for local, 60 seconds for remote. Loopback and local sessions expire more quickly when MSLT is used.
Vestigial Time-Wait (VTW) replaces a TIME_WAIT session's PCB/socket dead weight with a compact representation of the session, called a "vestigial PCB". VTW data structures are designed to be very fast and memory-efficient: for fast insertion and lookup of vestigial PCBs, the PCBs are stored in a hash table that is designed to minimize the number of cacheline visits per lookup/insertion. The memory both for vestigial PCBs and for elements of the PCB hashtable come from fixed-size pools, and linked data structures exploit this to conserve memory by representing references with a narrow index/offset from the start of a pool instead of a pointer. When space for new vestigial PCBs runs out, VTW makes room by discarding old vestigial PCBs, oldest first. VTW cooperates with MSLT.
It may help to think of VTW as a "FIN cache" by analogy to the SYN cache.
A 2.8-GHz Pentium 4 running a test workload that creates TIME_WAIT sessions as fast as it can is approximately 17% idle when VTW is active versus 0% idle when VTW is inactive. It has 103 megabytes more free RAM when VTW is active (approximately 64k vestigial PCBs are created) than when it is inactive.
show more ...
|
| #
60149b1c |
| 05-Oct-2007 |
dyoung <dyoung@NetBSD.org> |
Work in progress: use a raw socket for GRE in IP encapsulation instead of adding/subtracting our own IPv4 header.
There are many benefits: gre(4) needn't grok the outer encapsulation header any lon
Work in progress: use a raw socket for GRE in IP encapsulation instead of adding/subtracting our own IPv4 header.
There are many benefits: gre(4) needn't grok the outer encapsulation header any longer, so this simplifies the gre(4) code. The IP stack needn't grok GRE, so it is simplified, too. gre(4) will benefit from optimizations in the socket code. Eventually, gre(4) will gain an IPv6 encapsulation with very few new lines of code.
There is a small performance loss. A 133 MHz, 486-class AMD Elan sinks/sources a TCP stream over GRE with about 93% the throughput of the old code. TCP throughput on a 266 MHz, 586-class AMD Geode is about 96% the throughput of the old code. A 175-MHz ADM5120 (MIPS) only sinks a TCP stream over GRE at about 90% of the old code; I am still investigating that.
I produced stripped-down versions of sosend() and soreceive() for gre(4) to use. They are guaranteed not to block, so they can be called from a software interrupt and from a socket upcall, respectively.
A kernel thread is no longer necessary for socket transmit/receive, but I didn't get around to removing it, yet.
Thanks to Matt Thomas for suggesting the use of stripped-down socket code and software interrupts, and to Andrew Doran for advice and answers concerning software interrupts, threads, and performance.
show more ...
|
| #
8b646d9b |
| 02-May-2007 |
dyoung <dyoung@NetBSD.org> |
Remove obsolete files netinet/in_route.[ch].
|
| #
c308b1c6 |
| 09-Dec-2006 |
dyoung <dyoung@NetBSD.org> |
Here are various changes designed to protect against bad IPv4 routing caused by stale route caches (struct route). Route caches are sprinkled throughout PCBs, the IP fast-forwarding table, and IP tu
Here are various changes designed to protect against bad IPv4 routing caused by stale route caches (struct route). Route caches are sprinkled throughout PCBs, the IP fast-forwarding table, and IP tunnel interfaces (gre, gif, stf).
Stale IPv6 and ISO route caches will be treated by separate patches.
Thank you to Christoph Badura for suggesting the general approach to invalidating route caches that I take here.
Here are the details:
Add hooks to struct domain for tracking and for invalidating each domain's route caches: dom_rtcache, dom_rtflush, and dom_rtflushall.
Introduce helper subroutines, rtflush(ro) for invalidating a route cache, rtflushall(family) for invalidating all route caches in a routing domain, and rtcache(ro) for notifying the domain of a new cached route.
Chain together all IPv4 route caches where ro_rt != NULL. Provide in_rtcache() for adding a route to the chain. Provide in_rtflush() and in_rtflushall() for invalidating IPv4 route caches. In in_rtflush(), set ro_rt to NULL, and remove the route from the chain. In in_rtflushall(), walk the chain and remove every route cache.
In rtrequest1(), call rtflushall() to invalidate route caches when a route is added.
In gif(4), discard the workaround for stale caches that involves expiring them every so often.
Replace the pattern 'RTFREE(ro->ro_rt); ro->ro_rt = NULL;' with a call to rtflush(ro).
Update ipflow_fastforward() and all other users of route caches so that they expect a cached route, ro->ro_rt, to turn to NULL.
Take care when moving a 'struct route' to rtflush() the source and to rtcache() the destination.
In domain initializers, use .dom_xxx tags.
KNF here and there.
show more ...
|
| #
a25eaede |
| 13-Nov-2006 |
dyoung <dyoung@NetBSD.org> |
Add a source-address selection policy mechanism to the kernel.
Also, add ioctls SIOCGIFADDRPREF/SIOCSIFADDRPREF to get/set preference numbers for addresses. Make ifconfig(8) set/display preference
Add a source-address selection policy mechanism to the kernel.
Also, add ioctls SIOCGIFADDRPREF/SIOCSIFADDRPREF to get/set preference numbers for addresses. Make ifconfig(8) set/display preference numbers.
To activate source-address selection policies in your kernel, add 'options IPSELSRC' to your kernel configuration.
Miscellaneous changes in support of source-address selection:
1 Factor out some common code, producing rt_replace_ifa().
2 Abbreviate a for-loop with TAILQ_FOREACH().
3 Add the predicates on IPv4 addresses IN_LINKLOCAL() and IN_PRIVATE(), that are true for link-local unicast (169.254/16) and RFC1918 private addresses, respectively. Add the predicate IN_ANY_LOCAL() that is true for link-local unicast and multicast.
4 Add IPv4-specific interface attach/detach routines, in_domifattach and in_domifdetach, which build #ifdef IPSELSRC.
See in_getifa(9) for a more thorough description of source-address selection policy.
show more ...
|
| #
4876c304 |
| 18-May-2006 |
liamjfoy <liamjfoy@NetBSD.org> |
Integrate Common Address Redundancy Procotol (CARP) from OpenBSD
'pseudo-device carp'
Thanks to: joerg@ christos@ riz@ and others who tested Ok: core@
|
| #
95e1ffb1 |
| 11-Dec-2005 |
christos <christos@NetBSD.org> |
merge ktrace-lwp.
|
| #
997ffdba |
| 09-Jul-2005 |
xtraeme <xtraeme@NetBSD.org> |
Move ipl.h into the ipfilter block, which is the right place.
|
| #
84022805 |
| 01-May-2005 |
martti <martti@NetBSD.org> |
Install netinet/ipl.h (bin/30095)
|
| #
1c9b56c8 |
| 22-Feb-2005 |
peter <peter@NetBSD.org> |
Add MKIPFILTER; if set to no, don't build and install the ipf(4) programs, headers and LKM.
Add MKPF; if set to no, don't build and install the pf(4) programs, headers, LKM and spamd.
Both options
Add MKIPFILTER; if set to no, don't build and install the ipf(4) programs, headers and LKM.
Add MKPF; if set to no, don't build and install the pf(4) programs, headers, LKM and spamd.
Both options default to yes, so nothing changed in the default build.
Reviewed by lukem.
show more ...
|
| #
8484dd9e |
| 05-Oct-2004 |
yamt <yamt@NetBSD.org> |
move ipf headers and add a comment.
|
| #
5976437e |
| 01-Oct-2004 |
christos <christos@NetBSD.org> |
Move ipf to sys/dist/ipf; Note that I followed the pattern used for pf. I think though that the files.ipfilter and Makefile glue should go to the dist directory, not like it is done now.
|
| #
6e3c6399 |
| 04-Sep-2004 |
manu <manu@NetBSD.org> |
IPv4 PIM support, based on a submission from Pavlin Radoslavov posted on tech-net@
|