Skip to main content
Topic: Wifi then Ethernet -> no route (Read 4295 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

 

Re: Wifi then Ethernet -> no route

Reply #31
Code: [Select]
$ sudo iw dev wlp12s0 scan

BSS aa:11:bb:22:cc:33(on wlpxxxxxxx)
...
        SSID: my-ap-name
...
                 * primary channel: 4


BSS aa:11:bb:22:cc:34(on wlpxxxxxxx)
...
        SSID: my-ap-name
...
                 * primary channel: 44


wpa_supplicant.conf
...
#ssid=my-ap-name < this would connect to either aa:11:bb:22:cc:33 or aa:11:bb:22:cc:34
bssid=aa:11:bb:22:cc:33
...

In my case I have a dual band wireless router, by default it has 2 channels with the same ssid. WICD sees them in it's gui but wrote a wpa_supplicant.conf using the ssid. wpa_supplicant makes the wireless connection for any method, gui or cli. Similar problems seemed to happen in Network Manager but it might have more config options to fix it.
I returned to a basic manual config for now without any gui to try this out, and it's working OK with the bssid field, with both dhcpcd and dhclient. The higher channel is slower so you need to specify which one, if that's temporarily stronger at startup then the connection might go to that.
So that's what I meant by using the bssid.

Re: Wifi then Ethernet -> no route

Reply #32
Code: [Select]
$ sudo iw dev wlp12s0 scan

BSS aa:11:bb:22:cc:33(on wlpxxxxxxx)
...
        SSID: my-ap-name
...
                 * primary channel: 4


BSS aa:11:bb:22:cc:34(on wlpxxxxxxx)
...
        SSID: my-ap-name
...
                 * primary channel: 44


wpa_supplicant.conf
...
#ssid=my-ap-name < this would connect to either aa:11:bb:22:cc:33 or aa:11:bb:22:cc:34
bssid=aa:11:bb:22:cc:33
...

In my case I have a dual band wireless router, by default it has 2 channels with the same ssid. WICD sees them in it's gui but wrote a wpa_supplicant.conf using the ssid. wpa_supplicant makes the wireless connection for any method, gui or cli. Similar problems seemed to happen in Network Manager but it might have more config options to fix it.
I returned to a basic manual config for now without any gui to try this out, and it's working OK with the bssid field, with both dhcpcd and dhclient. The higher channel is slower so you need to specify which one, if that's temporarily stronger at startup then the connection might go to that.
So that's what I meant by using the bssid.



ESSID and said derivitive have nothing to do with ethernet

there also might be a udev issue with wifi

Re: Wifi then Ethernet -> no route

Reply #33
Oh yes, there's no ssid field in the  wpa_supplicant.conf man page ethernet example, even if wpa_supplicant was used to connect to ethernet, you're right, that's a different issue. Thank you for explaining it.

Re: Wifi then Ethernet -> no route

Reply #34
ethernet, if not hard coded, is brought up by udev when a connection is sensed.  I am actually not sure how this works because I ripped it out of my OS, but if the ethernet connection goes down, udev takes down the eth0 or whatever UUID name it has.  ANd it likwise brings it up and calls either dhcpcd or whatever.

http://www.tldp.org/HOWTO/Ethernet-HOWTO.html for backgroung

https://linuxconfig.org/tutorial-on-how-to-write-basic-udev-rules-in-linux

https://www.linuxquestions.org/questions/linux-networking-3/ethernet-auto-connect-auto-sense-doesn't-work-860604/

https://www.linuxjournal.com/content/fun-ethtool

https://www.linuxquestions.org/questions/linux-networking-3/ethernet-auto-connect-auto-sense-doesn't-work-860604/

aside from the gentoo and arch networking howtos
https://wiki.archlinux.org/index.php/Wake-on-LAN


Fix the ethernet FIRST.  Then work on the wifi