I moved my pfSense Spectrum from Altafiber
-
I have seen others talk about this but I do not see a solution for my scenario.
I have installed pfSense on a VM running on a QNAP251 NAS. The NAS have 2 NICs WAN and LAN and I have been running this for YEARS on Altafiber. In an cost savings effort I moved to Spectrum.
-
If I move my WAN cable from the Altafiber modem to the Spectrum modem and reboot the modem I get an IP on the WAN NIC and I see the gateway in the pfSense console with 100% packet loss. I cannot ping anything from pfSense to the internet.
-
If I put the Spectrum router in the mix and plug my pfSense into it, I get an IP on the WAN NIC (its different obviously) and I can get to the internet from my devices behind pfSense but with the double NAT issue, some things do not work.
I want to JUST have my pfSense plugged into the Spectrum modem like I had with Altafiber. I have tried most of what I have read on this forum regarding this issue but I do not believe I have seen any true successful fixes here. I have purchased my own modem in hopes that there is a configuration I can set myself to resolve the issue. We will see.
I am hoping there is someone in my situation that has gotten it resolved that can help.
Thank you
-
-
I assume your WAN is DHCP?
You get a different random dynamic IP address at each connection?
Surprising that it would give you a dhcp lease but not route traffic from it. The Spectrum gateway may not respond to pings, you might need to set an alternative monitoring IP.
-
Yes, as mentioned I do get a different IP when connected to the router. I get the standard 192.bla.bla address as would be expected. When I connect to the modem I get an internet routable IP.
"Surprising that it would give you a dhcp lease but not route traffic from it" - That is the same things that Spectrum told me. After 5 calls to them I finally got a manager that seemed to know what he was talking about. He boiled my configuration down to a non-compatible 3rd party router.
Change the monitoring IP is curious to me. Monitoring suggests something pretty passive I sit more than that?
-
By default pfSense pings the gateway address to monitor the WAN for packet loss, latency and connectivity status. But the ISP gateway does not have to respond to ping and if it doesn't then pfSense will see it as down. If that's the only gateway on the system it should still be the default route but if not then pfSense may switch to some other gateway which may be invalid. Setting a different monitoring IP to use, like 8.8.8.8, works around that.
See: https://docs.netgate.com/pfsense/en/latest/routing/gateway-configure.html#advanced-gateway-settings -
@JoeAshley What model modem? If it is a telephone also modem it might have a battery in it.
Can you confirm either way? (Post the model here if you are unsure.)
With the ISP router out of the mix.. if you go to Diagnostics/Ping..
Can you try to ping something like 1.1.1.1 or 8.8.8.8 and see if that comes back..
Then try to ping a host name from the same tool..
Commercial or Residential account?
