Needing to Flush the ARP Tables to get the IP working in a Proxmox VM

[FormBurden]

Been delving into Proxmox and the VM world making a lot of things more simple, for me at least. But what I've been running into is that whenever I restart a VM in Proxmox even using a static IP Address from within the IP settings of the VM (LXC Container specificly), which is mostly always a Debian 10 Container. From the console if I ping or use a simple command like "Apt update" to see if the internet is working, it doesn't. I'm running VLANs for these, and Proxmox itself is on a VLAN too (an Admin VLAN you could say) E.g. Admin is on 192.168.10.1/24 and typical application VLAN 192.1678.30.1/24. If that helps at all.

After doing pretty much every kind of setting I could think of in OPNsense that could possibly conflict with this when I restart a VM, I ended up finding that if I flush the ARP Tables, the Tables refresh, and then the VM's internet and even local traffic works correctly.

I made it so the VM MAC address doesn't auto change since it auto generates in a VM, I made it static. But even so, even the ARP table has the same MAC, still, it needs to be refreshed.

When the LAN/internet is down on the VM, the only person I 'can' ping, is the VLAN 192.168.30.1 (which is the main OPNsense VLAN) for example. Not sure if I could ping others on the sub net as well, but I don't have any other clients on that VLAN yet. But once the ARP is flushed I can ping other sub nets on my network (and yes, the firewall rules allow this, for now).

VLANs are set up correctly with the switch and router-bridge that are in between the server and OPNsense.

Here is the topology if it helps:  OPNsense > Mikrotik-Router Fiber Switch in Bridged mode > Mikrotik regular Switch > then VM Proxmox Server.

Anyone know what I could do to solve this?

[FormBurden]

Update:

Welp, I fixed my own issue. Oddly enough what was happening, was the VLAN IP network address on the Proxmox I was putting 192.168.30.1/24 without realizing that, just that was conflicting with the OPNsense VLAN 30 of 192.168.30.1/24. But when I changed the .1 to something like .5 or whatever, everything worked correctly when restarting a VM. I guess the mistake was accidentally trying to have two VLAN interfaces on the network instead of the one which is on OPNsense.

So for anyone with a similar issue, that's how I solved it.