Networking disparity between guest OS and XO

jcdick1

I have my router (OPNsense) running in a VM on XCP 8.2 and there seems to be a disparity between what XO is reporting from the guest utils and what the guest OS itself is saying.

In the guest OS, interface with MAC ending in 72:1e is my WAN interface, getting a DHCP address from my ISP. In XO, that interface is a static IP.

Here are two example interface assignments in the guest OS:

XO issue 1.png

Here is how each of those is configured:

XO issue 2.png

XO issue 3.png

Here is how XO is reporting them:

XO issue 4.png

That interface with the Jumbo Frames configured should be a 10.10.10.X address, per the OS config. That 192.168.5.X is on a completely different interface in the OS, and the MAC X:X:X:X:72:1e should be having the address currently shown on X:X:X:X:fd:93

Any suggestions? Because resolving networking issues when I can't get the information sources to align is problematic.

Thanks!

olivierlambert

Maybe a question for @fohdeesha

fohdeesha

@jcdick1 Hi, have you hot-added any new network interfaces to this VM by chance? I've noticed when doing this with *bsd based guests like the *sense projects, the order can get quite messed up, if you've added any new interfaces, changed any MAC addresses, etc, can you please shut the VM down entirely (not just issue a reboot) - once the power state of the VM is completely off, start it again.

Note that if you did hot-add interfaces and hadn't rebooted yet, the interface order will probably change into its "final" order (the ordering seems to be affected when hot adding interfaces, eg when I hot add interfaces into *bsd VMs, sometimes the new interface will show up as xn0 in the VM, so the existing xn0 will get moved to xn3 etc). I've avoided this by just no longer hot adding interfaces and doing it when the VM is off instead

jcdick1

@fohdeesha

I tried a full shutdown. I let it go full "red" before clicking the start icon. XO is still reporting very different MAC and IP assignments from what the guest OS has configured. Is it perhaps due to the tools that OPNsense packages?

fohdeesha

@jcdick1 I run opnsense on xcp-ng personally as well and use their packaged tools without issue, the only time I've gotten this behavior is when I hot-added interfaces and it changed the order of interfaces. If that's not it, I'm really not sure what would be causing this

One last thing you can try in case it's a weird cash issue is (inside XOA) go to settings > servers, click the green connected button next to your xcp-ng server to disconnect it from xoa - then wait a couple seconds and click it again to reconnect it