Fimeg/SouveraineOS
Watch
1
0
Fork
You've already forked SouveraineOS
 0
Code Releases Activity

task-49: wiuf/wiufph resolved — wiuf carried the laptop's tunnel address

Browse source 
wiuf was ipv4.addresses 10.8.0.5/24, which is wiufarch's; wiufph is 10.8.0.6,
the phone's. Not near-copies - bringing wiuf up would have put two devices on
one WireGuard address. wiufph also carried the dns-priority 10 fix; wiuf was
still at 0. Deleted, backed up to /root/nm-profile-backup/ on the device.

autoconnect=no left alone on purpose: it is why the tunnel does not return
after a reboot, and the switch is the user's authority per this task's own
constraints.
This commit is contained in:
Fimeg 2026-08-01 14:37:21 -04:00
commit 0737387379
1 changed files with 15 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/tasks/49-bearer-selection-as-device-state.md
View file

@ -322,10 +322,21 @@ sessiond owns is the WireGuard endpoint `/32`. The probe rides the existing
tunnel is off. This decides how traffic is carried, never whether the tunnel
exists.
Still to do, in order: set `home_ssids` on the device (`set_policy`), decide
which of `wiuf`/`wiufph` is authoritative and delete the other — the grid
cannot target "the VPN" while two profiles answer to the name — then work the
acceptance list. `dns=systemd-resolved` remains untouched and is what makes
**The duplicate profile is resolved.** `wiufph` is authoritative and `wiuf` is
deleted (backed up to `/root/nm-profile-backup/` on the phone). The two were
not near-copies — `wiuf` carried `ipv4.addresses 10.8.0.5/24`, which is the
*laptop's* tunnel address (`wiufarch`), while `wiufph` carries `10.8.0.6`, the
phone's. Bringing `wiuf` up would have put two devices on one WireGuard
address. `wiufph` also has the `dns-priority 10` correction from 2026-07-31;
`wiuf` was still at `0`.
**`wiufph` is `autoconnect=no`, and that is left alone deliberately.** It is
the real reason the tunnel does not return after a reboot, and flipping it is
the user's call, not this task's — the constraint above says the switch stays
the user's authority. Worth a decision, not a silent default.
Still to do, in order: set `home_ssids` on the device (`set_policy`), then work
the acceptance list. `dns=systemd-resolved` remains untouched and is what makes
`~wiuf.net` mean anything; nothing here addresses split DNS.
## Acceptance