Skip to content

GB-122: a pinned port is one the edge host already holds

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-122 is printed by goatbuilder. The same text offline: goat explain GB-122 or goatbuilder explain GB-122.

What it means

A pinned WireGuard or carrier listen port is a UDP port the environment's edge hosts already hold (environments[].peering_edge_reserved_udp; absent, NetBird's WireGuard on 51820). A second listener there fails or steals its traffic.

Why it happens

  • values.wg_listen_port or values.carrier_listen_port is pinned to a reserved port
  • a peering running on the role default 51820, on edges with no mesh client, is being adopted

What to do

One line per step or alternative:

remove the pin and run goatbuilder federate allocate (it allocates odd ports from 51823 up and never takes a reserved port)
when the environment's edges run no mesh client: set peering_edge_reserved_udp: [] on that environment in goatbuilder.yaml

Read more

Exit code

goatbuilder exits with 2.