Setup pfSense using your LAN and WAN as you would expect. Make the LAN (for example) 192.168.1.1/24. Now setup OPT1 with a different subnet- say 192.168.2.1/24. Now (and I think this is the step you are missing) go in NAT setup and add a NAT translation, just copy the settings that are in use for LAN and make an entry for OPT1.
With these settings, rules on OPT1 (re0) and OPT2 (re2) will be ignored. Rules on LAN (BRIDGE0) will be honored. So OPT1 and OPT2 will freely communicate like ports on an unmanaged switch. The OPT1 (re0) interface is not known to pfSense yet so it must be added. Interfaces > (assign) Available network ports: re0 Add. OPT1 is created. Jun 18, 2010 · Well, the OpenVPN part isn't really important, but I'd like to set up OPT1 to work as LAN but on a separate subnet (192.168.2.1 instead of 192.168.1.1). Jan 24, 2019 · If not, check pfSense config and make sure DHCP is configured correctly for OPT1 2. run command ping 192.168.99.1 (pfSense) at your computer. You should be able to ping 192.168.99.1 successfully. If not, make sure you have firewall rule setup at OPT1 to allow OPT1-net devices to communicate with each other 1x OPT1 - Random issue? I am trying to configure a second network (OPT1). I have configure the network and gave it an ip address 192.168.0.1 this is on its own subnet. I have plugged a laptop directly into the OPT1 port and attempted to ping the gateway address 192.168.0.1 and get no response! May 03, 2017 · i’m trying to replace the netgear with pfsense sg4860 fw, but quite honestly, i might have bitten more than i can chew as a network noob. while the computer that’s connected to the pfsense appliance is quite fast now, i’m unable to replicate the setup where i can connect to the asus ap. Assign Interfaces¶. In pfSense® software, the Interface Assignments screen at Interfaces > (assign) lists the current system interfaces such as WAN and LAN, and a drop-down box next to each with a list of all available network interfaces on the system (real and virtual).
So, once you get pfSense installed, go to Interfaces->(assign) Assuming you already configured both your LAN and WAN interfaces, it should be clear which interface to choose for the extra port. Then go Interfaces-> in my case, OPT1.
I can't ping past the OPT1 ip address. Might be a switch problem as when I do a traceroute it dies off at the 192.168.5.1 gateway. But I do have the default gateway set to the PfSense OPT1 ip with routing enabled so I don't know what's missing. Which is also weird because a traceroute to the OPT1 ip works perfectly fine.
Make note of your pfSense TCP Port. Mine is currently 443 but I changed it to 444. Go to the Floating Firewall Rules and create a rule which blocks certain VLANs from accessing the pfSense GUI from its TCP Port. The end result is something like this: Test it out by attempting to access the pfSense web interface from a host on the blocked VLAN.
In pfSense® software, the real distinction between “WAN”, “LAN” and “OPT” interfaces is blurred as they are all capable of handling any role. For historical and ease-of-use purposes, the first two interfaces are WAN and LAN. Additional interfaces start at OPT1 and are numbered from there (OPT2, OPT3, … Setup pfSense using your LAN and WAN as you would expect. Make the LAN (for example) 192.168.1.1/24. Now setup OPT1 with a different subnet- say 192.168.2.1/24. Now (and I think this is the step you are missing) go in NAT setup and add a NAT translation, just copy the settings that are in use for LAN and make an entry for OPT1.