Messages

Thank you for responding so quick!

Does that happen only when (one of) your Proxmox host restarts or also if you only restart the OpnSense VM?
And what do you mean with a "2 PC cluster"? Is that a Proxmox cluster?

Yes, when I would reboot the box that held opnsense, I would lose my WAN IP when it came back up.  I had to power cycle the modem to get a new WAN address.  Yes, I meant a 2 PC Proxmox cluster.  As you suggested, I separated my cluster so that I have two independent Proxmox machines again.  I basically reinstalled everything to make sure they were truly separate.

After reading through your response a couple of times, I believe that Proxmox is sending out the MAC address of the network port that is assigned as my WAN port even though it is not configured with an IP.  When OPNsense starts up, a new MAC address is broadcast so I am not given an IP until I power cycle the modem.  I did try to use the MAC address (I think it was the MAC address I grabbed) of the network adapter assigned in Proxmox.  When I added it to the WAN port config to spoof Proxmox, I was given an IP from my ISP, but I could not reach the internet.  I removed the spoofed MAC and I got an IP and could browse the web.

I need to do some more testing I suppose to figure out how to get this working.  :)

Hello all.  I have searched a ton of places looking for an answer to my problem, but I have not found anything that applies to my situation. I am hoping it is something easy that I just do not see.

I am running OPNsense 25.7.3_7-amd64 on Promox 9.0.9 (currently in a 2 PC cluster).  I am running it on a GMKTec Nucbox M5 Plus (Ryzen 7 5825U, 32GB Ram, 512GB SSD, 2 x 2.5GB LAN ports). I have the following plugins installed:  acme-client, caddy, ddclient, haproxy, ntopng, redis, smart, theme-rebellion.  I have configured all by haproxy and they all work as designed when the router is working.

The LAN port works fine and I can access both Proxmox and OPNsense on my network.

The problem I keep having is if Proxmox is shutdown or reboots, I do not get a WAN IP and cannot access the Internet.  The OPNsense dashboard shows the WAN interface without an IP and Gateways box on the dashboard shows the WAN_DHCP as undefined.  Rebooting OPNsense does not fix it, nor does reloading the WAN interface under Interfaces:Overview.

To fix it, I have to power cycle my fiber modem.  I then get a WAN IP address (which is different after each power cycle).  While researching this issue and leaving OPNsense running without its WAN address after the last reboot, I noticed that about 30 minutes later, I did get a WAN address without doing anything, but it was a new IP from my provider just as if I had power cycled the modem.  I have included the system.log from the last reboot and when the WAN IP resolved itself on its own.  In the system.log, there is a large number of TIMEOUT errors under dhclient-script for vtnet1 (WAN) causing it to fail on vtnet1 executing. Then OPNsense reports "/usr/local/etc/rc.newwanip: Failed to detect IP for interface wan".  This repeats a number of times.

While it is nice to be able to have other VMs on this machine, I am thinking about switching back to baremetal as it did not have this problem.  Regardless, I would like to at least understand why this is happening.  I don't know if it is something in Proxmox or OPNsense that I have wrong.  Maybe it will help someone else.  So, any expertise would be most welcome.

Here are the ports:

Proxmox Node:
enp1s0 (active/no autostart) --> vmbr0 (active/autostart) -->  192.168.1.1/24 (CIDR) -->  192.168.1.254 (Gateway)  -->  LAN
enp2s0 (active/no autostart) --> vmbr1 (active/autostart) -->  CIDR blank -->  Gateway blank  -->  WAN

Proxmox VM:
Network device (net0): virtio=BC::::D3, bridge=vmbr0, queues=4
Network device (net1): virtio=BC::::7C, bridge=vmbr1, queues=4


OPNSense:
LAN  -->  vtnet0  -->  192.168.1.254/24
WAN  -->  vtnet1  -->  69.xx.xxx.246/25  --> 69.xx.xxx.129 (Gateway)

Thanks.