branches: 1.1.2; 1.1.4; 1.1.6; 1.1.18;
Add a very simplistic PF_INET/SOCK_DGRAM domain/proto implementation,
which delegates the work to host kernel sockets. This does not
run the entire kernel TCP/IP stack in userspace and therefore does
not require the ability to send or receive raw packets. This
implies that root priviledges are not required. As already said
above, only supports UDPv4 for now. Extending should be easy.

Rename Makefile.rump${x} to Makefile.rump${x}comp for consistency.

bluetooth stack component for rump

branches: 1.6.2; 1.6.4;
Move the net80211 support component into the proper place in "net"
and install as rumpnet_net80211.

branches: 1.5.2;
Add a virtual ethernet interface which uses shared memory as the
bus instead of relying on the host kernel's tap and bridge. This
is much lighterweight approach which does not consume non-pageable
kernel resources.

branches: 1.4.2;
Add a PF_LOCAL rump kernel component.

Add missing dollar sign ($) for $NetBSD$ tag.

branches: 1.2.2; 1.2.4; 1.2.6;
Locally descend into new directories (build does not descend here yet).

branches: 1.1.2;
Add a very simplistic PF_INET/SOCK_DGRAM domain/proto implementation,
which delegates the work to host kernel sockets. This does not
run the entire kernel TCP/IP stack in userspace and therefore does
not require the ability to send or receive raw packets. This
implies that root priviledges are not required. As already said
above, only supports UDPv4 for now. Extending should be easy.

Rump-ify ALTQ (librumpnet_altq.so)

Add a new link-aggregation pseudo interface named lagg(4)

- FreeBSD's lagg(4) based implementation
- MP-safe and MP-scalable

branches: 1.23.6; 1.23.8;
rumpify vether(4)

Clarify wg(4)'s relation to WireGuard, pending further discussion.

Still planning to replace wgconfig(8) and wg-keygen(8) by one wg(8)
tool compatible with wireguard-tools; update wg(4) for the minor
changes from the 2018-06-30 spec to the 2020-06-01 spec; &c. This just
clarifies the current state of affairs as it exists in the development
tree for now.

Mark the man page EXPERIMENTAL for extra clarity.

[ozaki-r] Changes to the kernel core for wireguard

ipsec(4) interface supports rump now.

branches: 1.19.2;
merge the bouyer-socketcan branch to HEAD.

CAN stands for Controller Area Network, a broadcast network used
in automation and automotive fields. For example, the NMEA2000 standard
developped for marine devices uses a CAN network as the link layer.

This is an implementation of the linux socketcan API:
https://www.kernel.org/doc/Documentation/networking/can.txt
you can also see can(4).

This adds a new socket family (AF_CAN) and protocol (PF_CAN),
as well as the canconfig(8) utility, used to set timing parameter of
CAN hardware. Also inclued is a driver for the CAN controller
found in the allwinner A20 SoC (I tested it with an Olimex lime2 board,
connected with PIC18-based CAN devices).

There is also the canloop(4) pseudo-device, which allows to use
the socketcan API without CAN hardware.

At this time the CANFD part of the linux socketcan API is not implemented.
Error frames are not implemented either. But I could get the cansend and
canreceive utilities from the canutils package to build and run with minimal
changes. tcpudmp(8) can also be used to record frames, which can be
decoded with etherreal.

Rumpify netipsec

Note that we should modularize netipsec and reduce reverse symbol references
(referencing symbols of netipsec from net, netinet and netinet6) though,
the task needs lots of code changes. Prior to doing so, rumpifying it and
having ATF tests should be useful.

l2tp(4) support rump.

branches: 1.16.2;
Rumpify vlan(4)

Support tun devices on rump kernels

branches: 1.14.2;
Rump-ify if_pppoe

From s-yamaguchi@IIJ

Always descend into component directories for rumpdescribe.

if_gif supports rump now.

Add a rump kernel component for the tap device.

from Wei Liu <wei.liu2@citrix.com> via private email

branches: 1.10.6;
Move rumpnet_bpfjit under MKSLJIT as well.

Build rumpkern_sljit and rumpnet_bpfjit; include them into the sets.

Separate inet and inet6, allows inet6-only rump kernels.

Make it possible to not build virtif since it's not supported
on all hosts.

(no change to NetBSD)

Add librumpnet_netmpls that provides MPLS features into rump kernels
ok'ed pooka@

branches: 1.5.2; 1.5.4; 1.5.10;
Enable the build of librumpnet_npf.

branches: 1.4.6; 1.4.10; 1.4.16;
agr(4) support

Actually, unlike e.g. carp, bridge can be its own component since
it doesn't want to join the protosw party. We can deal with other
linkhappy stuff with weak symbols.

(where is our modular networking stack?)

sockin cannot be loaded the same time as rumpnet_inet because both
provide a PF_INET domain. Guess that real inet is more useful and
don't put sockin on the "all components" list.

Rename Makefile.rump${x} to Makefile.rump${x}comp for consistency.

Rename Makefile.rump${x} to Makefile.rump${x}comp for consistency.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.18; 1.1.24;
Add a very simplistic PF_INET/SOCK_DGRAM domain/proto implementation,
which delegates the work to host kernel sockets. This does not
run the entire kernel TCP/IP stack in userspace and therefore does
not require the ability to send or receive raw packets. This
implies that root priviledges are not required. As already said
above, only supports UDPv4 for now. Extending should be easy.

adapt to ${CC_WNO_ADDRESS_OF_PACKED_MEMBER}

Simplify CWARNFLAGS to use ${CC_WNO_ADDRESS_OF_PACKED_MEMBER}
which works for both clang and gcc, and remove compiler-specific
equivalents.

bsd.own.mk: rename to CC_WNO_ADDRESS_OF_PACKED_MEMBER

Provide a single variable
CC_WNO_ADDRESS_OF_PACKED_MEMBER
with options for both clang and gcc, to replace
CLANG_NO_ADDR_OF_PACKED_MEMBER
CC_NO_ADDR_OF_PACKED_MEMBER
GCC_NO_ADDR_OF_PACKED_MEMBER

Using the convention CC_compilerflag, where compilerflag
is based on the full compiler flag name.

add support for new GCC 9 warnings that may be too much to fix
right now. new address-of-packed-member and format-overflow
warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd
GCC_NO_FORMAT_OVERFLOW variables to remove these warnings.

apply to a bunch of the tree. mostly, these are real bugs that
should be fixed, but in many cases, only by removing the 'packed'
attribute from some structure that doesn't really need it. (i
looked at many different ones, and while perhaps 60-80% were
already properly aligned, it wasn't clear to me that the uses
were always coming from sane data vs network alignment, so it
doesn't seem safe to remove packed without careful research for
each affect struct.) clang already warned (and was not erroring)
for many of these cases, but gcc picked up dozens more.

Disable a couple of warnings until further investigation.

branches: 1.6.2;
Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

remove librump/rumpnet/opt, consolidate in rump/include/opt

branches: 1.4.20; 1.4.38;
Introduce RUMP_COMPONENT. It behaves mostly like a simplified
module which is linked into the kernel and cannot be unloaded.
The main purpose is to get the proper constructors run and create
any /dev nodes necessary for said component. Once more of the
kernel (e.g. networking stack and device drivers) are converted to
MODULE and devfs pops up from somewhere, rump components can be
retired.

branches: 1.3.2;
Add a dummyif, which doesn't actually traffic any cargo, but since
it has no backend it can always be attached and is therefore
convenient for testing ifconfig.

branches: 1.2.2; 1.2.4;
Purge multiple kernel opt files.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8;
Add a very simplistic PF_INET/SOCK_DGRAM domain/proto implementation,
which delegates the work to host kernel sockets. This does not
run the entire kernel TCP/IP stack in userspace and therefore does
not require the ability to send or receive raw packets. This
implies that root priviledges are not required. As already said
above, only supports UDPv4 for now. Extending should be easy.

branches: 1.1.2; 1.1.18;
add ioconf files for pseudo device attach prototypes

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

add ioconf files for pseudo device attach prototypes

branches: 1.2.6;
rename component.c -> agr_component.c

branches: 1.1.6; 1.1.10; 1.1.20; 1.1.24;
agr(4) support

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.12;
rename component.c -> agr_component.c

rename component.c -> agr_component.c

branches: 1.1.6; 1.1.10; 1.1.20; 1.1.24;
agr(4) support

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.6; 1.1.20; 1.1.38;
agr(4) support

branches: 1.1.4;
Rump-ify ALTQ (librumpnet_altq.so)

branches: 1.1.4;
Rump-ify ALTQ (librumpnet_altq.so)

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.12;
Add rumpkern_sljit and rumpnet_bpfjit modules.

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.12;
Add rumpkern_sljit and rumpnet_bpfjit modules.

branches: 1.1.2; 1.1.18;
add ioconf files for pseudo device attach prototypes

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

