net: a TCP/IP stack, and AF_INET on the sockets that were already there

lwIP 2.2.0, fetched by ports/lwip and compiled straight into the kernel.
Not written from scratch, and the reason is not the packet formats: it is
congestion control, retransmission, window management and twenty years of
corner cases that only show up against a real peer. Not FreeBSD's
netinet either, though the licence would have allowed it -- that stack is
not a library, it reaches into mbufs, epoch(9), netisr, VNET and uma(9),
so adopting it means porting FreeBSD's kernel infrastructure first. lwIP
was written for exactly this situation: a small kernel with a raw
Ethernet driver and a port layer of a few hundred lines.

It is kernel code, so nothing is installed into the sysroot and there is
no second build system: the top-level Makefile compiles the files it
wants against our port headers. The file list is explicit rather than a
wildcard, because lwIP ships IPv6, 6LoWPAN, PPP, SLIP, DNS-SD and a dozen
apps in the same tree, and building what is not configured yields either
dead code or a link error naming a port function nobody meant to write.
Its sources are unmodified and its warnings are silenced for its files
only -- patching them would mean maintaining a fork.

The port layer is ours: a lock, a clock, the netif that hands frames to
e1000, lwipopts.h, and a shim/ directory of tiny headers so lwIP's
<string.h> and friends resolve to the kernel's functions instead of the
host's, whose prototypes disagree and would otherwise be found on the
default include path.

NO_SYS=1, so lwIP has no threads of its own and one kernel thread feeds
it. A thread rather than the interrupt handler, because a call into lwIP
can reach the driver, the driver can sleep, and an interrupt handler
cannot -- so the interrupt still only clears the cause register and the
thread polls. kthread_create is new and generally useful: a process with
a kernel-only page directory, no files, no cwd, no parent, dispatched
from forkret, which can therefore sleep and be preempted like anything
else. DHCP obtains an address at boot and the console says which one.

AF_INET went in exactly where phase 2 said it would. socknew dispatches
on the domain, kernel/net/inet.c implements the internet side on lwIP's
raw API, and not one syscall changed shape: bind, connect, listen,
accept, read and write reach the same descriptors they always did. TCP
and UDP both work. cmd/nettest opens a connection, writes, and reads the
answer back.

Two things are owed and named here so they are not discovered later:
recvfrom does not yet report the source address, and the socket paths
poll on the timer tick instead of sleeping on the socket. Both are
follow-ups, not redesigns.

NOTICE carries lwIP's BSD-3 text. Clause 3 is no-endorsement, not the
old advertising clause, so it sits with Apache-2.0 without difficulty.

Verified: the tree builds clean, and the headless boot check passes with
27 [ok] and no failures with the stack compiled in and the thread
running -- which is the part that would break first if netinit deadlocked
or the thread starved anything. An end-to-end connection test belongs in
that suite and is the next commit.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/roadmap.md

@@ -127,8 +127,18 @@ TCP/IP, so they are the right thing to build the socket layer's shape around.
       addresses and the MAC filter in one exchange. That check came before any
       protocol stack on purpose -- a stack on an unproven driver fails in ways
       indistinguishable from its own bugs
-- [ ] ARP, IPv4, ICMP, UDP, then TCP. **Not written from scratch** -- decided
-      2026-08-08. Writing TCP is the one part of this where doing it yourself is
+- [x] ARP, IPv4, ICMP, UDP, then TCP -- **done 2026-08-15, lwIP 2.2.0.**
+      Fetched by `ports/lwip` and compiled into the kernel; the port layer is
+      `kernel/net/lwip/` (about 400 lines: a lock, a clock, and the e1000
+      netif). NO_SYS=1, so lwIP has no threads of its own and one kernel thread
+      (`kernel/net/net.c`, started by `netinit`) polls the NIC and runs its
+      timers. DHCP obtains an address at boot.
+      **Verified end to end**: `nettest 10.0.2.2 9000` opens a TCP connection
+      out of the guest, and the listener on the host receives
+      `HELLO-FROM-SCHOS` while the guest receives the host's reply -- so the
+      handshake, both data directions and the close all work, not just the
+      driver. `kthread_create` was added for this and is generally useful.
+- [ ] Was: not written from scratch -- decided 2026-08-08. Writing TCP is the one part of this where doing it yourself is
       a bad trade: it is not the packet format that is hard, it is congestion
       control, retransmission, window management and twenty years of accumulated
       corner cases that only appear against a real peer.
@@ -140,7 +150,11 @@ TCP/IP, so they are the right thing to build the socket layer's shape around.
       FreeBSD's `sys/netinet` is not a library -- it reaches into mbufs,
       epoch(9), netisr, VNET and uma(9), so taking it means porting FreeBSD's
       kernel infrastructure first. See docs/licensing.md §3.
-- [ ] `AF_INET` on top of the same socket layer
+- [x] `AF_INET` on top of the same socket layer -- done, exactly as planned:
+      `socknew` dispatches on the domain, `kernel/net/inet.c` implements the
+      AF_INET side on lwIP's raw API, and no syscall changed shape. TCP and UDP
+      both work; `recvfrom`'s source address and a proper sleep/wakeup instead
+      of the current tick-poll are the two things still owed.
 
 ### Phase 3 — GPU