Did the upgrade process started all these daemons?
]]>The network handling for wlan0 was made by the wpa_supplicant
Please share the full configuration and also indicate which services were enabled (and how) to acheive this.
Now I saw that the wpa_supplicant was running on wlan0, but the dhclient was unable to give an ip.
It's always best to provide the full, verbatim command output rather than a vague description.
What is the best way to connect to the internet? Is it time to say good-bye to the wpa_supplicant? Or shall I deactivate network-manager and modem-manager and let still do wpa_supplicant the job?
There should be no problem using wpa_supplicant alone to associate with the access point. Disabling any other networking services that might conflict and configuring wpa_supplicant and dhclient correctly should work.
]]>The network handling for wlan0 was made by the wpa_supplicant, also perfect and stable. Now I saw that the wpa_supplicant was running on wlan0, but the dhclient was unable to give an ip.
Then I saw that further daemons were :
- avahi-daemon, which created an own interface wlan0:avahi with a fall-back ip adress from a wrong range.
-network-manager
-modem-manager
I never ever had configured this daemons to run and to handle my wlan interface - but they did. However none of the programs were able to fire up wlan0 and connect to my dhcp server. OK, to many cooks probably.
All this only happened on the old eee701 Asus machine, other computer with wlan interface are still running fine with wpa_supplicant.
What is the best way to connect to the internet? Is it time to say good-bye to the wpa_supplicant? Or shall I deactivate network-manager and modem-manager and let still do wpa_supplicant the job?
Hints are highly appreciated.
Regards
Berni