diff options
| author | Asbjørn Sloth Tønnesen <asbjorn@labitat.dk> | 2021-09-13 14:39:08 +0000 |
|---|---|---|
| committer | Asbjørn Sloth Tønnesen <asbjorn@labitat.dk> | 2021-09-13 15:10:49 +0000 |
| commit | a8fab3916c0ec8ec7307de636522f4de8849543b (patch) | |
| tree | 2e3705465ca2866d5977dd6c10c8da7f1e26ef48 /roles/space_server/files/network/10-lan11.network | |
| parent | 30aa929a02402ba58221cbc347fb1580dd79fd32 (diff) | |
| download | labitat-ansible-3x1g-bond.tar.gz labitat-ansible-3x1g-bond.tar.xz labitat-ansible-3x1g-bond.zip | |
space_server: bond all 3 gigabit ports, and enjoy 3x1G uplink3x1g-bond
Before:
- enp1s0: wan
- enp2s0: lan (with VLANs)
- enp3s0: mgt
Changes in this patch:
- wan is moved to VLAN id 5
- bond0 is created, replacing lan as lower device for VLANs
- mgt config is removed (could be reconfigured as a VLAN, and
made a available on a switch port)
- all 3 ports are enslaved in bond0
From the switch towards the space server load-balance algorithm
src-dst-ip* is used.
From the space server towards the switch L3+L4 is used.
Therefore a single IP pair will always use the same 1G
from the swith to the space server, a client therefore
needs to multiplex over multiple IPs in order to
*) The src-dst-ip algorithm on the switch hasn't been
tested with IPv6 yet. Hopefully we can find a better
switch at some point, so we can include the L4 ports in
the hashing on the switch.
Signed-off-by: Asbjørn Sloth Tønnesen <asbjorn@labitat.dk>
Diffstat (limited to 'roles/space_server/files/network/10-lan11.network')
0 files changed, 0 insertions, 0 deletions