Hi,
On a CCR1009-8G-1S-1S+ running 6.34.2: I have recently discovered a significant amount of packet reordering when using EoIP with an ipsec secret. I believe packets are being distributed across the cores for crypto per packet (vs per flow) with UDP and ICMP and possibly TCP (unconfirmed). I believe this is what creates the packet reordering when there is a bursty flow.
Has anyone else run into this?
Is there any way to change the hashing to have these packets land on a single core to prevent the reordering?
This can be demonstrated by creating an EoIP connection between a clean path and then running a preloaded ping:
Code: Select all
# ping -l 10 192.168.55.2
PING 192.168.55.2 (192.168.55.2) 56(84) bytes of data.
64 bytes from 192.168.55.2: icmp_seq=4 ttl=64 time=23.9 ms
64 bytes from 192.168.55.2: icmp_seq=5 ttl=64 time=23.9 ms
64 bytes from 192.168.55.2: icmp_seq=7 ttl=64 time=23.9 ms
64 bytes from 192.168.55.2: icmp_seq=8 ttl=64 time=24.0 ms
64 bytes from 192.168.55.2: icmp_seq=3 ttl=64 time=24.0 ms
64 bytes from 192.168.55.2: icmp_seq=6 ttl=64 time=24.0 ms
64 bytes from 192.168.55.2: icmp_seq=1 ttl=64 time=24.0 ms
64 bytes from 192.168.55.2: icmp_seq=10 ttl=64 time=24.0 ms
64 bytes from 192.168.55.2: icmp_seq=2 ttl=64 time=24.0 ms
64 bytes from 192.168.55.2: icmp_seq=9 ttl=64 time=24.0 ms
--- 192.168.55.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 23.928/24.032/24.082/0.146 ms, pipe 10
Code: Select all
21:23:18.234793 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 2, length 64
21:23:18.234809 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 2, length 64
21:23:18.234834 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 4, length 64
21:23:18.234841 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 4, length 64
21:23:18.234845 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 6, length 64
21:23:18.234848 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 6, length 64
21:23:18.234858 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 5, length 64
21:23:18.234862 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 5, length 64
21:23:18.234865 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 7, length 64
21:23:18.234868 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 7, length 64
21:23:18.234870 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 8, length 64
21:23:18.234874 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 8, length 64
21:23:18.234888 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 3, length 64
21:23:18.234893 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 3, length 64
21:23:18.234895 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 1, length 64
21:23:18.234899 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 1, length 64
21:23:18.234902 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 10, length 64
21:23:18.234906 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 10, length 64
21:23:18.234908 IP 192.168.55.1 > 192.168.55.2: ICMP echo request, id 44608, seq 9, length 64
21:23:18.234912 IP 192.168.55.2 > 192.168.55.1: ICMP echo reply, id 44608, seq 9, length 64
