Not Getting IP Address from Cable Modem
-
We have pfsense 2.7.0 running on a multi-wan router for our business. One of our internet providers is Optimum online and we connect through an Arris cable modem. We realized recently that no traffic was going through this connection. The WAN interface shows an IP address of 0.0.0.0 on the pfsense router. We have rebooted both the cable modem and the router multiple times. The router is getting a DHCP lease, but still shows the 0.0.0.0 address. We contacted Optimum support and they see the DHCP lease and the MAC address of our router and claim the cable modem shows an assigned public IP address being given to the router.
We have also directly connected a PC to the cable modem, and it is immediately assigned a public IP address by the cable modem so it does not appear to be an Optimum issue or an issue with the cable modem. Any thoughts on why our router is suddenly unable to realize the IP address being offered by the cable modem? Both the router and the cable modem have been installed for several years. The router software had been upgraded to newer versions over the years. Because we have 2 internet connections, we are not sure how long the Optimum connection has been down. It could have been down for a few weeks.
-
@marksabado Does anyone have a hint as to how I might track this issue down? I still can't use one of our two internet providers because the WAN port is not getting an IP address. However, I can plug a PC into the cable modem and successfully get an IP address. Optimum can also see the MAC address of my WAN port when they connect through the Optimum cable modem as well as the IP address the cable modem is trying to assign to it. pfSense just shows 0.0.0.0.
-
@marksabado first thing would be to upgrade to 2.7.2. If you’re not seeing it run this command: https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting
Have you tried powering off the cable modem?
I recall seeing threads about this but I have never had the issue.
-
@marksabado
Are you sure, that the modem is trying to assign an IP to pfSense?Check the DHCP log. You can filter it for client entries.
Also you can sniff the DHCP traffic on the WAN. It is plain text, so you can read, what exactly going on there.
-
@marksabado Another thing to try, the PC that gets an address, spoof it's MAC on the pfSense WAN
-
@SteveITS Thanks, I will try upgrading to 2.7.2. We have been through multiple power cycles of both the cable modem and the router.
-
@viragomann I will try to look at the logs and see if I can get any hints. When I have Optimum on the phone, they can see the MAC address of the router's WAN port. They can also see the DHCP address that has been assigned to the router by the cable modem.
-
@Jarhead I tried all the other suggestions in this thread, but MAC spoofing was the one that worked! I used the MAC address from the machine I tested with the modem and that worked. Does this mean that the ISP is locking on an IP address? If so, why did it take a random machine that I connected to it versus the router that has been connected to the cable modem for years? In any event, I did ask the Optimum technician about this while on the phone, and he claimed that they don't tie to MAC addresses.
Good news, router is now connecting through the ISP. Bad news, will there be a conflict if I place the machine with that actual MAC address back on the network - it is on the LAN side while the router is using this on the WAN port?
-
@marksabado usually powering off the cable modem releases this. Check if it has a battery in it, some with voice do. Possibly, leave it off for a while?
-
..... cable modem.....
Is this a real cable modem or a router?
Normally you install the modem in front of the pfSense and connect
it to the WAN port and at the WAN gateway you select IPv4 & IPv6
DHCP if you are not sorted with an static IP address. -
@SteveITS Thanks, it has been unplugged multiple times, but only for 15-30 seconds. I don't think there is a battery, but happy to try it for a longer period.
-
@Dobby_ Yes, this is how we are setup. There is not a static IP address, but the cable modem assigns an address to the WAN port on the pfsense router through DHCP. This has been stable for several years before it suddenly stopped working and showed an IP address of 0.0.0.0. Since MAC spoofing solves it, I think the cable modem or ISP is somehow locking the old MAC address and excluding it.
