Hi dionisis,
dionisis wrote:edit: I hope I did the tcpdump you asked correctly.
while running the command you gave me I was downloading a file as i did on tests I described and this time, wan4 was not used.
I couldn't post all it here so I uploaded it to drobox,
https://www.dropbox.com/s/mkmpeazadsccx … p.txt?dl=0
Well, the tcpdump you uploaded was exactly the confirmation i was looking for. All your wans are used! So, i dont know what you are looking at and measuring, but all your wans are definitely used. 100% sure.
You can see for yourself in the dump towards 154.53.224.210:
wan = eth0.2 = 10.0.0.2:
17:05:12.049923 Out c4:6e:1f:6b:be:f1 (tos 0x0, ttl 127, id 24023, offset 0, flags [DF], proto TCP (6), length 48)
10.0.0.2.56615 > 154.53.224.210.80: tcp 0
17:05:12.150609 Out c4:6e:1f:6b:be:f1 (tos 0x0, ttl 127, id 24041, offset 0, flags [DF], proto TCP (6), length 48)
10.0.0.2.56617 > 154.53.224.210.80: tcp 0
wan2 = eth0.3 = 192.168.10.88:
17:05:12.250756 Out c4:6e:1f:6b:be:f1 (tos 0x0, ttl 127, id 24062, offset 0, flags [DF], proto TCP (6), length 48)
192.168.10.88.56619 > 154.53.224.210.80: tcp 0
17:06:14.612843 Out c4:6e:1f:6b:be:f1 (tos 0x0, ttl 127, id 3722, offset 0, flags [DF], proto TCP (6), length 48)
192.168.10.88.56666 > 154.53.224.210.80: tcp 0
wan3 = eth0.4 = 192.168.2.99:
17:06:14.307973 Out c4:6e:1f:6b:be:f1 (tos 0x0, ttl 127, id 3704, offset 0, flags [DF], proto TCP (6), length 48)
192.168.2.99.56663 > 154.53.224.210.80: tcp 0
17:06:14.514029 Out c4:6e:1f:6b:be:f1 (tos 0x0, ttl 127, id 3709, offset 0, flags [DF], proto TCP (6), length 48)
192.168.2.99.56664 > 154.53.224.210.80: tcp 0
wan4 = eth0.5 = 10.0.1.3:
17:05:11.830023 Out c4:6e:1f:6b:be:f1 (tos 0x0, ttl 127, id 24014, offset 0, flags [DF], proto TCP (6), length 48)
10.0.1.3.56613 > 154.53.224.210.80: tcp 0
17:05:12.001816 Out c4:6e:1f:6b:be:f1 (tos 0x0, ttl 127, id 24018, offset 0, flags [DF], proto TCP (6), length 48)
10.0.1.3.56614 > 154.53.224.210.80: tcp 0
Case closed
(Last edited by Adze on 15 Jan 2016, 14:53)