Show Posts
1
23.7 Legacy Series / Interface Issue
« on: August 26, 2023, 01:03:02 pm »
Hi,
I am quite new to OpnSense so please go gently.
Here is some background on the problem I am facing.
For a number of days now, I have been struggling to get an interface on Opnsense to act as a gateway on a proxmox host.
I have 3 Linux Bridges passed from ProxMox. vmbr0 is bound to a physical port and acts as the link to another router, vmbr1 acts as the LAN and I have some VM's working with full internet access.
vmbr3 I want to use as an interface so the proxmox host can utilise the guest VM with Opnsense on as a gateway (I intend to replace my existing router with this new physical host but for the purposes of testing and setting up I need web access for my existing devices)
I am having so many issues with vmbr3. I have assigned a static ip outside of the range of my existing DHCP on my current subnet, and specified a unique gateway ip on another subnet that I have configured in OpnSense.
When I first setup the interface, enable it and assign an IP, if I ping from my host, I can see entries in the firewall log populating in the default/deny rule for the source IP on my current subnet. Adding in the appropriate firewall rules, enables me to access the internet from the host through that interface.
All works well until I reboot the OpnSense VM, once it has fully booted I can no longer get access to the internet through the bridge.
However, I have noticed that as the VM is booting, I can run a trace route and it works as expected, but once boot is fully complete, the traceroute cuts out. (For Info, When the VM is powered down I can't reach the net as would be expected if I am using it as a gateway)
I can see the correct gateway IP is assigned to the interface in OpnSense after boot, but it just does not look like any traffic hits it, and there are no hits in the FW log, and I can't see any tell tale signs in other logs either
If I remove the interface reboot the VM, and set it up again it works until the next reboot of the VM.
Are there any pointers someone can give me in tracing why the interface effectively stops working as expected despite being shown as available?
Thanks in advance
I am quite new to OpnSense so please go gently.
Here is some background on the problem I am facing.
For a number of days now, I have been struggling to get an interface on Opnsense to act as a gateway on a proxmox host.
I have 3 Linux Bridges passed from ProxMox. vmbr0 is bound to a physical port and acts as the link to another router, vmbr1 acts as the LAN and I have some VM's working with full internet access.
vmbr3 I want to use as an interface so the proxmox host can utilise the guest VM with Opnsense on as a gateway (I intend to replace my existing router with this new physical host but for the purposes of testing and setting up I need web access for my existing devices)
I am having so many issues with vmbr3. I have assigned a static ip outside of the range of my existing DHCP on my current subnet, and specified a unique gateway ip on another subnet that I have configured in OpnSense.
When I first setup the interface, enable it and assign an IP, if I ping from my host, I can see entries in the firewall log populating in the default/deny rule for the source IP on my current subnet. Adding in the appropriate firewall rules, enables me to access the internet from the host through that interface.
All works well until I reboot the OpnSense VM, once it has fully booted I can no longer get access to the internet through the bridge.
However, I have noticed that as the VM is booting, I can run a trace route and it works as expected, but once boot is fully complete, the traceroute cuts out. (For Info, When the VM is powered down I can't reach the net as would be expected if I am using it as a gateway)
I can see the correct gateway IP is assigned to the interface in OpnSense after boot, but it just does not look like any traffic hits it, and there are no hits in the FW log, and I can't see any tell tale signs in other logs either
If I remove the interface reboot the VM, and set it up again it works until the next reboot of the VM.
Are there any pointers someone can give me in tracing why the interface effectively stops working as expected despite being shown as available?
Thanks in advance