Bug #13503
closed
Default LAN IP on Setup within WAN Range.
0%
Description
On Install of pfSense, if you have an WAN-IP-Range that closes in 192.168.1.1, The routing is impossible until either the defualt LAN IP or the WAN-Network is changed.
Right after Install I get
@pfSense 2.6.0-RELEASE (amd64)
WAN (wan) -> bge1 -> v4/DHCP4: 192.168.0.217/22
LAN (lan) -> bge0 -> v4: 192.168.1.1/24@
(mind the /22, which means 192.168.1.0/24 is within the WAN Range)
Solution: Calculate the default IP depending on the values you get by DHCP on the setup.
Workaround: change the IP for the LAN-IF to a reansonable value by Hand (Option "2) set interfaces IP adress")
(thats why Priority =Very Low)
Updated by Jim Pingle almost 3 years ago
- Category deleted (
Setup Wizard) - Status changed from New to Not a Bug
This is a well known and documented problem and there isn't any viable automated way around it. If there is a conflict it's unlikely the user could even get to the GUI to correct it, so correcting it manually at the console is the only viable alternative.
Forcing a change to the LAN based on a dynamic WAN allocation is unlikely to be viable either, as the user would still need console access to determine what the new LAN subnet is, and if they have console access they may as well change it themselves to a specific known value.