debian networking services. device priority. eth0>wlan

[i8igmac]

my understanding.

If eth0 is up and working, then you launch wpa_supplicant -iwlan0

Eth0 gateway ->192.168.0.1

Wlan0 gateway->10.0.0.1

You will notice eth0 is still the active connection. route -n will show the gatway is still 192.168.0.... I can change this with ip route gw add via 10.0.0.1.

so, what service or config is responsible for device priority? eth0>wlan0

[Lost In Cyberia]

my understanding.

If eth0 is up and working, then you launch wpa_supplicant -iwlan0

Eth0 gateway ->192.168.0.1

Wlan0 gateway->10.0.0.1

You will notice eth0 is still the active connection. route -n will show the gatway is still 192.168.0.... I can change this with ip route gw add via 10.0.0.1.

so, what service or config is responsible for device priority? eth0>wlan0

Most likely network-manager? Not 100% sure on your system.

Run :

sudo systemctl status networking.service  

and then run:

sudo systemctl status systemd-networkd.service

One of those should be active and the other should be dead. Whichever is actice is most likely handling your interfaces

Edited March 3, 2016 by Lost In Cyberia

[i8igmac]

I have 2 systems that share the same situation... (I'm sure all linux will do this)

Debian arm version 2016

network-manager was not present but I see networking service. It fails to stop when I run service stop (witch was frustrating)

I had hopes to find exactly what controls this priority scenario...

If eth0 is associated then Hold this gateway. what if eth0 does not provide internet? Its still the priority over any other device!

In my situation, eth0 is simply providing me remote access via ssh server...

(I wont be able to. Test your commands until I get home)