Problem with Lan address 10.0.0.1/24
-
Your doing it wrong then…. pfsense doesn't give 2 shits what network you use for your lan network.. be it 192.168.x.x, 10.x.x.x or 172.16-31.x.x or public space even.
Double check your mask your setting, double check your dhcp server settings.
Here I fired up a vm real quick - set to 10.0.0.1, bing bang zoom everything working. Took longer to download the 2.3.4 image then to set it up ;)
-
At a guess I would suggest it's conflicting with something already on your network. What is your WAN subnet there? Public IP?
Steve
-
1 post wonder prob wont ever be back even. I just respond to such nonsense so that someone else searching for some sort of issue they are seeing and finding this thread don't get the idea might actually be a problem since someone else posted about it, etc.
I agree prob a conflict.. He prob has is old soho router on 10.0.0.1 on the same network.. Or not renewing his dhcp lease or setting static on his machine so can not get to pfsense.
-
Yes, there was conflict on my wan network - it was set as dhcp client on vlan network 192.168.101.0/24, but that vlan was on adapter 10.0.0.1 behind it….
Thank you, everything is ok now :)
-
Thanks for confirming. :)
Steve
-
"there was conflict on my wan network "
What would that have to do with this?
when I change default address to 10.0.0.1/24 Pfsense does not have any Lan address and no dhcp is working either. -
I agree it does not immediately look like something that would prevent DHCP working.
Perhaps the parent was enabled on pfSense also? That would probably do it.
Steve
-
Nor would pfsense care if there was a conflict on the wan layer 2 that matched up with its lan side interface IP, which is a different layer 2. Would could you have routing issues if pfsense say had an IP in 10.0.0/24 on wan, and you tried to setup 10.0.0/24 on lan - then sure.. We see that quite common around here actually
user: How come internet doesn't work?
admin: Well you have same network on both your lan and wan!But this should not stop you from accessing its lan interface from lan side or its dhcp server handing out ips on the lan side layer 2, etc.
-
Indeed. I would expect a more common outcome to be that DHCP client on WAN fails to add a IP in a subnet that exists on LAN. Though separate layer 2sa might be expected to allow it as you say.
However I've seen IP conflicts between WAN and LAN result in no IP on either WAN or LAN.
Subnet conflicts > bad things happen! ;)
Steve
-
you need to resolve the ip conflict issue first.
-
Since this from May I doubt he is still working on this problem ;)
