Post #2741385
2026-03-15 08:29 UTC
@uep@timeloop.cafe @hugo@social.treehouse.systems
After much tears I was able to get this working...sort of. Site A router (opnsense) has a client on site B router (openwrt) working. From site B I'm at least able to ssh into the OPNsense router, so I'm calling that good enough for now.
I've set up a wireguard server on site B openwrt, that looks fine. Generated a client for it and ...well there's no client option on opnsense. Instructions look like it's just another peer as Hugo pointed out, meshily.
There's no direct "import this client config" option so I rammed the settings into a peer config but no dice yet.
Before I go checking firewall settings and whether tethering impacted - I definitely need this parallel peering setup right? It seems like it could have worked both ways with one pair...
#OPNsense #Wireguard
Replies (1)
-
@uep@timeloop.cafe 2026-03-15 08:42
@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.