Changing default LAN IP address
-
I have successfully installed pfSense with a default IP address for the LAN, 192.168.1.1, which, unfortunately conflicts with the IP address associated with my WiFi router. I have attempted two fixes: (i) reset the address to 192.168.1.9 (alternatively to 192.168.2.1) on the console, (ii) change the IP address to the same two addresses in the GUI under Interfaces/LAN/Static IPv4 Configuration/IPv4 Address. After each of these attempts, I was unable to re-access the pfSense installation via the LAN port, using 192.168.1.9 (alternatively 192.168.2.1). The only way that I was able access the installation was by reloading the default settings again and using 192.168.1.1. Any suggestions?
-
@metalrat easiest way would be to change the LAN interface IP via console (something like 192.168.50.1) and then make sure that dhcp is disabled. Then statically set your laptop Ethernet adapter to have IP 192.168.50.100 (or so), then access the router via the web configurator and set up dhcp and firewall rules etc. Once done, I’d reboot the router just for fun and then reset your laptop Ethernet adapter to use dhcp versus static IP. That should have you on your way. In general, always avoid 192.168.1.1 (as you have learned no doubt)
-
@metalrat Is there some reason you can't just change the wifi IP address?
-
@kom
Thanks for the quick reply! I'll try resetting the firewall IP address as suggested by the previous reply and see how that works out because the Verizon router is attached to a set-top box and there are apparently hard-coded address references that break things that tech support won't help with (which is a recurrnt issue for me on the outskirts of the connected word).
MR -
@gabacho4
Thanks for the helpful suggestion! I set the address to 192.168.50.1 via the console, set the laptop to 192.168.50.100, disabled dns, rebooted both systems, tried unsuccessfully to access the web configurator ... until, on a hunch, I managed to suppress Firefox's heavy-handed defaulting to https and finally managed to connect to http://192.168.50.1. Thanks again! -
@metalrat glad you got it worked out. Best of luck with the rest of your configuration and packet pushing!
-
@gabacho4
Thanks for getting me over the first hurdle. I've now got my device configured as a rudimentary hardware firewall, with all of the basic settings ... I'll see if it will play nicely with my WiFi router, and if that is not an unmitigated disaster, I'll work through the documentation and see how VPNs and other layers can be added incrementally.
