* Re: routing table doesn't report wireguard routes
@ 2018-03-29 19:26 Lane Russell
0 siblings, 0 replies; 2+ messages in thread
From: Lane Russell @ 2018-03-29 19:26 UTC (permalink / raw)
To: wireguard
[-- Attachment #1: Type: text/plain, Size: 265 bytes --]
Turns out, I didn't understand quite how the routing table works in Linux.
Here is a good high-level description of how this works: (thanks to wurtel
over at stackexhange:
https://unix.stackexchange.com/questions/188584/which-order-is-the-route-table-analyzed-in
)
[-- Attachment #2: Type: text/html, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* routing table doesn't report wireguard routes
@ 2018-03-29 18:46 Lane Russell
0 siblings, 0 replies; 2+ messages in thread
From: Lane Russell @ 2018-03-29 18:46 UTC (permalink / raw)
To: wireguard
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
Ubuntu 16.04.4 LTS
Currently, WireGuard's routes don't seem to show up in the routing table,
at least as viewed via "route -n" and "netstat -rn".
Is this an issue, or am I misunderstanding the mechanism WireGuard uses to
route traffic?
In my case, the client config has "AllowedIPs = 0.0.0.0/0", and this is
working fine, it's just that the routes aren't visible.
[-- Attachment #2: Type: text/html, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-03-29 19:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-29 19:26 routing table doesn't report wireguard routes Lane Russell
-- strict thread matches above, loose matches on Subject: below --
2018-03-29 18:46 Lane Russell
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.