Topics

When doing port forward what's the difference between "destination" and "redirect target IP"?

Say I want to forward port 8080 to internal host 10.1.1.10, which of those fields do I put that, or do I put it in both?

Been fighting with this for a while now, I noticed there is a newer version so downloaded it hoping this would stop happening but it's still happening.  In order to not have to sit at my work bench and listen to the very loud switch, I temporary enabled the admin interface through the WAN port and have it plugged into my network, so I can sit at my regular PC to do all the configuring of vlans etc, then go to the work bench where I have a switch and laptop to test vlans.

After adding the 6th or so vlan, I will lose connectivity, and even rebooting, never get it back. I also can't connect to anything via the laptop/switch. The console shows all the interfaces with the right IPs, but can't ping anything. The only way to fix this is to completely reinstall, and start over from scratch.

Is there a way to stop this from happening?

I'm using it on a Sophos XG 115

I'm in the process of installing Opnsense on a Sohpos XG 115 and have it setup in a lab environment until I get all my vlans and rules working well enough that I can swap it into production.  Just to give a general idea of my environment, I have the firewall box setup so the WAN port is going to one of my vlans of my existing prod network, and the LAN port is setup as a trunk to a switch I'm using temporarily so I can plug a laptop into it and test the vlans etc, and do initial config. 

I originally accidentally installed the legacy 24.1 and when I performed the upgrade it trashed the whole install and I lost access to everything even from the laptop. I was able to get back in by creating a temporary admin interface on a 3rd port then found that all my vlans were not assigned anymore.  When I came to the forum that's when I realized I was on 24.1 when I checked my version to check what forum to post in and saw that 24.1 was considered legacy. 

So I reinstalled and put 24.7 and now back to configuring vlans etc.  I had a backup from the initial config on 24.1 so I restored it.

I also setup a rule so I can access admin interface from WAN, which obviously would be a bad idea if it was facing the internet but it's setup on my network temporarily.  This was working before I restored the backup but now I cannot access the WAN interface at all, I can't even ping it, despite adding firewall rules.  I also can't leave the WAN interface from the firewall.  It's almost like the WAN is not doing anything at all.  It shows up that it picked up an IP from my DHCP server but I can't do anything at all from there.

I also removed the checkbox to block bogon networks, as I thought maybe that was causing problems. (I will put that back once it's in prod). 

Any other ideas on how to troubleshoot this?  I want to make sure I can pass traffic through the WAN interface before I put this in production and it would also be nice to be able to configure rules from the WAN interface as I can do it from my PC instead of standing at the laptop on the workbench. 

I'm in the process of upgrading my current firewall to Opnsense from an older version of Pfsense. I have it installed on a Sophos box and have a Dell switch with all the vlans setup so I can have a test environment before I deploy it live.  For now the WAN is connected to my internal network, so I had allowed the admin interface to be accessible, so I can play around with it from my regular PC instead of standing at it directly with the laptop plugged into the switch.

I had the basic stuff working and decided it would be a good time to run an upgrade to bring me to the latest version. (although I now see that this version is considered legacy?  So that's odd. Maybe the upgrade never took)

After the upgrade process and it rebooted I lost access through every port and can no longer get to the admin interface. It's basically blocking all traffic, even internally.  I had it setup so the admin interface is available on all interfaces as a temp measure and have the laptop plugged into a port setup as vlan 2 and LAN is setup as a trunk port to the switch and I get an IP from the firewall which indicates to me that network wise my setup is correct.  However I can no longer access the admin interface either internally via the laptop, or externally via my PC. Cannot ping either.  In the console I went to the firewall log and sure enough I can see that the packets are being blocked.

Is there a way I can gain access to the admin interface without having to do a factory reset?  Like some kind of way to turn off the firewall portion completely?  I'm guessing with the upgrade a default rule may have changed or something and the admin interface is now being blocked.  I had not explicitly allowed it, as it was working already.