No WAN IP after power outage
-
@luddite said in No WAN IP after power outage:
LAN Interface (lan, igb1)
10.10.10.1Keep in mind : the day you install pfBlockerNG-devel, you'll have a IP address conflict to deal with.
-
@gertjan said in No WAN IP after power outage:
Keep in mind : the day you install pfBlockerNG-devel, you'll have a IP address conflict to deal with.
Thanks- I have pfBlockerNG obviously already :-)
-
@luddite That is not what he has meant...
-
@luddite said in No WAN IP after power outage:
I have pfBlockerNG obviously already :-)
What IP addresses is used by the web server ??
The default is pfBlockerNG web server VIP is 10.10.10.1 ... your LAN also uses 10.10.10.1(/24).
You're good for some network fireworks. -
@gertjan pfBlocker changed that for me.
-
This post is deleted! -
@bob-dig said in No WAN IP after power outage:
@luddite That is not what he has meant...
Ah - yes I see. Thanks for pointing that out. I have the non devel version installed and no plans to install the devel version.
@stephenw10 said in No WAN IP after power outage:
If those are all /24 subnets then you're probably OK.
Please post the actual interface IPs and subnets as shown in Status > Interfaces.
Steve
I found that the WAN was /32 and I changed that to /24
@bpsdtzpw said in No WAN IP after power outage:
@luddite said in No WAN IP after power outage:
@bpsdtzpw oh, i think this might be it.
Note: modem has internet IP but its lan range is 192.168.1.x
So 192.168.1.x (.2 for wan) 192.168.0.x (lan) are in the same subnet but 192.168.1.x (wan) 192.168.2.x (lan) are not in the same subnet?
Your modem probably is setup to use 192.168.1.1 with a subnet mask of 255.255.255.0. This collides with addresses handed out by your existing LAN DHCP server. You need to separate the spaces, and use a static route to reach the modem from a 192.168.2.x, subset 255.255.255.0 LAN. To add the static route, use system/routing/static routes, then add an entry with "destination network" = 192.168.1.1/32, "gateway" = whatever your WAN gateway is (yeah, the modem is on the WAN from the point of view of pfSense), and a nice description.
Also remember to make your modem's admin page inaccessible from the internet at large, so as to minimize security issues.
I think this did the trick. I made the WAN IP static and also added the WAN Gateway.
I pulled the plug on the modem and everything runs as per expected. I rebooted the router and it all worked expected. I Uplugged the phone line on the modem and it was all as expected. Amazing. Such a silly oversight that I never would have discovered a fix for without everyone's help.
Thank-you All!!!! Fingers crossed it doesnt have any unexpected side effects ;-)
-
It looks like you may also be hitting this: https://redmine.pfsense.org/issues/11545
Because the address shown as the LAN is clearly actually the pfBlocker VIP, which is a /32.That's probably not an issue on the LAN but worth watching out for.
Steve
-
@luddite Sweet! Yeah, address conflicts can cause mysterious behaviors.
-
@stephenw10 said in No WAN IP after power outage:
It looks like you may also be hitting this: https://redmine.pfsense.org/issues/11545
Because the address shown as the LAN is clearly actually the pfBlocker VIP, which is a /32.That's probably not an issue on the LAN but worth watching out for.
Steve
I followed this guide for the most part and after everything was running I installed pfBlockerNG and it force changed the LAN IP. I didnt touch it. Nothing broke so i thought it was normal and left it as per the forced change. Is that wrong?
https://www.youtube.com/watch?v=bz45r_4BREw
-
It shouldn't change the interface IP and it probably didn't. If you hit that bug it will just show like that in the Status. If you run ifconfig at the command line you will find the LAN still using the same IP address and subnet you set with 10.10.10.1 as a VIP on that.
Steve
-
@stephenw10 ok- I will investigate after work. Thanks for the info.
