You are not logged in.
I'm attempting to set up a round-robin bonding between the two ethernet ports on my box using bonding. Following https://wiki.archlinux.org/index.php/Netctl#Bonding and https://bbs.archlinux.org/viewtopic.php?id=203255, I have installed ifenslave and added this line to /etc/modprobe.d/bonding.conf:
options bonding mode=0 miimon=100
I've created a profile /etc/netctl/bond:
Description='Bond Interface'
Interface='bond0'
Connection=bond
BindsToInterfaces=('eno1' 'eno2')
IP=static
Address='192.168.1.100/24'
Gateway='192.168.1.1'
DNS='192.168.1.1'
I've also tried using the alternative names, but that didn't make any difference:
$ ip link
...
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 70:10:6f:3e:90:b4 brd ff:ff:ff:ff:ff:ff
altname enp3s0f0
3: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
link/ether de:03:3c:2a:d3:48 brd ff:ff:ff:ff:ff:ff permaddr 70:10:6f:3e:90:b5
altname enp3s0f1
...
When I issue netctl switch-to bond, it returns Profile 'bond' does not specify an interface, just like in https://bbs.archlinux.org/viewtopic.php?id=186313. When I use netctl start bond I fails after an expected
Error: Device can not be enslaved while up.
So it is trying to enslave the device eno1, which is the one being up. Indeed, after that I can do:
$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0
Slave Interface: eno2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 70:10:6f:3e:90:b5
Slave queue ID: 0
I cannot stop the existing network profile, because the machine only has VGA out and I have nothing to use that, so I can only reach it over network. That's why I hoped switch-to would allow me to retain the connection or at least re-log in.
Why can netctl not find the interfaces specified when using switch-to, yet doesn't seem to have any problem starting the profile?
Offline
Try creating a small script that stops the profile associated with eno1 (or all netctl profiles) and then starts the bond profile .
Last edited by Lone_Wolf (2020-06-01 13:59:16)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Try creating a small script that stops the profile associated with eno1 (or all netctl profiles) and then starts the bond profile .
But when the network connection is lost, I'm logged out and the script stops being executed, so the bond profile won't start, right?
Offline
I've also tried using the alternative names
Did you create this altname? I have a feeling the names are conflicting.
When I issue netctl switch-to bond, it returns Profile 'bond' does not specify an interface
A link to rename interfaces via udev.
Offline
Did you create this altname? I have a feeling the names are conflicting.
No, the altnames where there the first time I checked the interface names to put in the script. Confrontingly, I have no idea what created them. Also, they are not the same, so how do you mean they could be conflicting?
Offline
It was pure hunch but it was wrong.
Like Lone_Wolf said, it seems the old configuration needs to be stopped first and before the bond can be switched on but since you're logged in through the network, I don't have the answer.
Offline
Offline