purge rump/net of component-specific opt directories

add ioconf files for pseudo device attach prototypes

branches: 1.2.6;
rename component.c -> bridge_component.c

branches: 1.1.6; 1.1.10; 1.1.20; 1.1.24;
Actually, unlike e.g. carp, bridge can be its own component since
it doesn't want to join the protosw party. We can deal with other
linkhappy stuff with weak symbols.

(where is our modular networking stack?)

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.12;
rename component.c -> bridge_component.c

rename component.c -> bridge_component.c

branches: 1.1.6; 1.1.10; 1.1.20; 1.1.24;
Actually, unlike e.g. carp, bridge can be its own component since
it doesn't want to join the protosw party. We can deal with other
linkhappy stuff with weak symbols.

(where is our modular networking stack?)

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.6; 1.1.20; 1.1.38;
Actually, unlike e.g. carp, bridge can be its own component since
it doesn't want to join the protosw party. We can deal with other
linkhappy stuff with weak symbols.

(where is our modular networking stack?)

branches: 1.1.2; 1.1.18;
if_gif supports rump now.

branches: 1.1.2; 1.1.18;
if_gif supports rump now.

branches: 1.2.16;
Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.1.2;
if_gif supports rump now.

branches: 1.1.2;
ipsec(4) interface supports rump now.

branches: 1.1.2;
ipsec(4) interface supports rump now.

branches: 1.1.2;
ipsec(4) interface supports rump now.

branches: 1.1.2; 1.1.6; 1.1.14; 1.1.18;
l2tp(4) support rump.

branches: 1.1.2; 1.1.6; 1.1.14; 1.1.18;
l2tp(4) support rump.

branches: 1.1.2; 1.1.6; 1.1.14; 1.1.18;
l2tp(4) support rump.

branches: 1.1.2; 1.1.6;
Add a new link-aggregation pseudo interface named lagg(4)

- FreeBSD's lagg(4) based implementation
- MP-safe and MP-scalable

branches: 1.1.2; 1.1.6;
Add a new link-aggregation pseudo interface named lagg(4)

- FreeBSD's lagg(4) based implementation
- MP-safe and MP-scalable

branches: 1.1.2; 1.1.6;
Add a new link-aggregation pseudo interface named lagg(4)

- FreeBSD's lagg(4) based implementation
- MP-safe and MP-scalable

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

branches: 1.6.6;
rename component.c -> local_component.c

branches: 1.5.10; 1.5.20; 1.5.24;
Globally define -Wno-pointer-sign, as it has become a pointless
exercise of "add it to every Makefile individually".

XXX: should autosynchronize with the rest of the kernel buildflags
in sys/conf/Makefile.kern.inc.

branches: 1.4.2;
Use linker script to make __start/stop_link_set_modules be present
in libs built with binutils >=2.19. This is a less error-prone
method than the previous where components had to be tagged in the
Makefile as modules (and if they weren't, things broke. and vice
versa).

binutils 2.19 has changed the old behaviour of defining __start_SECTNAME
for orphaned sections to using PROVIDE. What this means is that
unless a rump component internally references that symbol, it will
not be included in the component shared library, and hence cannot
be referenced when the component is loaded. Add a workaround which
works both with 2.16 and 2.19: force a reference to the __start
symbol internally and hence retain it in the resulting library.

Use a bunch of weak symbols to determine which network components
are present. This works in userspace as opposed relying in link
sets, which fail miserably. Later, when the networking stack
becomes modularized, we can move to a dynamic scheme like with file
systems.

Also, this change allows us to do proper autoconfig, namely attach
the loopback interface iff it is present.

branches: 1.1.2; 1.1.4; 1.1.6;
Add a PF_LOCAL rump kernel component.

rename component.c -> local_component.c

branches: 1.2.10; 1.2.20; 1.2.24;
Introduce RUMP_COMPONENT. It behaves mostly like a simplified
module which is linked into the kernel and cannot be unloaded.
The main purpose is to get the proper constructors run and create
any /dev nodes necessary for said component. Once more of the
kernel (e.g. networking stack and device drivers) are converted to
MODULE and devfs pops up from somewhere, rump components can be
retired.

branches: 1.1.2; 1.1.4;
Use a bunch of weak symbols to determine which network components
are present. This works in userspace as opposed relying in link
sets, which fail miserably. Later, when the networking stack
becomes modularized, we can move to a dynamic scheme like with file
systems.

Also, this change allows us to do proper autoconfig, namely attach
the loopback interface iff it is present.

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.2.2;
Nuke the DOMAINADD() macro and just call domain_attach(), now that things
work correctly that way.

branches: 1.1.4; 1.1.6; 1.1.10;
rename component.c -> local_component.c

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.4; 1.1.6; 1.1.28; 1.1.46;
Add a PF_LOCAL rump kernel component.

bsd.own.mk: rename GCC_NO_* to CC_WNO_*

Rename compiler-warning-disable variables from
GCC_NO_warning
to
CC_WNO_warning
where warning is the full warning name as used by the compiler.

GCC_NO_IMPLICIT_FALLTHRU is CC_WNO_IMPLICIT_FALLTHROUGH

Using the convention CC_compilerflag, where compilerflag
is based on the full compiler flag name.

new GCC_NO_* uses for warning issues. most of the users of the new
GCC_NO_RETURN_LOCAL_ADDR are bugs in GCC itself, not the code.

branches: 1.34.4;
rump: Add nd.c to libnet

Add if_stats.c to rumpnet.

branches: 1.32.2;
introduce some common variables for use in GCC warning disables:

GCC_NO_FORMAT_TRUNCATION -Wno-format-truncation (GCC 7/8)
GCC_NO_STRINGOP_TRUNCATION -Wno-stringop-truncation (GCC 8)
GCC_NO_STRINGOP_OVERFLOW -Wno-stringop-overflow (GCC 8)
GCC_NO_CAST_FUNCTION_TYPE -Wno-cast-function-type (GCC 8)

use these to turn off warnings for most GCC-8 complaints. many
of these are false positives, most of the real bugs are already
commited, or are yet to come.


we plan to introduce versions of (some?) of these that use the
"-Wno-error=" form, which still displays the warnings but does
not make it an error, and all of the above will be re-considered
as either being "fix me" (warning still displayed) or "warning
is wrong."

PR kern/53562

Add ether_sw_offload_[tr]x: handle TX/RX offload options in software.
Since this violates separation b/w L2 and L3/L4, new files are added
rather than having the routines in sys/net/if_ethersubr.c.

OK msaitoh thorpej

