wlan0 not brought up at boot, only at desktop login.

[Erwin Smout]

My home server is a laptop with a dead NIC; I just configure the wireless connection in /etc/network/interfaces. Looks like this -

auto wlp3s0
iface wlp3s0 inet dhcp
 wpa-ssid *ssid goes here*
 wpa-psk *passphrase goes here*

IIRC wicd and NM will both ignore a connection that's configured in /etc/network/interfaces.

Okay thanks I'll try and remember this in case I run into problems after all. What should it look like if I want static IP addresses for *both* ipv4 and ipv6 ? (I know about static address ... gateway ... and inet6 but where do I put the wpa clauses in that case, seeing as there appears to be no such thing as "end-static" ?)

(I've disabled NM altogether now and it doesn't seem to cause problems - if you are aware of any then advising me about them is welcomed.)

(Whether NM ignores these connection is at least also a function of NM's own Managed=true|false configuration setting.)

(Bonus question : the *passphrase goes here* would that be the passphrase in plaintext or the obfuscated thing we find in wpa_supplicant.conf ?)

[wizard10000]

My home server is a laptop with a dead NIC; I just configure the wireless connection in /etc/network/interfaces. Looks like this -

auto wlp3s0
iface wlp3s0 inet dhcp
	wpa-ssid *ssid goes here*
	wpa-psk *passphrase goes here*

IIRC wicd and NM will both ignore a connection that's configured in /etc/network/interfaces.

[GreyGeek]

It's somewhat old but may be of help:

https://help.ubuntu.com/community/Ne...WPA_supplicant

Note that using iwconfig, etc, is only for WEP, which you should not use


Sent from my iPhone using Tapatalk

[Erwin Smout]

OK Thanks.

(Any idea why this was changed from 14.04 ? With 14.04 I am absolutely positively 2000% certain that the link was up alive and kicking after power-on, because I used to use a laptop as a router and it worked without logging in.)

[GreyGeek]

It's not a bug.

If you are knowledgeable enough you can pick out the necessary steps from the following article:
https://www.linuxbabe.com/command-li...wpa-supplicant

Before systemd the process looked like this:
https://askubuntu.com/questions/2942...buntu-terminal
but "wlan0" isn't used any more for specific reasons.

A tool I used to use a long time ago was wicd-curses (and wicd-cli). If you plan to use it in a terminal without a desktop but plan to startx the KDE desktop later, as root or a user, you should take down the wifi connection first, so it won't interfere with NetworkManager.

[Erwin Smout]

May 28 13:07:51 FX6300 systemd[1]: Starting WPA supplicant...
May 28 13:07:51 FX6300 dbus[964]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
May 28 13:07:51 FX6300 wpa_supplicant[1073]: Successfully initialized wpa_supplicant
May 28 13:07:51 FX6300 systemd[1]: Started WPA supplicant.
May 28 13:07:51 FX6300 NetworkManager[981]: <info> [1495969671.5739] supplicant: wpa_supplicant running
May 28 13:07:51 FX6300 NetworkManager[981]: <info> [1495969671.5739] device (wlan0): supplicant interface state: init -> starting
May 28 13:07:51 FX6300 wpa_supplicant[1073]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
May 28 13:07:51 FX6300 wpa_supplicant[1073]: dbus: Failed to construct signal
May 28 13:07:51 FX6300 NetworkManager[981]: <info> [1495969671.6447] device (wlan0): supplicant interface state: starting -> ready
May 28 13:07:51 FX6300 NetworkManager[981]: <info> [1495969671.6447] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 28 13:07:51 FX6300 kernel: [ 23.857495] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Bug 1439771 seems to be about a similar problem (only over there it's after a wakeup, not after powerup.)

Do I have any chance there is a solution to this problem ? I want the wireless active at boot without having to login to the desktop.