Attempting to link an interface to an IP address is not working in pfSense.
Attempting to link an interface to an IP address is not working in pfSense.
Hey everyone, I'm having trouble with this setup on pfSense. I want to configure an interface for my home WiFi router using the static IP 192.168.10.128/24. The goal is to cover the range from 192.168.10.128 to 192.168.10.255 so devices can connect through DHCP on the second half of that subnet. I'm seeing the error "This IPv4 address is the network address and cannot be used," which is confusing because the address range isn't being utilized anywhere else on the network. It looks like no other interfaces are using this subnet, so why isn't it working? I thought assigning up to 192.168.10.126 would be fine before hitting the network address space. I'm not sure why this is happening or how it should work. Thanks for your help!
Are you focusing on separating wireless devices in the back portion or all DHCP clients? If your router allows AP-only mode, choose that setting then set pfSense to permit only DHCP for the second half of the subnet. This maintains network cohesion and delivers consistent outcomes. Otherwise, if your configuration follows modem → router → AP → pfSense, this approach won't apply.
Adjusted the DNS range in PfSense under Services, then DHCP Server, and found the IP settings. You may be using your router as a DHCP server or the WAN interface, and you need to ensure it's configured correctly for your network setup. Confirm if you're treating the router like a traditional AP or a DHCP server.
You're configuring the device interface or assigning its IP through a fixed DHCP allocation? It seems you're trying to define the subnet it operates on. Could you clarify if you're using any VLANs? For setting up an interface, I'm uncertain about other options besides the standard 192.168.x.x range. If you aim for a specific address like 192.168.10.128, that would require a different network structure—likely a /25 instead of /24. Would it be simpler to assign the default gateway as 192.168.10.1 and restrict DHCP to that range? This way, the gateway would remain consistent while limiting IP distribution. Please share more details for better guidance.
To clear up the mix-ups, most of the issues stem from trying to set up a VLAN without the V component. Right now, I'm attempting to assign separate interfaces for different subnets but it seems challenging. The goal was to split the 192.168.10.x range, yet it appears more complex than expected. This setup isn't ideal. It looks like I only have a few options left—DHCP is working, but isolating a LAN interface for WiFi-only traffic is proving tricky. The idea of starting from .126 with a 25 prefix works in theory, but the DHCP range seems limited to .1 through .126, which isn't what I anticipated.
This approach is being taken because you're using what's available right now. It's not about having multiple subnets, but rather adapting to the existing setup. I'm not splitting across interfaces for the sake of it—just to fit the configuration you have. There are plenty of other subnets you could use if needed.
I have four interface ports and I’m hoping to use them all in one direction or another, even with a switch.
I think I’m mainly trying to test if it’s possible just for simplicity. It’s convenient to have everything on the same subnet, but honestly, what’s the point anyway?
To mimic a switch setup, you build a bridge and set it as the LAN interface. Then assign each network adapter to the bridge with default configurations and add them as member interfaces. Be careful not to apply settings prematurely, or you’ll lose access to the Web UI. A helpful tip is to use distinct subnets if you have multiple ports, creating two separate LANs until you’re ready to merge them by removing the old one and reapplying the new bridge with your desired IP range. In my case, I mapped it to a VLAN1 interface since I previously used PPPoE over the WAN port and also linked a VLAN to the WebUI on the same port, but the approach remains consistent. Argh, the forum is being tricky and won’t let me embed images easily.
If your aim is this, you don’t have to rely on wireless clients behind double NAT. You can keep the router in AP mode while setting up another physical network interface on the pfSense device to connect to a different subnet with internet access. This would separate it from the wired network, allowing you to manage DHCP as desired. Just assign the IP address you reserve for the AP. It seems unnecessary to use a larger subnet than a standard /24. However, this approach could be quite inefficient.