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.