@pancakes there's incoming wireguard tunnels (those seem to work), and wireguard tunnels for outgoing traffic
it seems to break on the latter one, idk what exactly the setup is, but i assume for "outgoing", any connect attempts going to an IP will try to route via that tunnel, instead of directly
@ShadowJonathan@pancakes been a while since I did any wireguard config, but you should be able to specify what IPs/networks route via the tunnel and which don't. Is this routing under your control or someone else's?
@http_error_418@pancakes idk, its not my setup, its two instance admins who ive had poking me about federation issues, that were traced back to this thing
@ShadowJonathan@pancakes yeah routing through tunnels is a pain and it took me ages to get working reliably, not surprised at all if someone else is having trouble
@ShadowJonathan@pancakes will have to pass on discord, I hate that software with a flaming passion that burns hotter than a thousand suns. But I can find the documentation on wireguard routing config that I used.
Basically the main issue I encountered for outbound connections was defining the peer (client) device's address in its config file correctly. When I got it wrong I could see unencrypted packets on the wg virtual interface that never made it to being sent out encrypted on the main network interface, they were just dropped
☀️
@ShadowJonathan@tech.lgbt
