File: README

package info (click to toggle)
rear 2.6%2Bdfsg-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 5,844 kB
  • sloc: sh: 21,666; xml: 290; makefile: 286
file content (182 lines) | stat: -rw-r--r-- 4,296 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
                   +----------------------------------+
                   | Setup #2 (crazy networking)      |
                   +----------------------------------+


You need a VM with 11 network interfaces (eth0 being the main interface).
All interfaces except eth0 can be non-reachable.

kvm.xml is an example template of such VM.


eth0		IP 192.168.122.x/24 default 192.168.122.1 (x=177)
bond12		eth1 + eth2 mode=4 miimon=1000
vlan1bond12	bond12.1 IP 1.1.1.1 route 101.0.0.0/8
bond34		eth3 + eth4 mode=1 miimon=100
vlan2bond34	bond34.2
bridge2		bond34.2 IP 2.2.2.2 route 102.0.0.0/8
team567		eth5.5 + eth6 + eth7 IP 3.3.3.3 route 103.0.0.0/8
team89		eth8 + eth9
vlan3team89	team89.3
bridge3		eth10.3 + team89.3 IP 4.4.4.4 route 104.0.0.0/8

routes:
default via 192.168.122.1 dev eth0
101.0.0.0/8 via 1.1.1.254 dev bond12
102.0.0.0/8 via 2.2.2.254 dev bridge2
103.0.0.0/8 via 3.3.3.254 dev team567
104.0.0.0/8 via 4.4.4.254 dev bridge3


Running the unit tests:
----------------------

After copying the network configuration files and rebooting the system,

from the VM, run the following command:

# for i in $(seq 1 8); do ./tcase${i}.sh; done

This will record the generated network+route files.

Then to verify result, run the following command (this will take down the
network, except eth0):

# for i in $(seq 1 8); do ./verify.sh tcase${i}_results; done


-------------------------------------------------------------------------------


Test Case #1: standard
------------

Expected results:

team567 -> eth5.5
team89 -> eth8
101.0.0.0/8 via 1.1.1.254 dev bond12.1 
102.0.0.0/8 via 2.2.2.254 dev bridge2 
103.0.0.0/8 via 3.3.3.254 dev eth5.5
104.0.0.0/8 via 4.4.4.254 dev bridge3 


Test Case #2: simplification
------------

SIMPLIFY_BONDING=y SIMPLIFY_BRIDGE=y SIMPLIFY_TEAMING=y

Expected results:

bond12 -> bond12 (not simplified, because mode=4)
bond34 -> eth3
bridge2 -> eth3.2
team567 -> eth5.5
team89 -> team89 (not simplified, because runner=lacp)
bridge3 -> eth10.3


Test Case #3: standard with eth2, eth4, eth6, eth8, eth10 DOWN
------------

for eth in eth2 eth4 eth6 eth8 eth10; do ifdown $eth; done

Expected results:

eth2, eth4, eth6, eth8, eth10 not in file
team567 -> eth5.5
team89 -> eth9
101.0.0.0/8 via 1.1.1.254 dev bond12.1 
102.0.0.0/8 via 2.2.2.254 dev bridge2 
103.0.0.0/8 via 3.3.3.254 dev eth5.5
104.0.0.0/8 via 4.4.4.254 dev bridge3 


Test Case #4: simplification with eth2, eth4, eth6, eth8, eth10 DOWN
------------

for eth in eth2 eth4 eth6 eth8 eth10; do ifdown $eth; done

Expected results:

eth2, eth4, eth6, eth8, eth10 not in file
bond34 -> eth3
bridge2 -> eth3.2
team567 -> eth5.5
team89 -> eth9
bridge3 -> eth9.3
101.0.0.0/8 via 1.1.1.254 dev eth1.1 
102.0.0.0/8 via 2.2.2.254 dev eth3.2 
103.0.0.0/8 via 3.3.3.254 dev eth5.5
104.0.0.0/8 via 4.4.4.254 dev eth9.3 


Test Case #5: standard with eth1, eth3, eth5, eth7, eth9 DOWN
------------

for eth in eth1 eth3 eth5 eth7 eth9; do ifdown $eth; done

Expected results:

eth2, eth4, eth6, eth8, eth10 not in file
team567 -> eth6
team89 -> eth8
101.0.0.0/8 via 1.1.1.254 dev bond12.1 
102.0.0.0/8 via 2.2.2.254 dev bridge2 
103.0.0.0/8 via 3.3.3.254 dev eth6
104.0.0.0/8 via 4.4.4.254 dev bridge3 


Test Case #6: simplification with eth1, eth3, eth5, eth7, eth9 DOWN
------------

for eth in eth1 eth3 eth5 eth7 eth9; do ifdown $eth; done

Expected results:

eth2, eth4, eth6, eth8, eth10 not in file
bond34 -> eth4
team567 -> eth6
team89 -> eth8
bridge2 -> eth4.2
bridge3 -> eth10.3
101.0.0.0/8 via 1.1.1.254 dev eth2.1 
102.0.0.0/8 via 2.2.2.254 dev eth4.2 
103.0.0.0/8 via 3.3.3.254 dev eth6
104.0.0.0/8 via 4.4.4.254 dev eth10.3 


Test Case #7: IP address mapping
------------

# cat mappings/ip_addresses 
bond12.1	1.1.1.100/16
#bridge2	2.2.2.100/24
team567		3.3.3.100/16
bridge3		4.4.4.100/24

Expected results:

bond12.1 -> 1.1.1.100/16
bridge2 -> 2.2.2.1/24 (no mapping)
eth5.5 -> 3.3.3.100/16
bridge3 -> 4.4.4.100/24


Test Case #8: IP address mapping & simplification
------------

SIMPLIFY_BONDING=y SIMPLIFY_BRIDGE=y SIMPLIFY_TEAMING=y

# cat mappings/ip_addresses 
bond12.1	1.1.1.100/16
#bridge2	2.2.2.100/24
team567		3.3.3.100/16
bridge3		4.4.4.100/24

Expected results:

eth1.1 -> 1.1.1.100/16
eth3.2 -> 2.2.2.1/24 (no mapping)
eth5.5 -> 3.3.3.100/16
eth10.3 -> 4.4.4.100/24