problem with bonding/netctl for wireless failover

Ask questions about Arch Linux ARM. Please search before making a new topic.

problem with bonding/netctl for wireless failover

Postby hp4 » Wed Jun 22, 2016 5:09 pm

Hi,
I've tried to configure the "Wired to wireless failover" as has been described in

https://wiki.archlinux.org/index.php/ne ... s_failover

but it doesn't work on my RaspberryPI.

Unplugging the wired connection doesn't lead to failover, the bonding driver reports loss of last active connection.

ifconfig -a shows that both slaves are up while cat /proc/net/bonding/bond0 reports at least "MII Status down" for the WLAN

After taking wlan0 out of the bonding configuration it can be activated with netctl without problems, so the wireless-access is configured correctly.

Any idea what's going wrong or how it's possible to trace/debug the reason for the failing failover?

BR
HP

----------------------------------------------------------------------------------------
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500
inet 192.168.85.17 netmask 255.255.255.0 broadcast 192.168.85.255
ether 80:1f:02:d3:20:c7 txqueuelen 1000 (Ethernet)
RX packets 2382 bytes 468412 (457.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2925 bytes 995993 (972.6 KiB)
TX errors 0 dropped 3 overruns 0 carrier 0 collisions 0

eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500
ether 80:1f:02:d3:20:c7 txqueuelen 1000 (Ethernet)
RX packets 2382 bytes 468412 (457.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2925 bytes 995993 (972.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=6147<UP,BROADCAST,SLAVE,MULTICAST> mtu 1500
ether 80:1f:02:d3:20:c7 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
----------------------------------------------------------------------------------------
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: wlan0 (primary_reselect always)
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 500
Down Delay (ms): 500

Slave Interface: eth0
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: b8:27:eb:4d:5a:73
Slave queue ID: 0

Slave Interface: wlan0
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: 80:1f:02:d3:20:c7
Slave queue ID: 0
hp4
 
Posts: 45
Joined: Thu May 30, 2013 12:09 pm

Re: problem with bonding/netctl for wireless failover

Postby cmsigler » Wed Jun 22, 2016 5:41 pm

Hi,

Just a tip for the forums. Please remember to enclose config file contents, output of commands, etc., in [ code ] [ /code ] display markup tags. You can use the "Code" button in your reply window. HTH.

Clemmitt
- Raspberry Pi 3
- Odroid-C2
- Raspberry Pi Zero
cmsigler
 
Posts: 37
Joined: Wed May 25, 2016 6:01 pm


Return to User Questions

Who is online

Users browsing this forum: No registered users and 21 guests