WAN IP assigned even though wan never connected

Started by motoracer47, April 04, 2025, 09:37:18 PM

Previous topic - Next topic
April 04, 2025, 09:37:18 PM Last Edit: April 04, 2025, 09:50:53 PM by motoracer47
Hi,
I have been running opnsense in a vm on proxmox, it has been working great for almost a year. I am now trying to do the same thing in Qnap virtualization Station, and I am having some issues.

Qnap TVS-672X
3 physical NICs
1 10Gb==LAN
1 1gb==WAN  (service binding enabled to remove all NAS associated services from this NIC)
1 1gb--not in use

The main issue is that I am getting an IP address assigned to the WAN interface even though the wan interface is not physically connected to anything. The second issue is that the IP address that is getting assigned to the WAN is either in the same subnet as my lan address or is in fact exactly the same as my lan address. (changes on rebooting the VM)
I have made quadruply sure they are not sharing an both a physical, or virtual interface.
Both interfaces connect to separate virtual switches that Qnap does not assign IP addresses to, and both virtual switches are connected to separate physical NICs. Even if I wait 20 minutes for ARP cache to clear, the problem persists. Needless to say, I cannot receive an IP from the cable modem.
I cant figure out what is assigning the IP address to this NIC, as only the cable modem should be able to, and it's not plugged in.
I'm not really sure why this is happening. Any thoughts?

So on the QNAP side, there's an equivalent to vmbr0 with static IP QIP and 10NIC as slave.
Also vmbr1 with 1NIC as slave.

From the VM's perspective, vtnet0 & 1 mapping to the corresponding vmbr0 & 1?

Did you get to the point of doing interface assignment during OPN setup?
Any chances some of the mappings are wrong? eg vtnet0 to vmbr1?