| 2018-11-20 17:36:13 |
Arkadiusz Kudan |
description |
Sometimes, the tunneling test "ICMP - sending big buffer succeeds" fails apart of tunneling protocol.
It happens when we send a ping with payload size equal or higher than 1473. In this scenario, container slices the packet into two fragments (container has default 1500 mtu) and sends it to the network interface. vRouter extension captures the fragments and adds tunneling headers. However, the first fragment is too big (physical interface's mtu is also 1500) so it also needs to be fragmented. At the egress of physical interface we should see 3 fragments.
This could indicate a bug in implementation of fragmentation in vRouter extension. |
Sometimes, the tunneling test "ICMP - sending big buffer succeeds" fails apart of tunneling protocol.
It happens when we send a ping with payload size equal or higher than 1473. In this scenario, container slices the packet into two fragments (container has default 1500 mtu) and sends it to the network interface. vRouter extension captures the fragments and adds tunneling headers. However, the first fragment is too big (physical interface's mtu is also 1500) so it also needs to be fragmented. At the egress of physical interface we should see 3 fragments.
This could indicate a bug in implementation of fragmentation in vRouter extension.
Example of log output:
2018-10-01 15:33:01.176000 | [-] IP fragmentation - ICMP - Ping with big buffer succeeds 102.84s
2018-10-01 15:33:01.177000 | Expected {0}, but got {1}.
2018-10-01 15:33:01.177000 | 183: -BufferSize $BufferSize | Should Be 0
2018-10-01 15:33:01.177000 | at Invoke-LegacyAssertion, C:\Program Files\WindowsPowerShell\Modules\Pester\4.2.0\Functions\Assertions\Should.ps1: line 188
2018-10-01 15:33:01.177000 | at <ScriptBlock>, J:\Jenkins\workspace\WinContrail\****-server2016-devel\Test\Tests\Network\TunnellingWithAgent.Tests.ps1: line 178 |
|
| 2018-11-20 18:57:56 |
Arkadiusz Kudan |
description |
Sometimes, the tunneling test "ICMP - sending big buffer succeeds" fails apart of tunneling protocol.
It happens when we send a ping with payload size equal or higher than 1473. In this scenario, container slices the packet into two fragments (container has default 1500 mtu) and sends it to the network interface. vRouter extension captures the fragments and adds tunneling headers. However, the first fragment is too big (physical interface's mtu is also 1500) so it also needs to be fragmented. At the egress of physical interface we should see 3 fragments.
This could indicate a bug in implementation of fragmentation in vRouter extension.
Example of log output:
2018-10-01 15:33:01.176000 | [-] IP fragmentation - ICMP - Ping with big buffer succeeds 102.84s
2018-10-01 15:33:01.177000 | Expected {0}, but got {1}.
2018-10-01 15:33:01.177000 | 183: -BufferSize $BufferSize | Should Be 0
2018-10-01 15:33:01.177000 | at Invoke-LegacyAssertion, C:\Program Files\WindowsPowerShell\Modules\Pester\4.2.0\Functions\Assertions\Should.ps1: line 188
2018-10-01 15:33:01.177000 | at <ScriptBlock>, J:\Jenkins\workspace\WinContrail\****-server2016-devel\Test\Tests\Network\TunnellingWithAgent.Tests.ps1: line 178 |
Sometimes, the tunneling test "ICMP - sending big buffer succeeds" fails apart of tunneling protocol.
It happens when we send a ping with payload size equal or higher than 1473. In this scenario, container slices the packet into two fragments (container has default 1500 mtu) and sends it to the network interface. vRouter extension captures the fragments and adds tunneling headers. However, the first fragment is too big (physical interface's mtu is also 1500) so it also needs to be fragmented. At the egress of physical interface we should see 3 fragments.
This could indicate a bug in implementation of fragmentation in vRouter extension.
Last seen: 2018-11-07 http://logs.opencontrail.org/winci/a57a20c9ee5142aeb0e6d6b23b500836
Example of log output:
2018-11-07 10:08:32.251000 | Context Tunneling VXLAN
2018-11-07 10:09:28.415000 | [?] Uses specified tunneling method 57.48s
2018-11-07 10:09:28.415000 | Test not performed, because VXLAN doesn't report correctly in vrfstats
2018-11-07 10:09:28.415000 | at <ScriptBlock>, J:\Jenkins\workspace\WinContrail\****-server2016-devel\Test\Tests\Network\TunnellingWithAgent.Tests.ps1: line 115
2018-11-07 10:09:28.415000 | 115: Set-TestInconclusive "Test not performed, because VXLAN doesn't report correctly in vrfstats"
2018-11-07 10:10:36.042000 | [+] ICMP - Ping between containers on separate compute nodes succeeds 68.24s
2018-11-07 10:11:32.213000 | [+] TCP - HTTP connection between containers on separate compute nodes succeeds 60.07s
2018-11-07 10:12:53.577000 | [+] UDP - sending message between containers on separate compute nodes succeeds 75.01s
2018-11-07 10:14:01.197000 | [-] IP fragmentation - ICMP - Ping with big buffer succeeds 75.09s
2018-11-07 10:14:01.198000 | Expected {0}, but got {1}.
2018-11-07 10:14:01.198000 | 182: -BufferSize $BufferSize | Should Be 0
2018-11-07 10:14:01.198000 | at Invoke-LegacyAssertion, C:\Program Files\WindowsPowerShell\Modules\Pester\4.2.0\Functions\Assertions\Should.ps1: line 188
2018-11-07 10:14:01.198000 | at <ScriptBlock>, J:\Jenkins\workspace\WinContrail\****-server2016-devel\Test\Tests\Network\TunnellingWithAgent.Tests.ps1: line 177
2018-11-07 10:15:52.583000 | [+] IP fragmentation - UDP - sending big buffer succeeds 102.36s |
|
