177 lines
6.6 KiB
Markdown
177 lines
6.6 KiB
Markdown
# Red Bear OS Networking: RTL8125 + netctl
|
||
|
||
## Native stack
|
||
|
||
Red Bear uses the native Redox wired networking path already present in the base tree:
|
||
|
||
`pcid-spawner` → native NIC daemon (`rtl8168d`, `e1000d`, `ixgbed`, `virtio-netd`) → `network.*`
|
||
scheme → `smolnetd` → `dhcpd` / `netcfg`.
|
||
|
||
This change keeps RTL8125 in that native path instead of trying to introduce a Linux netdevice,
|
||
`sk_buff`, or NAPI compatibility layer into `linux-kpi`.
|
||
|
||
## RTL8125 path
|
||
|
||
- Autoload now matches `10ec:8125` in `recipes/core/base/source/drivers/net/rtl8168d/config.toml`.
|
||
- The existing Realtek driver binary remains the autoload target (`rtl8168d`).
|
||
- The daemon names RTL8125 devices distinctly in its `network.*` scheme name suffix.
|
||
|
||
This is the narrowest viable implementation path in the current tree. It reuses the existing
|
||
userspace driver, PCI spawn, and netstack plumbing already proven for the native Realtek path.
|
||
|
||
## relibc networking surface
|
||
|
||
The Redox-facing libc networking surface was extended to stop reporting a fake `stub` interface:
|
||
|
||
- `net/if.h` now exposes a real `eth0`-based view of the active interface model
|
||
- `ifaddrs.h` now returns a populated `eth0` entry
|
||
- Redox `ioctl()` now answers the common read-only `SIOCGIF*` queries used by interface-aware apps
|
||
- `netinet/in.h` now includes `in6_pktinfo`
|
||
- a minimal `resolv.h` is now generated in relibc
|
||
|
||
This is intentionally aligned with the current single-active-interface design in `smolnetd` and
|
||
`netcfg`.
|
||
|
||
## netctl
|
||
|
||
Red Bear ships a Redox-native `netctl` compatibility command in `redbear-netctl`.
|
||
|
||
### Supported profile subset
|
||
|
||
- `Interface=eth0`
|
||
- `Connection=ethernet`
|
||
- `IP=dhcp`
|
||
- `IP=static`
|
||
- `Address=('a.b.c.d/prefix')`
|
||
- `Gateway='a.b.c.d'`
|
||
- `DNS=('a.b.c.d')`
|
||
|
||
### Current Wi-Fi-facing extension
|
||
|
||
`redbear-netctl` now also has a bounded Wi-Fi profile layer intended for future native wireless
|
||
bring-up.
|
||
|
||
Current Wi-Fi-facing fields:
|
||
|
||
- `Interface=wlan0` (or another future wireless interface name)
|
||
- `Connection=wifi`
|
||
- `SSID='...'`
|
||
- `Security=open|wpa2-psk`
|
||
- `Key='...'` / `Passphrase='...'`
|
||
|
||
Current boundary:
|
||
|
||
- `redbear-netctl` can parse and start these profiles
|
||
- it writes Wi-Fi intent and credentials into the in-tree `/scheme/wifictl` control surface
|
||
- it reuses the native `netcfg`/`dhcpd` handoff only after association
|
||
- it is **not** the supplicant and does not currently implement scan/auth/association itself
|
||
|
||
Current orchestration order for Intel Wi‑Fi profiles:
|
||
|
||
- `prepare`
|
||
- `init-transport`
|
||
- `activate-nic`
|
||
- `connect`
|
||
|
||
Current orchestration order for `netctl scan` on Intel Wi‑Fi profiles:
|
||
|
||
- `prepare`
|
||
- `init-transport`
|
||
- `activate-nic`
|
||
- `scan`
|
||
|
||
The current Intel backend will not attempt `scan` or `connect` until transport initialization has
|
||
been attempted.
|
||
|
||
The current user-facing Wi‑Fi subcommands are:
|
||
|
||
- `netctl scan <profile|iface>`
|
||
- `netctl status <profile>` with Wi‑Fi status, link state, firmware status, transport status, transport-init status, activation status, and last error
|
||
|
||
The current `redbear-wifictl` daemon provides:
|
||
|
||
- a bounded stub backend for end-to-end profile/control validation
|
||
- an Intel-oriented backend boundary that detects Intel wireless-class PCI devices
|
||
- firmware-family and firmware-presence reporting for the Intel target boundary
|
||
- a bounded `prepare` step before connect
|
||
- transport-readiness reporting for the detected Intel device
|
||
- a bounded `scan` action and per-interface `scan-results`
|
||
- a bounded PCI transport-prep action before connect
|
||
- a bounded `init-transport` state after preparation and before connect
|
||
- a bounded `activate-nic` state after transport initialization and before connect/scan
|
||
- per-interface Wi-Fi state files under `/scheme/wifictl/ifaces/<iface>/...`
|
||
|
||
Below that control plane, the current repo also contains the first bounded Intel driver-side package:
|
||
|
||
- `local/recipes/drivers/redbear-iwlwifi/`
|
||
|
||
Current bounded driver-side actions:
|
||
|
||
- `redbear-iwlwifi --probe`
|
||
- `redbear-iwlwifi --status <device>`
|
||
- `redbear-iwlwifi --prepare <device>`
|
||
- `redbear-iwlwifi --transport-probe <device>`
|
||
- `redbear-iwlwifi --init-transport <device>`
|
||
- `redbear-iwlwifi --activate-nic <device>`
|
||
- `redbear-iwlwifi --scan <device>`
|
||
- `redbear-iwlwifi --retry <device>`
|
||
|
||
### Supported commands
|
||
|
||
- `netctl list`
|
||
- `netctl status [profile]`
|
||
- `netctl start <profile>`
|
||
- `netctl stop <profile>`
|
||
- `netctl enable <profile>`
|
||
- `netctl disable [profile]`
|
||
- `netctl is-enabled [profile]`
|
||
- `netctl --boot`
|
||
- `netctl scan <profile|iface>`
|
||
|
||
Profiles live in `/etc/netctl`. Shipped examples live in `/etc/netctl/examples/`.
|
||
|
||
### Boot integration
|
||
|
||
Red Bear configs install `/usr/lib/init.d/12_netctl.service`, which runs:
|
||
|
||
```text
|
||
netctl --boot
|
||
```
|
||
|
||
If `/etc/netctl/active` contains a profile name, that profile is applied during boot after the
|
||
base networking services have started.
|
||
|
||
## Validation notes
|
||
|
||
- `redbear-netctl` was type-checked and smoke-tested with a fake runtime root by exercising:
|
||
`list`, `enable`, `status`, and `start`.
|
||
- the Wi-Fi profile flow was also exercised with a fake runtime root by starting a
|
||
`Connection=wifi` / `Interface=wlan0` profile and verifying that `SSID`, `Security`, `Key`, and
|
||
`connect` were written to the fake `/scheme/wifictl` tree while `status` reported the Wi-Fi
|
||
profile correctly
|
||
- `rtl8168d` type-checks with the RTL8125 autoload configuration in place.
|
||
- relibc type-checks with the interface and header updates in place.
|
||
- `./local/scripts/validate-vm-network-baseline.sh` verifies the repo-level VM boot chain for
|
||
`redbear-minimal`: `pcid-spawner` → `smolnetd` → `dhcpd` → `netctl --boot` → `wired-dhcp`.
|
||
- `./local/scripts/test-vm-network-qemu.sh` launches a VirtIO-backed QEMU run for the same Phase 2
|
||
baseline and prints the in-guest validation commands to run.
|
||
On x86_64 hosts it now fails fast unless usable OVMF/edk2 UEFI firmware is installed, because
|
||
otherwise the helper can fall through a misleading BIOS/iPXE boot path before Red Bear OS ever
|
||
starts.
|
||
- `./local/scripts/test-vm-network-runtime.sh` is the in-guest check for the same baseline: it
|
||
verifies `/scheme/pci`, `/scheme/netcfg`, the active netctl profile, visible `network.*`
|
||
schemes, and the current `eth0` address.
|
||
|
||
During reassessment, the QEMU/UEFI VM baseline reached a real guest login prompt and
|
||
`redbear-info --json` reported:
|
||
|
||
- `virtio_net_present: true`
|
||
- configured `eth0` address `10.0.2.15/24`
|
||
- default route via `10.0.2.2`
|
||
- visible `network.pci-0000-00-03.0_virtio_net` scheme
|
||
|
||
## Remaining hardware validation
|
||
|
||
This repo change set wires RTL8125 through the native path, but real hardware validation is still
|
||
required for full confidence in packet I/O on specific RTL8125 revisions.
|