Order / Timing of Booting Modem and pfsense PC

montreel

Gosh, I feel like a dingdong! I seem to have a MAC binding issue with my pfsense box (x64 SFF PC) and my modem (Motorola MG8702 in bridge mode). igb0 is my WAN. igb1 is my LAN. igb3 and igb4 are unpopulated.

What is the timing and order of operations that you use to get it to bind properly? In other words, Do I let pfsense fully boot and then power on the modem?

Thanks in advance!

stephenw10

You should be able to power both on at the same time and have it boot to a working connection. Otherwise it won't come back up correctly in the event of a power outage.

You might need to prevent pfSense pulling a dhcp lease from the modem itself before it syncs with the cable. Many cable modems will do that to allow diagnostics. You can add a the modems local IP to reject leases from in the pfSense WAN config.

provels

FWIW, I always have to boot the modem (Netgear cable) first and let it hook up, then pfSense. If I ever simply reboot the modem, the pfSense Dashboard's Gateway widget constantly cycles from "Online" to "Unknown" ad infinitum.
@stephenw10 said in Order / Timing of Booting Modem and pfsense PC:

You can add a the modems local IP to reject leases from in the pfSense WAN config.

Good point, bc once the modem starts handing out leases, you're stuck. Right or wrong, WAN's got a lease and it's satisfied.

stephenw10

You can also add boot delay to pfSense to allow the modem to finish booting first. That can be required for some setups though it's an annoying delay at normal reboots!

mer

On Comcast, with a Zoom cable modem (my device, not a Comcast one)
What I've noticed:
If pfSense is up and modem not fully on network, pfSense WAN seems to get a private IP (link local IPV4 if I remember correctly), but when modem comes fully on network, WAN gets an IP from Comcast.
So if both powered on at same time, pfSense WAN may get an unroutable address for a little bit, then as modem comes online WAN gets a new address.

I think you could test your hardware by simply leaving pfSense off, wait until modem gets fully on network, then power on pfSense. At that point it should get an IP from your ISP.
Then test the case where pfSense is up and modem reboots (like maintainence) and see what happens.

stephenw10

Yup if the modem bounces the link when it syncs with the cable then pfSense will pull a new lease. Not all modems do.

provels

Maybe it's not needed any more, but I've had this set for a long time in Interfaces / WAN / DHCP Client Configuration:

mer

@provels Nice. That would cover what I see temporarily in my configuration. Of course it assumes the modem is always at 192.168.100.1.

But nice.

provels

@mer I imagine it could depend on the brand of modem, but it's be a fixed IP in the Netgears and Motorolas I've had. Or if the modem even offers DHCP in the first place.

johnpoz

@mer said in Order / Timing of Booting Modem and pfsense PC:

Of course it assumes the modem is always at 192.168.100.1.

That IP is pretty common across the makers of modems, sure it could be something else.. But if you get a lease in the 192.168.100.x, its not like the modem would change its IP from 192.168.100.1 to 192.168.100.Z etc..

I have a arris S33 and that is the management IP, all the previous modems I have had over the years it has always been that 192.168.100.1 IP..

mer

@johnpoz @provels I know that "unstated industry standard" is 192.168.100.1, but I've learned the hard way that assuming may cause problems.
Now if IANA had something stating 192.168.100.1 is the default address for devices like cable modems, I'd accept that as gospel

:)

johnpoz

@mer nobody said its gospel and they all use it.. But clearly you got an IP in the 192.168.,100.x range - what I stated is if your device is in fact using 192.168.100.1 - its not going to change to say 192.168.200.1 out of the blue..