LACP bond0 working but not used by system

On my test box I’ve configured bond0 to use eth1, eth2, eth3, and eth4 which all seems fine. I can see broadcast traffic on the bond0 interface but I cannot ping it or reach anything on it.

This is the configuration of bond0

DEVICE=bond0
Type=Bond
NAME=bond0
BONDING_MASTER=yes
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.0.14
PREFIX=24
GATEWAY=192.168.0.1
NM_CONTROLLED=no
BONDING_OPTS="mode=4 miimon=100 lacp_rate=1"
ZONE=trusted
DESCRIPTION="unset"

This is eth1. I’ve not included the others because they only differ by NAME, DEVICE, and UUID

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=eth1
UUID=e6f832db-45b2-46bb-b547-8481ea8c■■■■
DEVICE=eth1
ONBOOT=yes
MASTER=bond0
SLAVE=yes

This is the output of ifconfig note that eth0 is intended to be a management-only port.

bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500
        inet 192.168.0.14  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::290:27ff:■■■■:■■■■  prefixlen 64  scopeid 0x20<link>
        ether 00:90:27:f4:■■:■■ txqueuelen 1000  (Ethernet)
        RX packets 704406  bytes 417374585 (398.0 MiB)
        RX errors 0  dropped 2454  overruns 0  frame 0
        TX packets 32802  bytes 4179182 (3.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.13  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::290:27ff:■■■■:■■■■  prefixlen 64  scopeid 0x20<link>
        ether 00:90:27:f4:■■:■■ txqueuelen 1000  (Ethernet)
        RX packets 248314  bytes 47040406 (44.8 MiB)
        RX errors 0  dropped 14  overruns 0  frame 0
        TX packets 47022  bytes 33023762 (31.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xf7d00000-f7d20000

eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether 00:90:27:f4:■■:■■  txqueuelen 1000  (Ethernet)
        RX packets 186295  bytes 71902948 (68.5 MiB)
        RX errors 0  dropped 2372  overruns 0  frame 0
        TX packets 7012  bytes 894885 (873.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  memory 0xf7c00000-f7c20000

eth2: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether 00:90:27:f4:■■:■■  txqueuelen 1000  (Ethernet)
        RX packets 25527  bytes 4198175 (4.0 MiB)
        RX errors 0  dropped 12  overruns 0  frame 0
        TX packets 7762  bytes 993720 (970.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 18  memory 0xf7b00000-f7b20000

eth3: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether 00:90:27:f4:■■:■■  txqueuelen 1000  (Ethernet)
        RX packets 144159  bytes 45285194 (43.1 MiB)
        RX errors 0  dropped 63  overruns 0  frame 0
        TX packets 9094  bytes 1146779 (1.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 19  memory 0xf7a00000-f7a20000

eth4: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether 00:90:27:f4:■■:■■  txqueuelen 1000  (Ethernet)
        RX packets 348425  bytes 295988268 (282.2 MiB)
        RX errors 0  dropped 7  overruns 0  frame 0
        TX packets 8934  bytes 1143798 (1.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xf7900000-f7920000

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 108404  bytes 632944935 (603.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 108404  bytes 632944935 (603.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

After starting a ping -I bond0 192.168.0.100 this is the output of tcpdump -nn -n -i bond0 ‘dst 192.168.0.100 or src 192.168.0.100’

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bond0, link-type EN10MB (Ethernet), capture size 262144 bytes
13:19:04.062467 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28
13:19:05.064409 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28
13:19:06.066422 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28
13:19:08.062459 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28
13:19:09.064421 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28

A Wireshark trace on 192.168.0.100 shows the traffic is not reaching it. There’s no output from the tcpdump command when I try to ping 192.168.0.14 from 192.168.0.100. However, if I just do tcpdump -nn -n -i bond0 I can see ARP requests from other machines on the network so I know traffic is definitely reaching the interface.

PBXact saw the new interface and I have set it to the trusted zone but I can’t find a firewall log that might show what’s being blocked anyway.

So my question is, what am I missing to allow PBXact to use bond0?

EDIT: I rebooted PBXact and now bond0 is active but I can’t reach eth0. I’d like both interfaces to be available. I mainly want the LACP bond working for call traffic and the PBXact GUI so I have resilience on physical cables.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.