I have an Ubuntu Bionic machine with a wifi link; and I have set up a wireguard tunnel on it: # ifconfig lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 5502 bytes 545376 (545.3 KB) RX errors 0 dropped 0 overruns 0 […]
- Tags 30 hops max, 60 byte packets 1 10.0.0.1 (10.0.0.1) 68.393 ms 74.587 ms 74.328 ms^C But if use traceroute 8.8.8.8 -i wlan0 to force traceroute to use, as the routing table above should enforce, BROADCAST, but now I have reversed that to allow the peer to forward through this host. However, I have an Ubuntu Bionic machine with a wifi link; and I have set up a wireguard tunnel on it: # ifconfig lo: flags=73<UP, it always hangs. Traceroute shows that it's trying to route packets through the tunnel (the peer is currently configured to drop them): trac, it seems like my packets still want to route through the tunnel for some reason. Here's my routing table: # route -n Kernel IP routing tabl, LOOPBACK, MULTICAST> mtu 1500 inet 192.168.1.218 netmask 255.255.0.0 broadcast 192.168.255.255 ether dc:85:de:f3:3f:65 txqueuelen 1, NOARP> mtu 1420 inet 10.0.0.3 netmask 255.255.0.0 destination 10.0.0.3 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00, POINTOPOINT, RUNNING, RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1, then it works. What could be going on? Doesn't the routing table say that packets targeting 8.8.8.8 have to go out wlan0 to 192.168.1.1 for