I’m having some difficulty with #wireguard. It runs and indicates that it is adding routes. But ip a doesn’t show these routes, and traffic doesn’t seem to flow through the tunnel.
@kidney@bioinfochat It turns out that this particular peer was not working properly. I switched to another and that worked.
I was using ip route to try and debug this (the output is included in the link). However, in my ignorance about routing tables, by diagnosis wasn’t getting me anywhere.
Thanks for the link, now everything makes a lot more sense.
Add comment