vasilito
e6e030025d
The relibc commit (f7f27a91f3) accidentally included phantom deletions
of local/docs/networking-validation-log.md because the relibc
submodule's working tree had a stale reference to a file that
belonged only to the parent 0.3.1 branch. Restoring the file in
the parent.
The relibc commit itself only affects the relibc submodule pointer
in the parent. The MSG_NOSIGNAL fix lives in the relibc submodule
at its own branch (submodule/relibc), not in the parent 0.3.1
branch. The parent 0.3.1 only tracks the submodule pointer bump.
77 lines
3.2 KiB
Markdown
77 lines
3.2 KiB
Markdown
# 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 A–F).
|
||
- [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).
|