Ethernet Bonding Configuration
Receive traffic from connections created by the server is also balanced. When the local system sends an ARP Request the bonding software copies and saves the peer’s IP information from the ARP packet. When the ARP Reply arrives from the peer, its hardware address is retrieved and the bonding driver initiates an ARP reply to this peer assigning it to one of the slaves in the bond.Different behavior is exhibited in this mode of operation whether the Ethernet ports are bridged or routed with the WiFi interface. Specifically, if the Ethernet ports are bridged the load balancing is enforced on the TX side because the traffic flow is identified based on the destination IP address. The figure below describes the scenario where the Base Station is bridged. Traffic flowing from the Base Station to the CPEs will NOT be load balanced.
Different behavior is exhibited when the Ethernet is operating in routing mode, i.e. the WiFi is on a separate IP subnet, as depicted below.
This mode will balance the traffic such that packets destined for specific peers will always be sent over the same interface. Peers are identified by a traffic flow by hashing the tuple <IP-SRC, IP-DST, PORT-SRC, PORT-DST>. Therefore, the same pair of IP addresses can actually be allocated on separate ports depending on the specific traffic flow.With this mode of operation, the switch ports need to be configured for “etherchannel” or “trunking, which is a very common feature supported by the majority of the switches.
In this mode of operation, there is no limitation whether the Ethernet are bridged or routed with the WiFi interface.
IEEE 802.3ad (LACP)
The IEEE 802.3ad mode is a standard aggregation mode and requires that the switch have the appropriate ports configured as an 802.3ad aggregation. The precise method used to configure this varies from switch to switch, but, for example, a Cisco 3550 series switch requires that the appropriate ports first be grouped together in a single etherchannel instance, then that etherchannel is set to mode “lacp” to enable IEEE 802.3ad (instead of standard EtherChannel). Below is reported an example configuration for a Cisco 3550 switch.
interface Port-channel5 switchport access vlan 666 switchport mode access storm-control broadcast level 20.00 storm-control action shutdown ! interface FastEthernet0/7 switchport access vlan 666 switchport mode access power inline never storm-control broadcast level 20.00 storm-control action shutdown channel-protocol lacp channel-group 5 mode active spanning-tree portfast ! interface FastEthernet0/8 switchport access vlan 666 switchport mode access power inline never storm-control broadcast level 20.00 storm-control action shutdown channel-protocol lacp channel-group 5 mode active spanning-tree portfast