last fragment of the pkt is not fwded if intf mirror is configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Won't Fix
|
High
|
Divakar Dharanalakota | ||
R4.0 |
Won't Fix
|
High
|
Divakar Dharanalakota | ||
Trunk |
Won't Fix
|
High
|
Divakar Dharanalakota |
Bug Description
Last fragment of the pkt is not fwded if intf mirror is configured
When the VM sends fragmented pkts then the last fragment is not sent out by the vrouter. This happens only if interface mirroring is configured.
Intf mirror config:
virtual_
local_preference: null
interface_mirror: {
traffic_
mirror_to: {
analyzer_
nh_mode: dynamic
juniper_
udp_port: 8099
static_
analyzer_
analyzer_
nic_
}
}
}
Sent 5500 byte pkt from a VM with default (1500) MTU.
tcpdump on tap interface:
root@5b8s35:~# tcpdump -i tapff434d27-8e -n ip and greater 500 -v
tcpdump: WARNING: tapff434d27-8e: no IPv4 address assigned
tcpdump: listening on tapff434d27-8e, link-type EN10MB (Ethernet), capture size 65535 bytes
21:58:28.557091 IP (tos 0x0, ttl 64, id 53299, offset 0, flags [+], proto ICMP (1), length 1500)
112.12.1.3 > 112.12.1.4: ICMP echo request, id 28080, seq 1, length 1480
21:58:28.557145 IP (tos 0x0, ttl 64, id 53299, offset 1480, flags [+], proto ICMP (1), length 1500)
112.12.1.3 > 112.12.1.4: ip-proto-1
21:58:28.557158 IP (tos 0x0, ttl 64, id 53299, offset 2960, flags [+], proto ICMP (1), length 1500)
112.12.1.3 > 112.12.1.4: ip-proto-1
21:58:28.557170 IP (tos 0x0, ttl 64, id 53299, offset 4440, flags [none], proto ICMP (1), length 1088)
112.12.1.3 > 112.12.1.4: ip-proto-1
tcpdump on physical interface:
root@5b8s35:~# tcpdump -i p514p1 -n host 172.17.90.7 and udp -v
22:02:23.315496 IP (tos 0x0, ttl 64, id 53300, offset 0, flags [none], proto UDP (17), length 1486)
172.
IP (tos 0x0, ttl 64, id 53300, offset 0, flags [+], proto ICMP (1), length 1436)
112.12.1.3 > 112.12.1.4: ICMP echo request, id 28551, seq 1, length 1416
22:02:23.315503 IP (tos 0x0, ttl 64, id 53300, offset 0, flags [none], proto UDP (17), length 134)
172.
IP (tos 0x0, ttl 64, id 53300, offset 1416, flags [+], proto ICMP (1), length 84)
112.12.1.3 > 112.12.1.4: ip-proto-1
22:02:23.315511 IP (tos 0x0, ttl 64, id 53300, offset 0, flags [none], proto UDP (17), length 1486)
172.
IP (tos 0x0, ttl 64, id 53300, offset 1480, flags [+], proto ICMP (1), length 1436)
112.12.1.3 > 112.12.1.4: ip-proto-1
22:02:23.315517 IP (tos 0x0, ttl 64, id 53300, offset 0, flags [none], proto UDP (17), length 134)
172.
IP (tos 0x0, ttl 64, id 53300, offset 2896, flags [+], proto ICMP (1), length 84)
112.12.1.3 > 112.12.1.4: ip-proto-1
22:02:23.315522 IP (tos 0x0, ttl 64, id 53300, offset 0, flags [none], proto UDP (17), length 1486)
172.
IP (tos 0x0, ttl 64, id 53300, offset 2960, flags [+], proto ICMP (1), length 1436)
112.12.1.3 > 112.12.1.4: ip-proto-1
22:02:23.315524 IP (tos 0x0, ttl 64, id 53300, offset 0, flags [none], proto UDP (17), length 134)
172.
IP (tos 0x0, ttl 64, id 53300, offset 4376, flags [+], proto ICMP (1), length 84)
112.12.1.3 > 112.12.1.4: ip-proto-1
Changed in juniperopenstack: | |
status: | New → Won't Fix |
Looks like the issue is not a recent breakage. This was exposed now in the virtual overlay testbeds we have in Sanity. VM-VM traffic will get affected if we have mirroring and fragments. As customers did not hit this in previous releases I am moving it to get fixed in 4.0.2.0