Files
RedBear-OS/local/docs/networking-validation-log.md
T
vasilito b20f5f587b local/docs: add networking-validation-log.md + update §15 audit status
NETWORKING-IMPROVEMENT-PLAN.md:803 referenced a non-existent file
'local/docs/networking-validation-log.md' (Finding F19 from audit).
Created that file as the canonical per-run bare-metal networking
validation log, cross-referencing:
- HARDWARE-NETWORKING-INVENTORY.md (what hardware is available)
- HARDWARE-VALIDATION-MATRIX.md (the state of validation)
- FIREWALL-VALIDATION-LOG.md (netfilter scenario validation)
- USB-VALIDATION-RUNBOOK.md (USB controller validation)

Document structure: each run entry records hardware, software versions,
commands, results, regressions, fixes. Open tasks: acquire USB-C
dongle, Threadripper NIC inventory, USB Bluetooth adapter, first run.

Also updated NETWORKING-AND-DRIVERS-CODE-ASSESSMENT-2026-07-27.md §15.1
to reflect this round's fixes (config includes, recipe versions,
submodule CRITICAL fixes: BufferPool zero-fill, xHCI bounds, e1000d
bounds, rtl8139d/rtl8168d panic→exit).

Also documents that the openssh IPv4-only sed workaround was
correctly identified as needing a local fork (local/recipes/net/openssh/)
to fix properly, NOT a direct mainline edit (per AGENTS.md).
2026-07-27 15:37:24 +09:00

77 lines
3.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Red Bear OS Networking Validation Log
**Status:** Staged (2026-07-27). See [HARDWARE-VALIDATION-MATRIX.md](./HARDWARE-VALIDATION-MATRIX.md)
for the live cross-component matrix and [HARDWARE-NETWORKING-INVENTORY.md](./HARDWARE-NETWORKING-INVENTORY.md)
for per-driver hardware availability.
## Purpose
This document is the canonical per-run log of bare-metal networking validation activities for
Red Bear OS. Each run records:
- Hardware under test (machine, NIC model, BIOS/UEFI version)
- Software versions (kernel, relibc, netstack, drivers)
- Test commands executed
- Observed results
- New regressions or fixes
## Related Documents
This log is one of three coordinated artifacts. Read them in this order:
1. [HARDWARE-NETWORKING-INVENTORY.md](./HARDWARE-NETWORKING-INVENTORY.md) — *what* hardware
is available for validation. Tracks test bench inventory, per-driver hardware availability,
and acquisition priority list.
2. [HARDWARE-VALIDATION-MATRIX.md](./HARDWARE-VALIDATION-MATRIX.md) — *the state* of validation
per component. Tracks QEMU / bare-metal / hardware columns and gates the production-readiness
status.
3. This document — *the per-run record* of validation activities that update the matrix.
Per the project's evidence policy (per the [NETWORKING-IMPROVEMENT-PLAN.md](./NETWORKING-IMPROVEMENT-PLAN.md)
§Validation Evidence Requirements), every "validated" claim in any plan or doc must be backed
by an entry in this log.
## Format
Each run entry should follow this structure (Markdown):
```markdown
## YYYY-MM-DD — <Test bench> — <Operator>
**Hardware:** <machine> · <NIC model> · <PCI IDs>
**Software:** Red Bear OS <branch> · kernel <hash> · relibc <hash> · netstack <hash>
**Scope:** <what was tested, e.g. "e1000d on Threadripper — IPv4 DHCP+ping">
**Commands:**
\```
<exact commands run, with exit codes>
\```
**Results:** <PASS/FAIL/PARTIAL per test case>
**Regressions:** <newly discovered issues, with file:line>
**Fixes:** <fixes applied, with commit hash>
**Updated:** <links to entries updated in HARDWARE-VALIDATION-MATRIX.md>
```
## Runs
*(none yet — first run is the open task for the operator)*
## Cross-References to Other Validation Artifacts
- [FIREWALL-VALIDATION-LOG.md](./FIREWALL-VALIDATION-LOG.md) — netfilter rule validation (specific
to the `netfilter:` scheme, six scenario design documented in §Scenario AF).
- [USB-VALIDATION-RUNBOOK.md](./USB-VALIDATION-RUNBOOK.md) — USB controller validation matrix and
QEMU scripts.
- [HARDWARE-VALIDATION-MATRIX.md](./HARDWARE-VALIDATION-MATRIX.md) — cross-component validation
status (this log updates it).
- [HARDWARE-NETWORKING-INVENTORY.md](./HARDWARE-NETWORKING-INVENTORY.md) — hardware gate for
this log (records what can be tested).
## Open Tasks (as of 2026-07-27)
- **T-N1:** Acquire USB-C Ethernet dongle (~$15) for LG Gram bare-metal networking.
- **T-N2:** Collect Threadripper NIC inventory (`lspci -nn | grep -i ethernet`).
- **T-N3:** Acquire USB Bluetooth adapter (~$10) for LG Gram bare-metal Bluetooth.
- **T-N4:** First bare-metal networking run on Threadripper + onboard NIC.
These are the same tasks tracked in §15.4 of the [code audit](../docs/NETWORKING-AND-DRIVERS-CODE-ASSESSMENT-2026-07-27.md).