On 14 December 2017 at 22:44, Martin Pieuchot <[email protected]> wrote:
> > Here's a diff that should fix the problem, do you confirm? > > Index: net/if_vxlan.c > =================================================================== > RCS file: /cvs/src/sys/net/if_vxlan.c,v > > > <--snip--> Hi Martin, This patch stopped traffic flow being processed on the vxlan(4) interface. Data goes into it but doesn't exit via the tunnel, nor data coming from the remote end is handled by the adapter. I reverted the patch, re-compiled and the traffic returned to normal. Below is some traffic dumps including from the remote host that doesn't get processed. This was patched successfully against a cvs up from 17/12/2017 AEDT. Let me know if there is any further tests you need me to run. Thanks, Jason. q3# jobs [2] + Running tcpdump -ni vxlan1 [1] - Running tcpdump -ni vio0 q3# ping 10.2.2.2 PING 10.2.2.2 (10.2.2.2): 56 data bytes 16:07:52.781201 10.2.2.1 > 10.2.2.2: icmp: echo request 16:07:53.783079 10.2.2.1 > 10.2.2.2: icmp: echo request 16:07:54.777829 10.2.2.1 > 10.2.2.2: icmp: echo request 16:07:55.783351 10.2.2.1 > 10.2.2.2: icmp: echo request 16:07:56.777305 10.2.2.1 > 10.2.2.2: icmp: echo request ^C --- 10.2.2.2 ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss q3# ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2): 56 data bytes 64 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=1.824 ms 16:08:06.556414 192.168.1.1 > 192.168.1.2: icmp: echo request 16:08:06.558083 192.168.1.2 > 192.168.1.1: icmp: echo reply 64 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=6.884 ms 16:08:07.553165 192.168.1.1 > 192.168.1.2: icmp: echo request 16:08:07.559913 192.168.1.2 > 192.168.1.1: icmp: echo reply 64 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=6.011 ms ^C --- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 1.824/4.907/6.884/2.208 ms q3# 16:08:08.548219 192.168.1.1 > 192.168.1.2: icmp: echo request 16:08:08.554127 192.168.1.2 > 192.168.1.1: icmp: echo reply 16:08:36.077092 arp who-has 10.2.2.1 tell 10.2.2.2 16:08:36.077216 arp reply 10.2.2.1 is-at fe:e1:ba:d0:0d:7f 16:08:36.076746 192.168.1.2.4789 > 192.168.1.1.4789: udp 50 [tos 0x10] 16:08:37.077620 arp who-has 10.2.2.1 tell 10.2.2.2 16:08:37.077692 arp reply 10.2.2.1 is-at fe:e1:ba:d0:0d:7f 16:08:37.077410 192.168.1.2.4789 > 192.168.1.1.4789: udp 50 [tos 0x10] 16:08:38.074099 arp who-has 10.2.2.1 tell 10.2.2.2 16:08:38.074301 arp reply 10.2.2.1 is-at fe:e1:ba:d0:0d:7f 16:08:38.073318 192.168.1.2.4789 > 192.168.1.1.4789: udp 50 [tos 0x10] 16:08:39.056238 arp who-has 10.2.2.1 tell 10.2.2.2 16:08:39.056246 arp reply 10.2.2.1 is-at fe:e1:ba:d0:0d:7f 16:08:39.056207 192.168.1.2.4789 > 192.168.1.1.4789: udp 50 [tos 0x10]