branches: 1.30.12; 1.30.14;
Fix build (undefined reference to `rumpns_pfil_init' on usr.sbin/puffs/rump_nfs)

branches: 1.29.2;
Add ifam_pid and ifam_addrflags to ifa_msghdr.
Re-version RTM_NEWADDR, RTM_DELADDR, RTM_CHGADDR and NET_RT_IFLIST.
Add compat code for old version.

branches: 1.28.2;
Rump-ify if_pppoe

From s-yamaguchi@IIJ

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

Hook up lltable/llentry with the kernel (and rumpkernel)

It is built and initialized on bootup, but there is no user for now.

Most codes in in.c are imported from FreeBSD as well as lltable/llentry.

purge rump/net of component-specific opt directories

add ioconf files for pseudo device attach prototypes

Rename RUMP_COMPAT to RUMP_NBCOMBAT to better signify what the
variable does.

COMPAT_OIF{DATA,REQ} are defined by compat/sys/sockio.h if need be,
don't define them here unconditionally.

Build compat code only when specified by RUMP_COMPAT

branches: 1.20.6;
rename component.c -> net_component.c

Separate inet and inet6, allows inet6-only rump kernels.

Add librumpnet_netmpls that provides MPLS features into rump kernels
ok'ed pooka@

branches: 1.17.2; 1.17.4;
cosmetic: put portalgo.c in the conceptually right place

branches: 1.16.2;
no need to include code which is already provided by the faction base

Adjust to rfc6056 rename to portalgo

rumpnet_net: add pfil.c

branches: 1.13.2; 1.13.6; 1.13.8;
add rfc6056.c

Hide the radix-trie implementation of the forwarding table so that we
will have an easier time replacing it with something different, even if
it is a second radix-trie implementation.

sys/net/route.c and sys/net/rtsock.c no longer operate directly on
radix_nodes or radix_node_heads.

Hopefully this will reduce the temptation to implement multipath or
source-based routing using grotty hacks to the grotty old radix-trie
code, too. :-)

Add a new AF/PF_ROUTE which is 64-bit clean which makes the routing socket
interface (and its associated sysctls) act identically for both 32 and 64 bit
programs. The old unclean one remains for backward compatibility.

branches: 1.10.2; 1.10.4;
Actually, unlike e.g. carp, bridge can be its own component since
it doesn't want to join the protosw party. We can deal with other
linkhappy stuff with weak symbols.

(where is our modular networking stack?)

Support bridging. As usual, it would be nice if this could be a
separate component, but King Ifdef doesn't let us.

support compat ioctl's (OOOOOlalaSIOC stuff)

branches: 1.7.4;
Use linker script to make __start/stop_link_set_modules be present
in libs built with binutils >=2.19. This is a less error-prone
method than the previous where components had to be tagged in the
Makefile as modules (and if they weren't, things broke. and vice
versa).

binutils 2.19 has changed the old behaviour of defining __start_SECTNAME
for orphaned sections to using PROVIDE. What this means is that
unless a rump component internally references that symbol, it will
not be included in the component shared library, and hence cannot
be referenced when the component is loaded. Add a workaround which
works both with 2.16 and 2.19: force a reference to the __start
symbol internally and hence retain it in the resulting library.

Use a bunch of weak symbols to determine which network components
are present. This works in userspace as opposed relying in link
sets, which fail miserably. Later, when the networking stack
becomes modularized, we can move to a dynamic scheme like with file
systems.

Also, this change allows us to do proper autoconfig, namely attach
the loopback interface iff it is present.

branches: 1.4.2; 1.4.4;
-fno-strict-aliasing is now set globally for rump

branches: 1.3.4;
Heave-ho radix.c from librumpnet_net to librumpnet.

branches: 1.2.2; 1.2.4;
Deal with the ld.so/linkset brokenness and compile all of libnet
and libnetinet into a big bunch for now. If they were separate
libraries, the DOMAIN_DEFINE() in the latter on the linkline would
not get noticed at "boot" time because of the abovementioned
brokenness. One of these days I'll add code to dlopen() the
libraries and resplit them, but this will allow things to work
until then.

branches: 1.1.2;
Provide essentially sys/net as a rump library.

branches: 1.1.2; 1.1.18;
add ioconf files for pseudo device attach prototypes

rename component.c -> net_component.c

branches: 1.10.4; 1.10.14; 1.10.18;
attach the compat_50_routedomain to make it actually work

branches: 1.9.2; 1.9.4;
Ensure that a) loopback attaches after all the domains have attached
b) loopback is configured only after it has attached.

makes tests/net/if_loop work again

Separate interface init and domain adding.

Actually, unlike e.g. carp, bridge can be its own component since
it doesn't want to join the protosw party. We can deal with other
linkhappy stuff with weak symbols.

(where is our modular networking stack?)

Support bridging. As usual, it would be nice if this could be a
separate component, but King Ifdef doesn't let us.

Attach PF_LINK domain. ifconfig wants to play with it, plus there's
no reason not to anyway.

Attach 1 loop instead of 0.

not tested on animals

branches: 1.3.2;
Introduce RUMP_COMPONENT. It behaves mostly like a simplified
module which is linked into the kernel and cannot be unloaded.
The main purpose is to get the proper constructors run and create
any /dev nodes necessary for said component. Once more of the
kernel (e.g. networking stack and device drivers) are converted to
MODULE and devfs pops up from somewhere, rump components can be
retired.

branches: 1.2.2;
call ifinit{,1}()

branches: 1.1.2;
Use a bunch of weak symbols to determine which network components
are present. This works in userspace as opposed relying in link
sets, which fail miserably. Later, when the networking stack
becomes modularized, we can move to a dynamic scheme like with file
systems.

Also, this change allows us to do proper autoconfig, namely attach
the loopback interface iff it is present.

Fix net.inet6.ip6.ifq node doesn't exist

The node (and child nodes) is initialized in sysctl_net_pktq_setup, but the call
of sysctl_net_pktq_setup is skipped unexpectedly.

sysctl_net_pktq_setup is skipped if in6_present is false that indicates the
netinet6 component isn't loaded on rump kernels. However the flag is
accidentally always false because the flag is turned on in in6_dom_init that is
called after if_sysctl_setup on both normal and rump kernels.

Fix the issue by moving if_sysctl_setup after in6_dom_init (domaininit on normal
kernels). This fix is ad-hoc but good enough for netbsd-8. We should refine
the initialization order of network components in the future.

Pointed out by hikaru@

branches: 1.9.6; 1.9.12; 1.9.14;
l2tp(4) support rump.

pfile_init earlier (not here)

Make pfil(9) MP-safe (applying psref(9))

branches: 1.6.2;

On the first day (that being the eighth day of the eighth month,) the
building was completed only to discover that within there lay havoc.

On the second day all just groaned and moaned, and it must be someone
else's problen.

On the third day, St. Martin stepped in and traced the culprit, which
provided inspiration, and a correction was made.

Forevermore all were agog at just how such a trivial thing could do
so much damage...


OK... to be a little less vague. The loopback interface is a truly
"special" thing, and rump knew that - and treated it very specially.
Unfortunately, when the loopback interface is changed, and rump does
not keep up, bad things happen.

This (overall) might, or might not, be the correct fix - but for now
it appears to work. If someone, sometime, finds a better way to
deal with the issues of the loopback interfaces true majesty, feel
free to revert this and do it another way.

branches: 1.5.2;
Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

Hook up lltable/llentry with the kernel (and rumpkernel)

It is built and initialized on bootup, but there is no user for now.

Most codes in in.c are imported from FreeBSD as well as lltable/llentry.

sprinkle COMPAT_50

branches: 1.2.2;
Nuke the DOMAINADD() macro and just call domain_attach(), now that things
work correctly that way.

branches: 1.1.4; 1.1.6; 1.1.10;
rename component.c -> net_component.c

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.2; 1.1.4; 1.1.12; 1.1.18; 1.1.46; 1.1.66;
Provide essentially sys/net as a rump library.

branches: 1.4.18;
Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

branches: 1.3.6;
GC unused functions. Don't bother building ieee80211_acl.c, nothing in
it is non-static.

branches: 1.2.2; 1.2.12; 1.2.22; 1.2.26;
Globally define -Wno-pointer-sign, as it has become a pointless
exercise of "add it to every Makefile individually".

XXX: should autosynchronize with the rest of the kernel buildflags
in sys/conf/Makefile.kern.inc.

branches: 1.1.2;
Move the net80211 support component into the proper place in "net"
and install as rumpnet_net80211.

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.4; 1.1.24; 1.1.42;
Move the net80211 support component into the proper place in "net"
and install as rumpnet_net80211.

GC some GCC 4.8 specific sh3 HACKS entries.

These existed to avoid compile errors, and haven't been effect
since gcc.old was removed.

branches: 1.6.2; 1.6.4;
Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

Add NOLINT

branches: 1.4.6;
rename component.c -> netbt_component.c

Fix syntax for undefined HAVE_GCC.

avoid gcc bug on sh3

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.14; 1.1.24; 1.1.28;
bluetooth stack component for rump

rename component.c -> netbt_component.c

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.14; 1.1.24; 1.1.28;
bluetooth stack component for rump

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.2.2;
Nuke the DOMAINADD() macro and just call domain_attach(), now that things
work correctly that way.

branches: 1.1.4; 1.1.6; 1.1.10;
rename component.c -> netbt_component.c

Remove unused opt_bluetooth.h

plunky: "feel free"

bluetooth stack component for rump

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.24; 1.1.42;
bluetooth stack component for rump

branches: 1.2.6; 1.2.10;
merge the bouyer-socketcan branch to HEAD.

CAN stands for Controller Area Network, a broadcast network used
in automation and automotive fields. For example, the NMEA2000 standard
developped for marine devices uses a CAN network as the link layer.

This is an implementation of the linux socketcan API:
https://www.kernel.org/doc/Documentation/networking/can.txt
you can also see can(4).

This adds a new socket family (AF_CAN) and protocol (PF_CAN),
as well as the canconfig(8) utility, used to set timing parameter of
CAN hardware. Also inclued is a driver for the CAN controller
found in the allwinner A20 SoC (I tested it with an Olimex lime2 board,
connected with PIC18-based CAN devices).

There is also the canloop(4) pseudo-device, which allows to use
the socketcan API without CAN hardware.

At this time the CANFD part of the linux socketcan API is not implemented.
Error frames are not implemented either. But I could get the cansend and
canreceive utilities from the canutils package to build and run with minimal
changes. tcpudmp(8) can also be used to record frames, which can be
decoded with etherreal.

branches: 1.1.2;
file Makefile was initially added on branch bouyer-socketcan.

branches: 1.2.6; 1.2.10;
merge the bouyer-socketcan branch to HEAD.

CAN stands for Controller Area Network, a broadcast network used
in automation and automotive fields. For example, the NMEA2000 standard
developped for marine devices uses a CAN network as the link layer.

This is an implementation of the linux socketcan API:
https://www.kernel.org/doc/Documentation/networking/can.txt
you can also see can(4).

This adds a new socket family (AF_CAN) and protocol (PF_CAN),
as well as the canconfig(8) utility, used to set timing parameter of
CAN hardware. Also inclued is a driver for the CAN controller
found in the allwinner A20 SoC (I tested it with an Olimex lime2 board,
connected with PIC18-based CAN devices).

There is also the canloop(4) pseudo-device, which allows to use
the socketcan API without CAN hardware.

At this time the CANFD part of the linux socketcan API is not implemented.
Error frames are not implemented either. But I could get the cansend and
canreceive utilities from the canutils package to build and run with minimal
changes. tcpudmp(8) can also be used to record frames, which can be
decoded with etherreal.

branches: 1.1.2;
file NETCAN.ioconf was initially added on branch bouyer-socketcan.

Garbage-collect the remaining vestiges of netisr.

Convert CAN from a legacy netisr to pktqueue.

Remove spurious call to canloopinit() in an attempt to fix kern/55489

This attempt at fixing is a result of IRC discussions with martin@ and
riastradh@

branches: 1.2.6; 1.2.10;
merge the bouyer-socketcan branch to HEAD.

CAN stands for Controller Area Network, a broadcast network used
in automation and automotive fields. For example, the NMEA2000 standard
developped for marine devices uses a CAN network as the link layer.

This is an implementation of the linux socketcan API:
https://www.kernel.org/doc/Documentation/networking/can.txt
you can also see can(4).

This adds a new socket family (AF_CAN) and protocol (PF_CAN),
as well as the canconfig(8) utility, used to set timing parameter of
CAN hardware. Also inclued is a driver for the CAN controller
found in the allwinner A20 SoC (I tested it with an Olimex lime2 board,
connected with PIC18-based CAN devices).

There is also the canloop(4) pseudo-device, which allows to use
the socketcan API without CAN hardware.

At this time the CANFD part of the linux socketcan API is not implemented.
Error frames are not implemented either. But I could get the cansend and
canreceive utilities from the canutils package to build and run with minimal
changes. tcpudmp(8) can also be used to record frames, which can be
decoded with etherreal.

branches: 1.1.2;
file netcan_component.c was initially added on branch bouyer-socketcan.

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

branches: 1.5.6;
rename component.c -> netinet_component.c

branches: 1.4.12; 1.4.22; 1.4.26;
Include component.c instead of dummy.c so that domain constructors
get properly called.

branches: 1.3.2; 1.3.10; 1.3.16;
Deal with the ld.so/linkset brokenness and compile all of libnet
and libnetinet into a big bunch for now. If they were separate
libraries, the DOMAIN_DEFINE() in the latter on the linkline would
not get noticed at "boot" time because of the abovementioned
brokenness. One of these days I'll add code to dlopen() the
libraries and resplit them, but this will allow things to work
until then.

Add tcp debugging as a build option.

branches: 1.1.2;
Provide the TCP/IP as a rump library.

tcp: separate syn cache stuffs into tcp_syncache.[ch] files

No functional change.

remove ip{,6}_id.c

branches: 1.14.24;
Rumpify netipsec

Note that we should modularize netipsec and reduce reverse symbol references
(referencing symbols of netipsec from net, netinet and netinet6) though,
the task needs lots of code changes. Prior to doing so, rumpifying it and
having ATF tests should be useful.

branches: 1.13.2; 1.13.4;
purge rump/net of component-specific opt directories

Move defines of INET and INET6 from opt_inet.h to Makefile.inc

As discussed with pooka@
fixes current issues with ipv6 on rump being broken

branches: 1.11.6;
Separate inet and inet6, allows inet6-only rump kernels.

branches: 1.10.2;
default portalgo to random_start, for less connections from port 65535

cosmetic: put portalgo.c in the conceptually right place

branches: 1.8.4; 1.8.14;
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.

branches: 1.7.2;
Support carp. It would be nice to support this as its own component,
but there's about 1000 lines of #ifdef which disagree with my wish.

Split-off IPv4 re-assembly mechanism into a separate module. Abstract
into ip_reass_init(), ip_reass_lookup(), etc (note: abstraction is not
yet complete). No functional changes to the actual mechanism.

OK matt@

branches: 1.5.2;
Globally define -Wno-pointer-sign, as it has become a pointless
exercise of "add it to every Makefile individually".

XXX: should autosynchronize with the rest of the kernel buildflags
in sys/conf/Makefile.kern.inc.

branches: 1.4.2;
Support IPv6 in rump. I'd have liked to introduce a netinet6
component, but due to ifdef happiness permeating the sources, it's
a compile decision for now, so netinet pulls in both inet and inet6.

One issue, one single issue: the loopback interface still needs to
be created for IPv6 to work. I have patches to take care of it
automatically if the appropriate component (net) is present, but
they require a bit more testing before commit.

branches: 1.3.2; 1.3.4;
Better define GATEWAY in opt_gateway.h instead of the Makefile so
UPDATE builds don't go all coocoo.

enable GATEWAY

branches: 1.1.2; 1.1.4; 1.1.10;
Deal with the ld.so/linkset brokenness and compile all of libnet
and libnetinet into a big bunch for now. If they were separate
libraries, the DOMAIN_DEFINE() in the latter on the linkline would
not get noticed at "boot" time because of the abovementioned
brokenness. One of these days I'll add code to dlopen() the
libraries and resplit them, but this will allow things to work
until then.

rename component.c -> netinet_component.c

Register netisr's from component constructors instead of via a hardcoded
global list.

Allow kernels compiled with INET+INET6 to be booted as IPv4-only or IPv6-only.

Partially revert previous, there are still a few gotchas in
running ipv4/ipv6-only (too many dependencies on ifdefs).

Separate inet and inet6, allows inet6-only rump kernels.

Raise lo0 so that ipv6 config gets done for it.

Requested and tested by Justin Cormack.

branches: 1.5.8; 1.5.18; 1.5.22;
Ensure that a) loopback attaches after all the domains have attached
b) loopback is configured only after it has attached.

makes tests/net/if_loop work again

Autoconfigure 127.0.0.1 for lo0.
(testing bind/connect/etc. is now possible on a virgin rump kernel
without the need to ifconfig anything)

Support carp. It would be nice to support this as its own component,
but there's about 1000 lines of #ifdef which disagree with my wish.

branches: 1.2.2;
Introduce RUMP_COMPONENT. It behaves mostly like a simplified
module which is linked into the kernel and cannot be unloaded.
The main purpose is to get the proper constructors run and create
any /dev nodes necessary for said component. Once more of the
kernel (e.g. networking stack and device drivers) are converted to
MODULE and devfs pops up from somewhere, rump components can be
retired.

branches: 1.1.2; 1.1.4;
Use a bunch of weak symbols to determine which network components
are present. This works in userspace as opposed relying in link
sets, which fail miserably. Later, when the networking stack
becomes modularized, we can move to a dynamic scheme like with file
systems.

Also, this change allows us to do proper autoconfig, namely attach
the loopback interface iff it is present.

Include component.c instead of dummy.c so that domain constructors
get properly called.

branches: 1.1.2; 1.1.10; 1.1.16;
Deal with the ld.so/linkset brokenness and compile all of libnet
and libnetinet into a big bunch for now. If they were separate
libraries, the DOMAIN_DEFINE() in the latter on the linkline would
not get noticed at "boot" time because of the abovementioned
brokenness. One of these days I'll add code to dlopen() the
libraries and resplit them, but this will allow things to work
until then.

Garbage-collect the remaining vestiges of netisr.

Convert ARP from a legacy netisr to pktqueue.

Avoid a deadlock between softnet_lock and IFNET_LOCK

A deadlock occurs because there is a violation of the rule of lock ordering;
softnet_lock is held with hodling IFNET_LOCK, which violates the rule.
To avoid the deadlock, replace softnet_lock in in_control and in6_control
with KERNEL_LOCK.

We also need to add some KERNEL_LOCKs to protect the network stack surely.
This is required, for example, for PR kern/51356.

Fix PR kern/53043

Wrap if_ioctl_lock with IFNET_* macros (NFC)

Also if_ioctl_lock perhaps needs to be renamed to something because it's now
not just for ioctl...

Ensure to call if_addr_init with holding if_ioctl_lock

branches: 1.8.6;
Protect if_clone data with if_clone_mtx

To this end, carpattach needs to be delayed from RUMP_COMPONENT_NET to
RUMP_COMPONENT_NET_IF on rump_server. Otherwise mutex_enter via carpattach
for if_clone_mtx is called before mutex_init for it in ifinit1.

branches: 1.7.2;
Don't call loopinit() here. Instead panic if -lrumpnet_net has not been
called to initialize lo0ifp.

more loopinit();

branches: 1.5.2;
Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.4.2;
Nuke the DOMAINADD() macro and just call domain_attach(), now that things
work correctly that way.

branches: 1.3.4;
fix parameter types in pr_ioctl, called xx_control() functions and remove
abuse of pointer to struct mbuf type.

param2 changed to u_long type and uses parameter name 'cmd' (ioctl command)
param3 changed to void * type and uses parameter name 'data'
param4 changed to struct ifnet * and uses parameter name 'ifp'
param5 has been removed (formerly struct lwp *) and uses of 'l' have been
replaced with curlwp from curproc(9).

callers have had (now unnecessary) casts to struct mbuf * removed, called
code has had (now unnecessary) casts to u_long, void * and struct ifnet *
respectively removed.

reviewed by rmind@

- Implement pktqueue interface for lockless IP input queue.
- Replace ipintrq and ip6intrq with the pktqueue mechanism.
- Eliminate kernel-lock from ipintr() and ip6intr().
- Some preparation work to push softnet_lock out of ipintr().

Discussed on tech-net.

branches: 1.1.2; 1.1.4; 1.1.6;
rename component.c -> netinet_component.c

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.2; 1.1.4; 1.1.12; 1.1.18; 1.1.46; 1.1.66;
Provide the TCP/IP as a rump library.

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

branches: 1.2.4; 1.2.8; 1.2.10;
rename component.c -> netinet6_component.c

branches: 1.1.2;
Separate inet and inet6, allows inet6-only rump kernels.

remove ip{,6}_id.c

branches: 1.5.16;
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.

Rumpify netipsec

Note that we should modularize netipsec and reduce reverse symbol references
(referencing symbols of netipsec from net, netinet and netinet6) though,
the task needs lots of code changes. Prior to doing so, rumpifying it and
having ATF tests should be useful.

branches: 1.3.2; 1.3.4;
some final -Ifoo/opt removal

Move defines of INET and INET6 from opt_inet.h to Makefile.inc

As discussed with pooka@
fixes current issues with ipv6 on rump being broken

branches: 1.1.2; 1.1.6; 1.1.10; 1.1.12;
Separate inet and inet6, allows inet6-only rump kernels.

rename component.c -> netinet6_component.c

Register netisr's from component constructors instead of via a hardcoded
global list.

Allow kernels compiled with INET+INET6 to be booted as IPv4-only or IPv6-only.

branches: 1.2.2;
Partially revert previous, there are still a few gotchas in
running ipv4/ipv6-only (too many dependencies on ifdefs).

Separate inet and inet6, allows inet6-only rump kernels.

Garbage-collect the remaining vestiges of netisr.

Don't call loopinit() here. Instead panic if -lrumpnet_net has not been
called to initialize lo0ifp.

more loopinit();

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.3.2;
Nuke the DOMAINADD() macro and just call domain_attach(), now that things
work correctly that way.

branches: 1.2.4;
- Implement pktqueue interface for lockless IP input queue.
- Replace ipintrq and ip6intrq with the pktqueue mechanism.
- Eliminate kernel-lock from ipintr() and ip6intr().
- Some preparation work to push softnet_lock out of ipintr().

Discussed on tech-net.

branches: 1.1.2; 1.1.4; 1.1.6;
rename component.c -> netinet6_component.c

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.2; 1.1.6; 1.1.10; 1.1.12;
Separate inet and inet6, allows inet6-only rump kernels.

branches: 1.1.2; 1.1.4; 1.1.12; 1.1.16;
Rumpify netipsec

Note that we should modularize netipsec and reduce reverse symbol references
(referencing symbols of netipsec from net, netinet and netinet6) though,
the task needs lots of code changes. Prior to doing so, rumpifying it and
having ATF tests should be useful.

branches: 1.1.2; 1.1.4; 1.1.12; 1.1.16;
Rumpify netipsec

Note that we should modularize netipsec and reduce reverse symbol references
(referencing symbols of netipsec from net, netinet and netinet6) though,
the task needs lots of code changes. Prior to doing so, rumpifying it and
having ATF tests should be useful.

branches: 1.1.2; 1.1.4; 1.1.12; 1.1.16;
Rumpify netipsec

Note that we should modularize netipsec and reduce reverse symbol references
(referencing symbols of netipsec from net, netinet and netinet6) though,
the task needs lots of code changes. Prior to doing so, rumpifying it and
having ATF tests should be useful.

Machete-waving to fix mpls rump build after pktqueue changes.

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

purge rump/net of component-specific opt directories

add ioconf files for pseudo device attach prototypes

branches: 1.2.4; 1.2.8; 1.2.10;
rename component.c -> netmpls_component.c

branches: 1.1.2; 1.1.4;
Add librumpnet_netmpls that provides MPLS features into rump kernels
ok'ed pooka@

Machete-waving to fix mpls rump build after pktqueue changes.

branches: 1.2.4; 1.2.8;
Merge riastradh-drm2 to HEAD.

branches: 1.1.2; 1.1.4;
Add librumpnet_netmpls that provides MPLS features into rump kernels
ok'ed pooka@

branches: 1.2.14;
finish ifmpls->mpls renaming.

branches: 1.1.2;
add ioconf files for pseudo device attach prototypes

rename component.c -> netmpls_component.c

Register netisr's from component constructors instead of via a hardcoded
global list.

branches: 1.1.2; 1.1.4;
Add librumpnet_netmpls that provides MPLS features into rump kernels
ok'ed pooka@

Garbage-collect the remaining vestiges of netisr.

Convert MPLS from a legacy netisr to pktqueue.

finish ifmpls->mpls renaming.

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

add ioconf files for pseudo device attach prototypes

branches: 1.2.2;
Nuke the DOMAINADD() macro and just call domain_attach(), now that things
work correctly that way.

branches: 1.1.4; 1.1.6; 1.1.10;
rename component.c -> netmpls_component.c

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.2.4; 1.2.8; 1.2.10;
Merge riastradh-drm2 to HEAD.

branches: 1.1.2; 1.1.4;
Add librumpnet_netmpls that provides MPLS features into rump kernels
ok'ed pooka@

kernel: extract rules, lookup socket, process filtering, reviews by christos@

branches: 1.27.34;
NPF improvements:
- Add support for dynamic NETMAP algorithm (stateful net-to-net).
- Add most of the support for the dynamic NAT rules; a little bit more
userland work is needed to finish this up and enable.
- Replace 'stateful-ends' with more permissive 'stateful-all'.
- Add various tunable parameters and document them, see npf-params(7).
- Reduce the memory usage of the connection state table (conndb).
- Portmap rewrite: use memory more efficiently, handle addresses dynamically.
- Bug fix: add splsoftnet()/splx() around the thmap writers and comment.
- npftest: clean up and simplify; fix some memleaks to make ASAN happy.

Back to using _NPF_TESTING now that it does not change the semantics of
the calls, but only adds extra functionality.

add an _NPF_RUMP define to expose the sampling function.

Revert previous (unbreak build) - for now anyway.

It turns out _NPF_TESTING is needed for the (rump only) function
npf_state_setsampler() in sys/net/npf/npf_state.c

Comment out _NPF_TESTING (really should be removed)

need libnvpair

NPF: Major rework -- migrate NPF to the libnv library.
- This conversion significantly simplifies the code and moves NPF to
a binary serialisation format (replacing the XML-like format).
- Fix some memory/reference leaks and possibly use-after-free bugs.
- Bump NPF_VERSION as this change makes libnpf incompatible with the
previous versions. Also, different serialisation format means NPF
connection/config saving and loading is not compatible with the
previous versions either.

Thanks to christos@ for extra testing.

branches: 1.20.14; 1.20.16;
need new file

Sync NPF with the version on github: backport standalone NPF changes,
which allow us to create and run separate NPF instances. Minor fixes.
(from rmind@)

remove ptree add lpm

branches: 1.17.2;
Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

add ioconf files for pseudo device attach prototypes

branches: 1.14.2; 1.14.4; 1.14.8;
NPF: partially rewrite the connection tracking mechanism:
- Separate the tracking interface from the storage (state table)
and thus prepare to use a new data structure for the storage.
- Fix some race conditions in NAT association logic.

branches: 1.13.2;
No lint for rumpnet npf library.

rename component.c -> npf_component.c

also include bsd.own.mk, so value for RUMP_NPF_TESTING can come from mk.conf

For now, make it possible to not specify -D_NPF_TESTING by compiling
with RUMP_NPF_TESTING_=no. This in turn makes it possible to use npf
in a rump kernel for real packet filtering instead of just testing.

no change to default

NPF: add support for specifying the interfaces before they are attached.
If an interface is or gets detached, all associated rules and connections
will be deactivated (it might be useful to have an option to invalidate
the associated connections). Once the interface is reattached they will
become active.

Bump NPF_VERSION.

NPF: G/C n-code in favour of BPF byte-code. Delete lots of code, mmm!

branches: 1.7.2;
- NPF connection tracking: rework synchronisation on tracking disable/enable
points and document it. Split the worker thread into a separate module
with an interface, so it could be re-used for other tasks.
- Replace ALG list with arrays and thus hit fewer cache lines.
- Misc bug fixes.

normali{s,z}e

remember to detach and add if_npflog module

NPF:
- Implement dynamic NPF rules. Controlled through npf(3) library of via
npfctl rule command. A rule can be removed using a unique identifier,
returned on addition, or using a key which is SHA1 hash of the rule.
Adjust npftest and add a regression test.
- Improvements to rule inspection mechanism.
- Initial BPF support as an alternative to n-code.
- Minor fixes; bump the version.

This component is not WARNS>3 clean (example: it includes socketvar.h
which does signed-unsigned comparison in an inline function). Why it
compiled at all is one of those marvels of compiler technology.

branches: 1.2.2; 1.2.4;
Implement dynamic NPF extensions interface. An extension consists of
dynamically loaded module (.so) supplementing npfctl(8) and a kernel
module. Move normalisation and logging functionality into their own
extensions. More improvements to come.

branches: 1.1.2;
Move and rename librumpdev_npf to librumpnet_npf.

branches: 1.1.2; 1.1.18;
add ioconf files for pseudo device attach prototypes

rename component.c -> npf_component.c

Run constructor as part of network faction bootstrap, not device
(rumpdev no longer necessary)

branches: 1.2.6;
remember to detach and add if_npflog module

branches: 1.1.2; 1.1.4; 1.1.6;
Move and rename librumpdev_npf to librumpnet_npf.

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.12;
rename component.c -> npf_component.c

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.20;
Move and rename librumpdev_npf to librumpnet_npf.

enabled PPPOE_DEBUG for librumpnet_pppoe* when RUMP_DEBUG is defined

Merge the [pgoyette-compat] branch

branches: 1.1.2; 1.1.18; 1.1.20; 1.1.22;
Rump-ify if_pppoe

From s-yamaguchi@IIJ

branches: 1.1.2; 1.1.18;
Rump-ify if_pppoe

From s-yamaguchi@IIJ

Add missing RCSIDs.

branches: 1.1.2; 1.1.18; 1.1.20; 1.1.22;
Rump-ify if_pppoe

From s-yamaguchi@IIJ

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

branches: 1.6.6;
rename component.c -> shmif_component.c

rename rumpcomp_user.* -> shmif_user.*

branches: 1.4.4;
make the file monitoring hypercalls private to shmif

branches: 1.3.8; 1.3.18;
* make interface a cloner
* use SIOCSLINKSTR for supplying bus filename in case of cloned if

TODO: downing interface, unclone, and some tweaks for robustness

Include a pointer to the beginning of the buffer and add support
to the packet dumper. This helps in situations where the juicy
details are in a bus multiple generations old.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8; 1.1.10;
Add a virtual ethernet interface which uses shared memory as the
bus instead of relying on the host kernel's tap and bridge. This
is much lighterweight approach which does not consume non-pageable
kernel resources.

rename component.c -> shmif_component.c

branches: 1.2.6; 1.2.10; 1.2.20; 1.2.24;
Use vmem for keeping track of unit numbers so that wildcard allocation
works correctly.

remember to commit this file too

this was moved to usr.bin ages ago

branches: 1.10.2; 1.10.6;
un-\240

add -h which prints only the bus header info

branches: 1.8.2; 1.8.4;
truncate pcap output file

Include a timestamp in the frame header. When converting to pcap,
it can give some idea of when packets were sent.

nb. it's the sending host's timestamp, not an observer timestamp
like in the typical pcap case.

Include a pointer to the beginning of the buffer and add support
to the packet dumper. This helps in situations where the juicy
details are in a bus multiple generations old.

Recognize ``-'' for stdout. allows piping output to tcpdump -r -

* include a magic number in the bus format
* simplify offset calculations by making them start from beginning of data

Make shmif memory access slightly more sane. Create a header which
is shared by the interface and the bus analyzer.

pass Wall

Add a little utility to convert shmif bus traffic to a pcap file
which can be then examined with tcpdump -r, wireshark, etc.

shmif: Fix logics for media change and status

- shmif_mediachange: Drop check for if_link_state. Otherwise,
there can be race b/w events in if_link_queue.

- shmif_mediastatus: Set ifm_status appropriately, by which
link state appears in ifconfig(8) "status:" line.

Pointed out by roy@, and taken from his codes in vether(4). Thanks!!

shmif: export LOCK_* definitions

They will be used by upcoming shmif_pcapin.

shmem(4): Fix typo in comment: AFT -> ATF.

Also fix grammar (if I understood correctly what this meant: rump
servers written in C, rather than set up via shell scripts around
rump_server invoking ifconfig).

No functional change intended.

shmif: support media

It enables to link-down shmif by ifconfig media none and link-up
again by media auto.

shmif: change behaviors about link states

- Change the link state to UP on ifconfig linkstr
- This behavior emulates physical devices
- Change the link state to UNKNOWN on ifconfig -linkstr just in case
- Reject sending/receiving packets if the link state is DOWN
- Permit to send/receive packets on UNKNOWN, which is required
to unbreak some ATF tests written in C

branches: 1.84.4; 1.84.10;
if_shmem(4): Use membar_acquire/release for lock acquire/release.

shmif: support ALTQ

if_attach and if_initialize cannot fail, don't test return value

These were originally made failable back in 2017 when if_initialize
allocated a softint in every interface for link state changes, so
that it could fail gracefully instead of panicking:

https://mail-index.NetBSD.org/source-changes/2017/10/23/msg089053.html

However, this spawned many seldom- or never-tested error branches,
which are risky to have around. And that softint in every interface
has since been replaced by a single global workqueue, because link
state changes require thread context but not low latency or high
throughput:

https://mail-index.NetBSD.org/source-changes/2020/02/06/msg113759.html

So there is no longer any reason for if_initialize to fail. (The
subroutine if_stats_init can't fail because percpu_alloc can't fail
either.)

There is a snag: the softint_establish in if_percpuq_create could
fail, potentially leading to bad consequences later on trying to use
the softint. This change doesn't introduce any new bugs because of
the snag -- if_percpuq_attach was already broken. However, the snag
can be better addressed without spawning error branches, either by
using a single softint or making softints less scarce.

(Separate commit will change the signatures of if_attach and
if_initialize to return void, scheduled to ride whatever is the next
convenient kernel bump.)

Patch and testing on amd64 and evbmips64-eb by maya@; commit message
soliloquy, and compile-testing on evbppc/i386/earmv7hf, by me.

branches: 1.81.10;
shmif: reduce the number of calls of cprng(9)

shmif: s/sc_uuid/sc_uid/

It's not UUID :-/

shmif: use cprng_strong64 instead of cprng_fast64 to generate a unique ID

shmif uses random bytes generated by cprng(9) as a unique device ID
between rump kernels to identify packets fed by itself and not receive
them. So if generated bytes are identical between shmif interfaces on
different rump kernels, shmif may drop incoming packets unintentionally.
This is one cause of recent ATF test failures of IPsec.

Fix it by using cprng_strong64 instead of cprng_fast64. This is a
workaround and we should also investigate why cprng_fast64 starts
failing on rump kernels, although using cprng_strong64 in initialization
itself is feasible.

Fix PR kern/54897

shmif: use cprng_strong32 to generate random bytes for a MAC address

cprng_fast32 sometimes returns indentical bytes, which look
"20:0e:11:33" in a MAC address, on different rump_server instances.
That leads MAC address duplications resulting in a test failure.

Fix it by using cprng_strong32 instead of cprng_fast32. However
we should rather fix cprng_fast32 (or rump itself) somehow.

The fix mitigates PR kern/54897 but test failures due to other
causes still remain.

Adopt <net/if_stats.h>.

branches: 1.76.6;
Add TX/RX offload capabilities to shmif(4). They are emulated in
software by ether_sw_offload_[tr]x().

For rump kernels, if_capabilities for shmemif(4) can be specified
by environmental variable RUMP_SHMIF_CAPENABLE:

setenv RUMP_SHMIF_CAPENABLE 0x7ff80 (all offload)
setenv RUMP_SHMIF_CAPENABLE 0x6aa80 (all TX)
setenv RUMP_SHMIF_CAPENABLE 0x15500 (all RX)

part of PR kern/53562
OK msaitoh

branches: 1.75.2;
Implement the BPF direction filter (BIOC[GS]DIRECTION). It provides backward
compatibility with BIOC[GS]SEESENT ioctl. The userland interface is the same
as FreeBSD.

This change also fixes a bug that the direction is misunderstand on some
environment by passing the direction to bpf_mtap*() instead of checking
m->m_pkthdr.rcvif.

branches: 1.74.2;
Fix compile error.

If if_initialize() failed in the attach function, free resources and return.

branches: 1.72.8;
Fix that rump.ifconfig shmifN destroy hangs up

rump.ifconfig shmifN destroy sometimes hangs up on closing a file
descriptor of kqueue under heavy load. It seems it happens because of
a race condition between closing a fd and kevent to the same fd on
another kthread for packet Rx. Fix it by executing the close operation
after the kthread left.

Fix handling return value of rumpcomp_shmif_watchwait

Move bpf_mtap and if_ipackets++ on Rx of each driver to percpuq if_input

The benefits of the change are:
- We can reduce codes
- We can provide the same behavior between drivers
- Where/When if_ipackets is counted up
- Note that some drivers still update packet statistics in their own
way (periodical update)
- Moved bpf_mtap run in softint
- This makes it easy to MP-ify bpf

Proposed on tech-kern and tech-net

branches: 1.69.2;
KNF. Remove extra spaces. No functional change.

Use curlwp_bind and curlwp_bindx instead of open-coding LP_BOUND

Introduce m_set_rcvif and m_reset_rcvif

The API is used to set (or reset) a received interface of a mbuf.
They are counterpart of m_get_rcvif, which will come in another
commit, hide internal of rcvif operation, and reduce the diff of
the upcoming change.

No functional change.

Prevent LWP migrations between CPUs during upper layer processing

This is a contract of psref(9) that is used by upper layer componenets,
e.g., bridge(4).

Introduce softint-based if_input

This change intends to run the whole network stack in softint context
(or normal LWP), not hardware interrupt context. Note that the work is
still incomplete by this change; to that end, we also have to softint-ify
if_link_state_change (and bpf) which can still run in hardware interrupt.

This change softint-ifies at ifp->if_input that is called from
each device driver (and ieee80211_input) to ensure Layer 2 runs
in softint (e.g., ether_input and bridge_input). To this end,
we provide a framework (called percpuq) that utlizes softint(9)
and percpu ifqueues. With this patch, rxintr of most drivers just
queues received packets and schedules a softint, and the softint
dequeues packets and does rest packet processing.

To minimize changes to each driver, percpuq is allocated in struct
ifnet for now and that is initialized by default (in if_attach).
We probably have to move percpuq to softc of each driver, but it's
future work. At this point, only wm(4) has percpuq in its softc
as a reference implementation.

Additional information including performance numbers can be found
in the thread at tech-kern@ and tech-net@:
http://mail-index.netbsd.org/tech-kern/2016/01/14/msg019997.html

Acknowledgment: riastradh@ greatly helped this work.
Thank you very much!

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.63.2;
Make shmif SIMPLEX

Add a sender field to a packet header on a shmif bus to identify
and ignore packets sent by itself.

This makes shmif work with bridges.

ok pooka@

branches: 1.62.2;
Count packets in if_shmem

ok @pooka

Add missing __diagused in rump code

branches: 1.60.2;
kill sprintf

rename rumpcomp_user.* -> shmif_user.*

Remove busversion.

In recv, align data after ether_header at _ALIGN_BYTES.

branches: 1.56.2; 1.56.4;
sauce previous with a comment

Ignore too short packets. This condition is true especially for the
first packet on a new bus (len == 0). Everything else in the stack
besides bpf seemed to be able to deal with one, though.

Three cheers for the mighty C type system that doesn't recognize the
difference between an enum and an integer. Due to wrong parameter order,
the lock backoff routine ended up sleeping 1 million seconds instead
of 1ms. On the plus side, we got some sort of idea how often the shmif
spinlock backoff routine is hit during a standard test run.

Make hypercall calling conventions consistent: iff a hypercall can fail,
it returns an int containing the error value.

Reduce hypercalls related to reading to essentially an amalgamation
of readv and preadv. ditto for writing. Hypercalls are so seldomly
used that it doesn't justify 3x the calls for syntactic sugar.

add a private hypercall to map the bus into memory

Improve the time-related hypercalls so that's it's possible to
sleep until an absolute time on the host's monotonic clock (should
something like that be supported).

* remove the unused "opaque" parameter
* fix some typos in the previous

make the file monitoring hypercalls private to shmif

fix debug printf formats

Pass up all multicast addresses, not just broadcast. Among other
things, makes IPv6 work over this interface.

Do not assume that O_FOO flags have matching values in the rump kernel
and hypervisor.

branches: 1.44.4; 1.44.8;
First step of random number subsystem rework described in
<20111022023242.BA26F14A158@mail.netbsd.org>. This change includes
the following:

An initial cleanup and minor reorganization of the entropy pool
code in sys/dev/rnd.c and sys/dev/rndpool.c. Several bugs are
fixed. Some effort is made to accumulate entropy more quickly at
boot time.

A generic interface, "rndsink", is added, for stream generators to
request that they be re-keyed with good quality entropy from the pool
as soon as it is available.

The arc4random()/arc4randbytes() implementation in libkern is
adjusted to use the rndsink interface for rekeying, which helps
address the problem of low-quality keys at boot time.

An implementation of the FIPS 140-2 statistical tests for random
number generator quality is provided (libkern/rngtest.c). This
is based on Greg Rose's implementation from Qualcomm.

A new random stream generator, nist_ctr_drbg, is provided. It is
based on an implementation of the NIST SP800-90 CTR_DRBG by
Henric Jungheim. This generator users AES in a modified counter
mode to generate a backtracking-resistant random stream.

An abstraction layer, "cprng", is provided for in-kernel consumers
of randomness. The arc4random/arc4randbytes API is deprecated for
in-kernel use. It is replaced by "cprng_strong". The current
cprng_fast implementation wraps the existing arc4random
implementation. The current cprng_strong implementation wraps the
new CTR_DRBG implementation. Both interfaces are rekeyed from
the entropy pool automatically at intervals justifiable from best
current cryptographic practice.

In some quick tests, cprng_fast() is about the same speed as
the old arc4randbytes(), and cprng_strong() is about 20% faster
than rnd_extract_data(). Performance is expected to improve.

The AES code in src/crypto/rijndael is no longer an optional
kernel component, as it is required by cprng_strong, which is
not an optional kernel component.

The entropy pool output is subjected to the rngtest tests at
startup time; if it fails, the system will reboot. There is
approximately a 3/10000 chance of a false positive from these
tests. Entropy pool _input_ from hardware random numbers is
subjected to the rngtest tests at attach time, as well as the
FIPS continuous-output test, to detect bad or stuck hardware
RNGs; if any are detected, they are detached, but the system
continues to run.

A problem with rndctl(8) is fixed -- datastructures with
pointers in arrays are no longer passed to userspace (this
was not a security problem, but rather a major issue for
compat32). A new kernel will require a new rndctl.

The sysctl kern.arandom() and kern.urandom() nodes are hooked
up to the new generators, but the /dev/*random pseudodevices
are not, yet.

Manual pages for the new kernel interfaces are forthcoming.

branches: 1.43.2;
Report vmem(9) errors out-of-band so that we can use vmem(9) to manage
ranges that include the least and the greatest vmem_addr_t. Update
vmem(9) uses throughout the kernel. Slightly expand on the tests in
subr_vmem.c, which still pass. I've been running a kernel with this
patch without any trouble.

Use VMEM_ADDR_MIN and VMEM_ADDR_MAX.

Introduce a couple of new constants, VMEM_ADDR_MIN (the least possible
address in a vmem(9) arena, 0) and VMEM_ADDR_MAX (the maximum possible
address, currently 0xFFFFFFFF). Modify several boundary conditions so
that a vmem(9) arena can allocate ranges including VMEM_ADDR_MAX.
Update documentation and tests.

These changes pass the tests in sys/kern/subr_vmem.c. To compile the
and run the test program, run "cd sys/kern/ && gcc -DVMEM_SANITY -o
subr_vmem ./subr_vmem.c && ./subr_vmem".

Rename slightly misleading KTHREAD_JOINABLE to KTHREAD_MUSTJOIN.

Update copyright statements.

no functional change.

make the if-else logic more obvious

After my change to the "interface accepts this packet" logic
yesterday the CARP test stopped working, since CARP depends on
IFF_PROMISC (which was previously always accidentally enabled).
While making the interface honor IFF_PROMISC, also make it compare
the received frame's address against ifp->if_sadl instead of a
local enaddr value we cached when the interface was created.

Don't assume rump kernel PAGE_SIZE and host page size are the same.

Support bpf. shmif_dumpbus(1) can be used for much the same effect,
but sometimes it's just more convenient to run tcpdump live.

Pass packet up if it's *for* us, not if it's from someone else.
This fixes a rather curious forwarding/redirect/etc. storm which
happened when there were >2 shmif kernels on the same shmbus with
ip forwarding set on. (at least it stress-tested other code ;)

branches: 1.33.2;
Allow creation with NULL busname (to be later set with SIOCSLINKSTR).

Support destroy in shmif.

Use vmem for keeping track of unit numbers so that wildcard allocation
works correctly.

"fix" completely crackheaded code w/ uninitialized use,
missed as usual by the wonderful -g -O0

* make interface a cloner
* use SIOCSLINKSTR for supplying bus filename in case of cloned if

TODO: downing interface, unclone, and some tweaks for robustness

Prefault bus pages in driver attachment. This seems to work around
weird corruption I've been seeing (most likely a host kernel bug).

For more details, see thread at:
http://mail-index.netbsd.org/tech-kern/2010/08/17/msg008749.html

* fix off-by-wrap case where current datagram aligns exactly with
the end of the bus
* clarify the "can we still use the device's next pointer" calculation
and move it to its own routine
* sprinkle dprintf

simplify, improve, etc.

reset pktsize each loop

reset wrap where necessary

Move the lockops together with the interface -- they are needed
only at runtime.

Take kernel lock before passing data to if_input. This is in line
with IPL_NET interrupts generally not being MPSAFE.

Don't do timestamping with buslock held. it's the little things ...

Include a timestamp in the frame header. When converting to pcap,
it can give some idea of when packets were sent.

nb. it's the sending host's timestamp, not an observer timestamp
like in the typical pcap case.

Include a pointer to the beginning of the buffer and add support
to the packet dumper. This helps in situations where the juicy
details are in a bus multiple generations old.

further simplify & fix calculations

* include a magic number in the bus format
* simplify offset calculations by making them start from beginning of data

Make shmif memory access slightly more sane. Create a header which
is shared by the interface and the bus analyzer.

* remove some magic numbers from the code
* include bus version number in header just in case we want to examine
bus traffic at some point in the future

Change bus header a little: reserve only 32bits for the lock and
use 32bit atomic ops to handle it. Begin data from 0x10 instead
of 0x14.

* use atomic ops instead of __cpu_simple_luck
* this interface is un-IFF_SIMPLEX

* print interface number, backend path and ethernet address for dmesg
* make kassert more demanding

* increase bus size so that we don't wrap so quickly when NFS
flushes writes
* verbosize debug print a bit

branches: 1.10.2; 1.10.4;
fix comment

use autogenerated prototype

printf -> rumpuser_dprintf
(can't use printf while holding spinlock)

Filter out ENETRESET from ether_ioctl() since we aren't interested
in multicast hugging.

branches: 1.6.2; 1.6.4;
let drivers define DPRINTF

* allow to specify PROT_READ/PROT_WRITE when mmapping a file
* add msync

branches: 1.4.2;
Create receive thread only in if_start() to make sure it happens
after the we have been attached to the ethernet framework.
XXX: if_stop is still unimplemented

add missing atomic.h include

don't require the ifnum return pointer.

Add a virtual ethernet interface which uses shared memory as the
bus instead of relying on the host kernel's tap and bridge. This
is much lighterweight approach which does not consume non-pageable
kernel resources.

rename rumpcomp_user.* -> shmif_user.*

OpenBSD has kqueue

Use kqueue on *BSD, not just NetBSD.

branches: 1.12.2; 1.12.4;
On Linux, pass the inotify descriptor up so that we can correctly read
it in the wait() routine.

Include necessary headers on Linux

Translate error codes between the hypervisor and rump kernel.

fix non-NetBSD implementation

Make hypercall calling conventions consistent: iff a hypercall can fail,
it returns an int containing the error value.

don't build in kernel build.

add a private hypercall to map the bus into memory

some more headers are required by the third implementation

include event.h only where used

be a bit less sloppy with errno

* remove the unused "opaque" parameter
* fix some typos in the previous

make the file monitoring hypercalls private to shmif

rename rumpcomp_user.* -> shmif_user.*

branches: 1.4.4; 1.4.6;
Make hypercall calling conventions consistent: iff a hypercall can fail,
it returns an int containing the error value.

add a private hypercall to map the bus into memory

* remove the unused "opaque" parameter
* fix some typos in the previous

make the file monitoring hypercalls private to shmif

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.28; 1.1.46;
Add a virtual ethernet interface which uses shared memory as the
bus instead of relying on the host kernel's tap and bridge. This
is much lighterweight approach which does not consume non-pageable
kernel resources.

Make shmif buildable when DRPINTF enabled

use _KERNEL_RCSID only in _KERNEL, _RCSID elsewhere

header massage, mostly improves portability

branches: 1.9.4; 1.9.14; 1.9.18;
Update copyright statements.

no functional change.

branches: 1.8.2; 1.8.6;
make this happy to compile standalone

branches: 1.7.2;
Fix hopefully last off-by-one: if we fill the bus, we must also
advance the "first" pointer. This problem triggered only if the
bus was filled in the first round, since the first pointer is at
the end-of-bus only for the bootstrap round.

* fix off-by-wrap case where current datagram aligns exactly with
the end of the bus
* clarify the "can we still use the device's next pointer" calculation
and move it to its own routine
* sprinkle dprintf

branches: 1.5.2;
simplify, improve, etc.

Move the lockops together with the interface -- they are needed
only at runtime.

introduce a sleep to trying to grab the bus

Include a timestamp in the frame header. When converting to pcap,
it can give some idea of when packets were sent.

nb. it's the sending host's timestamp, not an observer timestamp
like in the typical pcap case.

Include a pointer to the beginning of the buffer and add support
to the packet dumper. This helps in situations where the juicy
details are in a bus multiple generations old.

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.12;
rename component.c -> shmif_component.c

Protect __KERNEL_RCSID. It isn't available when compile rumpkernels under e.g. Linux.

Merge the [pgoyette-compat] branch

Add missing RCSIDs.

branches: 1.2.2;
Unconditionally include <unistd.h>, as we use ftruncate() unconditionally
too.
Reported (with patch) by Antonio Huete Jimenez in PR 53153, slightly
modified by me.

branches: 1.1.4; 1.1.6; 1.1.10; 1.1.34;
rename rumpcomp_user.* -> shmif_user.*

branches: 1.1.4; 1.1.6; 1.1.10;
rename rumpcomp_user.* -> shmif_user.*

shmif: export LOCK_* definitions

They will be used by upcoming shmif_pcapin.

branches: 1.11.22; 1.11.28;
make constant unsigned

branches: 1.10.20;
Make shmif buildable when DRPINTF enabled

Bump SHMIF_VERSION

Make shmif SIMPLEX

Add a sender field to a packet header on a shmif bus to identify
and ignore packets sent by itself.

This makes shmif work with bridges.

ok pooka@

branches: 1.7.4;
header massage, mostly improves portability

branches: 1.6.4; 1.6.14; 1.6.18;
Update copyright statements.

no functional change.

branches: 1.5.2; 1.5.4; 1.5.6; 1.5.10;
Move the lockops together with the interface -- they are needed
only at runtime.

Include a timestamp in the frame header. When converting to pcap,
it can give some idea of when packets were sent.

nb. it's the sending host's timestamp, not an observer timestamp
like in the typical pcap case.

Include a pointer to the beginning of the buffer and add support
to the packet dumper. This helps in situations where the juicy
details are in a bus multiple generations old.

* include a magic number in the bus format
* simplify offset calculations by making them start from beginning of data

Make shmif memory access slightly more sane. Create a header which
is shared by the interface and the bus analyzer.

Put the kernelside rump kernel headers into <rump-sys> instead of
sprinkling them around the faction directories. Avoids having
to add a CPPFLAGS (or several) to pretty much every component
Makefile.

Leave compat headers around in the old locations.

The commit changes some autogenerated files, but I'll fix the
generators shortly and regen.

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

branches: 1.8.6;
rename component.c -> sockin_component.c

rename rumpcomp_user.* -> sockin_user.*

branches: 1.6.6;
Move the rumpuser_net set of hypercalls to be a private to the sockin
component. This cleans up the generic hypercall interfaces from ones
specific to only one component. They should always have been private,
but the infrastructure to "make it so" didn't exist earlier.

no functional change

branches: 1.5.12; 1.5.22;
Use linker script to make __start/stop_link_set_modules be present
in libs built with binutils >=2.19. This is a less error-prone
method than the previous where components had to be tagged in the
Makefile as modules (and if they weren't, things broke. and vice
versa).

binutils 2.19 has changed the old behaviour of defining __start_SECTNAME
for orphaned sections to using PROVIDE. What this means is that
unless a rump component internally references that symbol, it will
not be included in the component shared library, and hence cannot
be referenced when the component is loaded. Add a workaround which
works both with 2.16 and 2.19: force a reference to the __start
symbol internally and hence retain it in the resulting library.

Use a bunch of weak symbols to determine which network components
are present. This works in userspace as opposed relying in link
sets, which fail miserably. Later, when the networking stack
becomes modularized, we can move to a dynamic scheme like with file
systems.

Also, this change allows us to do proper autoconfig, namely attach
the loopback interface iff it is present.

branches: 1.2.2; 1.2.4;
Convert compile-time SOCKIN_NOTHREADS into runtime rump_threads check.