Post #2741388

2026-03-15 08:42 UTC

@arichtman@eigenmagic.net @hugo@social.treehouse.systems Every node needs: a wg interface, with a pub/prv keypair, listening on an addr/porta list of peers, and their pubkeys, and allowed addresses. Peerings need to be symmetrical, yes - both nodes need to know about the other (by pubkey) and will only route/accept the listed addresses they know. At least one node needs a peer address for the other that is reachable to get things started. Reachable may include allowing the udp traffic in the firewall, unless config sugar does that for you.

Replies (2)

@arichtman@eigenmagic.net 2026-03-15 08:46

@uep@timeloop.cafe @hugo@social.treehouse.systems so it should have been working with one connection established :notsureif: I'll have to dig about more next week. I'm beat for today

Open ##2741391
@uep@timeloop.cafe 2026-03-15 08:49

@arichtman@eigenmagic.net @hugo@social.treehouse.systems that latter bit is the only thing that really makes any difference for client vs server.. wg will send traffic to initiate a connection when both of these are true: there's a peer address to trythere's traffic trying to use the tunnel, either from real processes or the internal "persistent keepalive" timer That initiation is the closest thing there is to being a "client", otherwise it just stays silent and no connection is negotiated. But of course a lot of helpful product gooeys try to make it seem like there must be c/s.

Open ##2741392