You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried to use netctl for failover bonding as described in the archlinux wiki for netctl.
wlan with wpa with netctl works fine
eth0 with netctl works fine
wlan as primary slave and eth0 as secondary slave works fine (MAC address is the same "wlan HW address" for bond0, wlan0 and eth0)
but wlan0 as secondary slave for failover purposes doesn't work!
symptoms seen with ifconfig -a and in syslog:
bond0 and eth0 have the same "eth0-HW address" as MAC address
wlan0 keeps its own HW-address as MAC address, it doesn't switch to the eth0-address!
connection to wireless network refused with wrong key.
The network key remains unaltered and is definitly correct, but maybe wpa_supplicant authentification process requires not only the key also the MAC address, which seems to be messed up in this case?
In both cases 3) and 4) I get the syslog-message
systemd-udevd[328]: Could not generate persistent MAC address for bond0: No such file or directory
BR
Hans-Peter
The text was updated successfully, but these errors were encountered:
I've tried to use netctl for failover bonding as described in the archlinux wiki for netctl.
wlan with wpa with netctl works fine
eth0 with netctl works fine
wlan as primary slave and eth0 as secondary slave works fine (MAC address is the same "wlan HW address" for bond0, wlan0 and eth0)
but wlan0 as secondary slave for failover purposes doesn't work!
symptoms seen with ifconfig -a and in syslog:
The network key remains unaltered and is definitly correct, but maybe wpa_supplicant authentification process requires not only the key also the MAC address, which seems to be messed up in this case?
In both cases 3) and 4) I get the syslog-message
systemd-udevd[328]: Could not generate persistent MAC address for bond0: No such file or directory
BR
Hans-Peter
The text was updated successfully, but these errors were encountered: