ip route get 8.8.8.8 ip route get 7.7.7.7 will show the routes for those ip addresses. you can check several to see where they go (in case the 2 default routes have the same metric) On 11 November 2015 at 14:38, Andrew Von Stein <16vonsa@xxxxxxxxx> wrote: > Expanding on the ip route command, you can you see what interface is used > to reach the Internet by looking at the default route. The entry that has > the destination as 0.0.0.0 and the subnet mask as 0.0.0.0 is the default > route. If your LAN is shown above your wifi interface I'm going to assume > that the default route is set to the LAN, but this leaves you with > definitive proof that it's working how you want it. Also, you'll want to > type "ip route -n" so you don't resolve hostnames. > > Also, if your wireless and LAN networks use a different gateway, you can > run a traceroute to an outside address to see what path the packets are > taking. Since it only shows the next hop IP address it doesn't work if your > networks use the same IP addressing scheme. > > Regards, > Andrew > > On Wed, Nov 11, 2015, 5:22 AM Bennett Piater <bennett@xxxxxxxxxxx> wrote: > >> > I don't use netctl, but you can usually see what default route it uses >> with >> > >> > ip route >> >> Thanks for that, I didn't know that command. >> The LAN is shown above WIFI, which (I assume) means that it takes >> precedence. >> >> > >> > I have made the experience that newly configured interfaces "steal" the >> > default route (although this can usually be configured - again, I don't >> > use netctl). >> > >> > I can imagine the default route passing through the WiFi interface in >> > your scenario. >> >> If I plug in LAN while having an active WIFI connection, it seems to >> steal the route. I checked it by monitoring steam download speeds. >> >> Thanks! >> >> Cheers, >> Bennett >> >> -- >> GPG fingerprint: 871F 1047 7DB3 DDED 5FC4 47B2 26C7 E577 EF96 7808 >> >> -- damjan
