Files
ssmithxandClaude Opus 5.5 0e113e7c96 WAN on eth0 (DHCP), WiFi client becomes wwan; br-lan portless
Lab topology change for the WiFi AP: the onboard Ethernet port is the
WAN (netifd dhcp, metric 10), served by archy-dev-pa's NetworkManager
shared connection (Pi at 10.42.0.2); the WiFi client uplink stays as
wwan (metric 20) in the wan zone; br-lan keeps 192.168.10.1 with no
wired port (bridge_empty) until the AP joins it.  Seeds and rpi4.scm
updated; the live Pi was changed with uci over the WiFi path first.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 14:35:49 -04:00

33 lines
1.0 KiB
Plaintext

# Seeded by Guix on first activation (uci-service-type); owned by UCI and
# netifd after that.
#
# wan: the onboard Ethernet port (GENET, eth0 as long as no USB NIC races
# it, PITFALLS #26), DHCP from the upstream (in the lab, archy-dev-pa's
# shared connection). br-lan has no wired port: the WiFi AP joins it
# (bridge_empty keeps it up meanwhile).
# wwan: WiFi client uplink, kept as a second WAN (higher metric): wlan0 is
# associated by wpa_supplicant (outside netifd) and attached to this
# interface over ubus (add_device, link-ext) by the netifd-attach-wlan0
# service: netifd won't take a WiFi netdev from `option device'.
config device
option name 'br-lan'
option type 'bridge'
option bridge_empty '1'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.10.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option device 'eth0'
option proto 'dhcp'
option metric '10'
config interface 'wwan'
option proto 'dhcp'
option metric '20'