A looped back NS message is detected during DAD
-
@kmo12345 So interestingly, I was playing around with SR-IOV and saw it was "Enabled" but not "Active" on my FreeBSD VM nor my pfSense VM. It was showing active on my Windows 2019 VM (after I had installed the correct supporting driver for support of the X520 Intel NIC) and Ubuntu LTS 18.04 VM. After examining it further and reading a bunch of posts in forums, I haven't had success in getting SR-IOV to be active, so I just disabled it. It seems the ix driver won't attach to the passed through PCI device for some reason. Anyway, when I did that on my FreeBSD 12 VM, the duplicate DAD issue came back after reboot. VMQ was left enabled. On the pfSense VM with the same configuration it wasn't showing the kernel warnings, but it seems SLAAC wasn't functioning with pfSense from my MacBook Pro. I honestly didn't verify this as I don't have a ton of time to mess with it at the moment. I just disabled VMQ and rebooted it again and all was happy.
So, I'm not totally sure of what to make of this, but it seems SR-IOV being enabled, even if it's not active, seems to fix the VMQ issue. It might be that SR-IOV effectively disables VMQ even though it's still selected in the VM configuration. I don't know where the issue lies and I'm not skilled enough in that area to really determine that, but I wanted to pass along my own personal findings for the community based on my own experiences. FreeBSD bug in hn driver maybe? Again, Linux and Windows seem fine in the same setup. I wanted to correct my earlier statement that the updated driver on Windows Server 2019 appeared to fix the problem with VMQ, as that doesn't appear to be the case now.
If I get time, I'd like to run disable SR-IOV on my other VM's and run Wireshark on Windows and tcpdump on my Linux VM just to verify that they also don't see the duplicate DAD issue and are just being silent about it. That would lead me to believe it's more of a Hyper-V and/or Intel driver problem on the host. If not, I'm back to supposing it's the hn driver in FreeBSD at fault with VMQ enabled.
-
@vabello It would be nice if the guide for installing pfsense on Hyper V included this issue.
I have run into it and trying basically everything in this thread and whatever sleuthing turns up to get these errors to go away.
I am working with Hyper V 2019 and the NICs (for now) are Intel X722 (10 Gbe) ones. I know the physical NICs have VMQ enabled (power shell command spit that out). The console messages though were for two virtual devices and it kept spamming (so I was unable to continue setup after initial install from iso).
If I figure anything out, I will share it.