[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| howtos:misc:network_interace_bonding [2018/03/08 17:58 (UTC)] – lamerix | howtos:misc:network_interace_bonding [2018/03/08 18:10 (UTC)] – adding balancing algorighm modes description lamerix | ||
|---|---|---|---|
| Line 51: | Line 51: | ||
| **mode 4 802.3ad** and **mode 5 balance-tlb** have some prerequisites. Check kernel docs for more information | **mode 4 802.3ad** and **mode 5 balance-tlb** have some prerequisites. Check kernel docs for more information | ||
| </ | </ | ||
| + | |||
| + | ====== Balancing algorithm modes ====== | ||
| + | |||
| + | **xmit_hash_policy** option sets the balancing algorithm used. | ||
| + | |||
| + | The default value is layer2. | ||
| + | |||
| + | |||
| + | * **layer2** Uses XOR of hardware MAC addresses to generate the hash. This algorithm will place all traffic to a particular network peer on the same slave. | ||
| + | * **layer2+3** Uses XOR of hardware MAC addresses and IP addresses to generate the hash. This algorithm will place all traffic to a particular network peer on the same slave. | ||
| + | * **layer3+4** This policy uses upper layer protocol information, | ||
| + | * **encap2+3** This policy uses the same formula as layer2+3 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. | ||
| + | * **encap3+4** This policy uses the same formula as layer3+4 but it relies on skb_flow_dissect to obtain the header fields which might result in the use of inner headers if an encapsulation protocol is used. | ||
| + | |||
| + | |||
| + | |||
| ====== Alternative methods ====== | ====== Alternative methods ====== | ||
