Issue with IP Alias Addresses

Started by Combatsatellite, November 21, 2024, 07:53:42 PM

Previous topic - Next topic
Hello,

I'm experiencing an issue with the IP Alias addresses in my OPNsense setup.

Previously, everything was working fine. I had the standard 10.0.0.1/24 subnet configured on the LAN interface and used Virtual IPs to assign additional addresses to my Proxmox VMs and containers. However, a few days ago, this setup suddenly stopped working without any apparent changes on my end.

I'm unsure what might have caused the issue, and I'd really appreciate any help troubleshooting this. I'm happy to provide additional information if needed to debug the problem.

Thank you in advance!


Is your Proxmox server on auto-update? Version 8.3 is out now with changes to its network stack. I'm still going through the changes...

Quote from: mooh on November 25, 2024, 04:02:36 PM
Is your Proxmox server on auto-update? Version 8.3 is out now with changes to its network stack. I'm still going through the changes...

I am on 24.7.9, and there are no updates available.
Auto update is not enabled, i do updates manually.

@mooh was asking about the proxmox version.
24.7.9 is the OPNsense version  ;)

Quote from: EricPerl on November 25, 2024, 08:11:22 PM
@mooh was asking about the proxmox version.
24.7.9 is the OPNsense version  ;)

Thanks, i missed that..  ;D

8.2.8 is the Proxmox version, i will update now and come back after testing.

Okay, so i ran an update+upgrade on Proxmox, then rebooted and the issue still persists.

I think it might be related to my bridged ports issue possibly, but I am not sure yet.
Ill focus on the other issue and report back if it fixes this one too.

I just noticed something regarding my issue:

I have Mailrise running on my PVE with the IP 10.0.1.103, and i can no longer send notifications from my NAS (10.0.0.200), nor can i reach that IP from any LAN device thus the original issue but from my OPNsense i can which is on 10.0.0.1


(And I think i forgot to mention that the VMs with those IPs have internet acces and everything)

So, i found a fix:

instead of assigning the virtual IP to the LAN interface to LAN i assigned it to the NIC port that has the PVE connected to it.
Now it works as before, not sure if it is meant to be this way or not.., could be related to my bridged ports issue but for now the vIP issue is solved.