After having been led astray by various (most) googled advices, it boiled down to the fact, that standard archlinux armv6 uses systemd-networkd as the service for network issues. (No netctl, no dhcpcd)
I can get WLAN up and running _only_ if eth0 is connected at boot. Thereafter I can set eth0 down and unplug it even, but the WLAN will not work if eth0 is unplugged to begin with. The AP shows it as connected though.
I would very much appreciate if anyone had a working suggestion to solve the riddle.
Files involved are
- /etc/systemd/network/wlan0.network
$this->bbcode_second_pass_code('', '[Match]
Name=wlan0
[Network]
#DHCP=both
DNS=192.168.178.1
Address=192.168.178.24/24
Gateway=192.168.178.1')
- /etc/wpa_supplicant/wlan0.conf
$this->bbcode_second_pass_code('', 'update_config=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="myap"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk="top-secret"
# wpa_ptk_rekey=600
}')
- /etc/systemd/system/wpa_supplicant.service
$this->bbcode_second_pass_code('', '[Unit]
Description=Wireless network connection wlan0
After=network.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/sbin/wpa_supplicant -i wlan0 -D wext -B -c/etc/wpa_supplicant/wlan0.conf
[Install]
WantedBy=multi-user.target')
As stated above, Raspberry Pi connects to the AP, but only if eth0 is present at boot. After boot I can SSH to Raspberry Pi, the set eth0 down and even disconnect the cable (in that order), but not with cable removed before booting or removing cable before setting eth0 down.