Dashboard wan/ acutal wan
Hey peeps im having a problem and been fighting it all day. After hours of trying to retrace all my steps of what failed when i did a server reboot im wondering if it is in pfsense. In the dashboard under gateways im seeing my old address but under the interfaces header i am seeing the new ip address from spectrum. I have called them to verify the ip address and the one under interfaces is the correct one. I have been having intermittent connectivity issues. I thought it was pi-hole or unify system as someting happened when i was doing a docker on pihole and unify. i rolled both those two back and then re-configured but still the same issues. Helpz please!!!
Gertjan last edited by Gertjan
did a server reboot
Server ? pfSense is a firewall router, not a server.
I have called them to verify the ip address
What about the one click : http://checkip.dyndns.org, as this will show your WAN IP right away. If I would call my ISP for my WAN IP they would have one question back : what is the colour of my hair ?
Btw : pfsense, under conditions, uses http://checkip.dyndns.org itself to get the real WAN IP.
When pfSense is behind an ISP modem, it will have a real Internet WAN IP on it's WAN NIC, so the IP is known right away. But when it is behind a ISP router, the WAN IP will be RFC1918, so http://checkip.dyndns.org is needed to detect the WAN IP.
What can happens : DNS for pfSense itself is broken (wrong setup) so it can't resolve dyndns.org so it can't detect the WAN IP ...
Btw : the default DNS setup works -always.
edit : test your DNS.
From a LAN device, and pfSense itself, using the GUI or better : SSH (or console if you have to ), access).
Test for local host names, and some known Internet based host names - and some unknown hostnames, so you know that resolving has to happens to obtain the IP info.
Do some ipconfig /flushdns (Windows) while testing because you don't want to test caches.
This post is deleted!
@Gertjan Sorry i was a little drunk when i was posting to get this figured out last night. The reason for the isp call was to see if there was any intermittent issues on their end and to see if there was an issue with signal coming into the modem, not to check the color of my hair so to speak lol. Not sure why i typed server reboot... i lost connectivity /laptop died becasue i forgot it wasn't plugged in when i was updating docker containers on my server and the updates hung, which just so happened to be updating the containers for pihole and unify.
Naturally i started there and ended up doing a full reintall of both of those dockers in case one of them was corrupt. In doing so i also rebooted the Modem, firewall, switch, and server(which houses said containers). When i rebooted the modem it pulled a new ip address from spectrum which i didn't catch until later and after checking everything i started to lean back to the firewall of causing an issue as i had done a few changes in rules last week which happened to also be dns rules to allow a fallback to cf dns if pihole was unreachable.
I rolled back to a known working backup but it didnt fix the issue.
Just realized i was being a complete idiot after reinstalling pfsense. Back to pfblocker i go.