No WAN
-
Remove the "Home Router"
Cable Modem -> pfSense -> Switch -> Computers
Or you can try this:
If you connect the "Switch" or a Single PC to the "Home Router" which ramge of IP it get from the Router ?
-
1. Is the home router supposed to respond to DHCP requests?
2. If so, does it allocate IP addresses in the same IP subnet as 192.168.1.1? If so, you will have to change the pfSense LAN interface IP address to a different subnet (since you probably can't change the home router).Do you see any DHCP response in the pfSense system log (Status -> System Logs System tab)?
-
I can't remove the router, that provides internet and wifi to other areas of the home.
It should be, I've had a similar setup where I ran my traffic through that computer before, so I think it's an issue with my pfSense computer, not my router
Here is the system log: http://pastebin.com/4UJx458Q (rl0 is my wan card, btw)
-
The log shows DHCP requests being sent but no response. What is the status of the pfSense WAN interface (Status -> Interfaces)?
-
It says it's up.
Here's everything about the WAN interface: http://pastebin.com/JeC1v3F8 -
Its a pity you don't post the log extracts etc with your replies - it is a bit more cumbersome to go to another site to get the data when it could so easily be included in the reply.
The interface status suggests the WAN interface is correctly connected to something else which has sent frames back. But those frames don't seem to be DHCP replies.
It would be useful to know if the router is receiving the DHCP requests and to know what it is doing about them. Maybe something on the router is inhibiting a reply - perhaps the DHCP IP address pool is fully allocated.
-
Go to "interfaces/WAN Uncheck "Block Private Networks"
-
Done. Still nothing…
-
What are the LAN subnets of both your router and pfsense box?
-
My router subnet is 255.255.255.0, and my lan subnet of my pfsense box appears to be 192.168.1.255
-
Oops- my mistake…
Your LAN addresses...
If they are both 192.168.1.x one or the other needs to be changed.
-
Your LAN addresses…
If they are both 192.168.1.x one or the other needs to be changed.
That is an important consideration but unlikely to a factor in the DHCP server apparently not responding to DHCP DISCOVER.
Doesthe router have a log showing receipt of the DHCP requests? Maybe something on the router is inhibiting a reply - is the router DHCP IP address pool fully allocated?
-
That is an important consideration but unlikely to a factor in the DHCP server apparently not responding to DHCP DISCOVER.
Even when "block private networks" was clicked?
Id be interested to see a new log now that its been unclicked if it does make a difference…
-
That is an important consideration but unlikely to a factor in the DHCP server apparently not responding to DHCP DISCOVER.
Even when "block private networks" was clicked?
Id be interested to see a new log now that its been unclicked if it does make a difference…
I was just able to play with this… Seems the WAN will still get an address in the private network space even if the "block private networks" box is checked...
-
I was just able to play with this… Seems the WAN will still get an address in the private network space even if the "block private networks" box is checked...
Block private networks is strictly for ingress traffic, DHCP requests are egress.
