ip: Fragmentation fixes 08/23108/4
authorNeale Ranns <nranns@cisco.com>
Wed, 30 Oct 2019 17:34:14 +0000 (17:34 +0000)
committerOle Trøan <otroan@employees.org>
Tue, 5 Nov 2019 15:34:00 +0000 (15:34 +0000)
commit0b6a857d85df97e887de7aaf00fd6bd2dae39bf8
tree9494d7544d7af1fb5381bfb0aea51f731a661afd
parent3ea17d54a9a00c81bc672a7be1d48b765ac87ed2
ip: Fragmentation fixes

Type: fix

if the packet is about to be fragmented, then don't call any of the
actions that expect the rewrite to have been written.
1) don't double count packets thru the adjacency (original & fragments)
2) don't double decrement the TTL for fragments
3) return to ip4-midchain post ip-frag if that's where we started.
4) only run midchain/mcast fixups if not fragmenting (if no errors)

Change-Id: Ib2866787a42713ee5871b87b597d8f74b901044b
Signed-off-by: Neale Ranns <nranns@cisco.com>
src/vnet/interface_output.h
src/vnet/ip/ip4_forward.c
src/vnet/ip/ip6_forward.c
src/vnet/ip/ip_frag.c
src/vnet/ip/ip_frag.h
src/vnet/ip/lookup.c
test/test_ip4.py
test/test_ipip.py
test/test_mtu.py
test/vpp_neighbor.py