Set up a fresh PFSense router and ensure no internet access for connected devices.
Set up a fresh PFSense router and ensure no internet access for connected devices.
I'm working on configuring a new PFSSense router and facing issues with IP assignment. I've got a Sophos SG230 with an Intel i5 quad-core processor running at 2.9 GHz and 16GB RAM. The previous owner had successfully installed PFSSense, and I can boot up the machine and open the GUI. All network interfaces appear to be detected. I placed my TELUS modem/router in bridge mode and connected it to the WAN port; PFSSense assigned a public IP from TELUS. I verified internet access by pinging 8.8.8.8 and confirmed DNS resolution worked. The LAN interface is set to static IP, which matches the PFSSense device's IP used for accessing the GUI. Four other Ethernet ports are active (OPT1/2/3/4). However, when connecting other devices, they display 0.0.0.0 and don't connect to the internet. I tried enabling DHCP on all ports but encountered errors, suspecting a conflict with the static IP setting. I considered using the LAN interface for DHCP, but it triggered warnings about running a "Router services advertising" service.
They need to allocate those interfaces, connect the ports, and set up firewall rules. Refer to the guide for details.
I've updated the connection setup on the LAN segment. The switch is now linked to the LAN, and devices accessing PFSSL are receiving IPs from the firewall. I'm still facing problems with downstream devices losing internet access even though they have IP addresses. I've verified the firewall can reach the internet through standard pinging and DNS checks, but it seems the default rules aren't sufficient for routing. According to the Netgate documentation, I shouldn't need extra firewall configurations if PFSSL operates as a router. Could there be an issue with NAT or interface settings?
It's generally a good idea to configure bridging properly; otherwise, you might lose LAN connectivity with pfSense. Ensure everything aligns correctly—it should function as intended. Verify the firewall settings, specifically the NAT rules, so the WAN interface displays your LAN IP range and the NAT address points to the WAN.