Hey Jesper,I apologize for not providing that information before. The driver is `virtio_net`. Unfortunately, I'm not sure what the NIC driver on the cluster is. Once my program's code is confirmed to be correct, I will try reaching out to our hosting provider to see if they can provide this information if the NIC's driver is the suspected cause to this issue.
``` root@SEAV21:~/AF_XDP-Test# ethtool -i ens3 driver: virtio_net version: 1.0.0 firmware-version: expansion-rom-version: bus-info: 0000:00:03.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no ``` Thank you! On 5/22/2020 10:51 AM, Jesper Dangaard Brouer wrote:
On Fri, 22 May 2020 10:22:10 -0500 Christian Deacon <gamemann@xxxxxxxxxxx> wrote:If I'm not doing anything wrong here, is it possible there's a bug with the NIC's driver? Unfortunately, I'm not sure which driver the cluster's NIC is using.Please run: ethtool -i ens3 And provide output. As it will tell you that NIC driver you are using.