Uploaded image for project: 'vpp'
  1. vpp
  2. VPP-1974

ping fails between AF_XDP VM interface and host

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • 21.01
    • af_xdp
    • None

      I'm trying to make a basic Virtual Box scenario. The purpose was to test AF_XDP interfaces from VPP basic scenario. Pinging does not work from the host interface to the AF_XDP interface made on top of a emulated e1000.

       

      vpp# ping 192.168.56.1
      Statistics: 5 sent, 0 received, 100% packet loss
      

      I tried tracing the AF_XDP interface:

      Also, I tried a tcpdump from the host:

      arcade@Arcade-PC ~ $ sudo tcpdump -i vboxnet0 -e
      tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
      listening on vboxnet0, link-type EN10MB (Ethernet), capture size 262144 bytes
      22:21:55.185306 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:55.185342 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:55.185359 0a:00:27:00:00:00 (oui Unknown) > 02:fe:95:99:a0:7c (oui Unknown), ethertype ARP (0x0806), length 42: Reply 192.168.56.1 is-at 0a:00:27:00:00:00 (oui Unknown), length 28
      22:21:56.185080 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:56.185090 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:56.185124 0a:00:27:00:00:00 (oui Unknown) > 02:fe:95:99:a0:7c (oui Unknown), ethertype ARP (0x0806), length 42: Reply 192.168.56.1 is-at 0a:00:27:00:00:00 (oui Unknown), length 28
      22:21:57.184746 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:57.184775 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:57.184808 0a:00:27:00:00:00 (oui Unknown) > 02:fe:95:99:a0:7c (oui Unknown), ethertype ARP (0x0806), length 42: Reply 192.168.56.1 is-at 0a:00:27:00:00:00 (oui Unknown), length 28
      22:21:58.184474 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:58.184482 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:58.184535 0a:00:27:00:00:00 (oui Unknown) > 02:fe:95:99:a0:7c (oui Unknown), ethertype ARP (0x0806), length 42: Reply 192.168.56.1 is-at 0a:00:27:00:00:00 (oui Unknown), length 28
      22:21:59.184257 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:59.184287 02:fe:95:99:a0:7c (oui Unknown) > Broadcast, ethertype ARP (0x0806), length 60: Request who-has 192.168.56.1 tell 192.168.56.101, length 46
      22:21:59.184301 0a:00:27:00:00:00 (oui Unknown) > 02:fe:95:99:a0:7c (oui Unknown), ethertype ARP (0x0806), length 42: Reply 192.168.56.1 is-at 0a:00:27:00:00:00 (oui Unknown), length 28
      22:22:03.137738 0a:00:27:00:00:00 (oui Unknown) > Broadcast, ethertype IPv4 (0x0800), length 86: 192.168.56.1.57621 > 192.168.56.255.57621: UDP, length 44

      Worth mentioning: If I do not use AF_XDP, and instead add the e1000 interface as a DPDK device, the ping has no problem in working.

       

            Unassigned Unassigned
            catalinv Catalin Vasile
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: