fix(netbird): apply the router's declared settings on every start #189

Merged
morten-olsen merged 1 commit from fix/homeit-499-netbird-router-apply-config into main 2026-10-30 11:18:42 +01:00
Owner

HOMEIT-499. After #188 the router's stored config still had NATExternalIPs null: on start the daemon auto-connected from its saved config, and the entrypoint's netbird up returned 'Already connected' (up.go:340), so NB_EXTERNAL_IP_MAP was never applied. Setting NB_DISABLE_AUTO_CONNECT=true makes up apply the declared environment on every start. Because that setting itself only lands through up, it needs one netbird down && netbird up in the pod after rollout, which is documented in docs/netbird.md. The desktop route covers both interruptions.

HOMEIT-499. After #188 the router's stored config still had NATExternalIPs null: on start the daemon auto-connected from its saved config, and the entrypoint's `netbird up` returned 'Already connected' (up.go:340), so NB_EXTERNAL_IP_MAP was never applied. Setting NB_DISABLE_AUTO_CONNECT=true makes `up` apply the declared environment on every start. Because that setting itself only lands through `up`, it needs one `netbird down && netbird up` in the pod after rollout, which is documented in docs/netbird.md. The desktop route covers both interruptions.
fix(netbird): apply the router's declared settings on every start
All checks were successful
ci/woodpecker/pr/charts Pipeline was successful
ci/woodpecker/push/scan Pipeline was successful
ci/woodpecker/manual/scan Pipeline was successful
ci/woodpecker/manual/charts Pipeline was successful
ci/woodpecker/manual/renovate Pipeline was successful
ci/woodpecker/cron/renovate Pipeline was successful
e327393d53
The daemon reconnected from the stored config before the entrypoint's
netbird up ran, so up reported 'Already connected' and never applied
NB_EXTERNAL_IP_MAP. Disable auto-connect so up applies the environment on
each start.

Refs HOMEIT-499
Sign in to join this conversation.
No description provided.