WAN Interface IP Different from Public IP.
-
Perhaps a caching issue in your browser and/or your PC?
You could always try checkmyip.com for a third opinion, but it's much more likely to be a caching hiccup (what's ipchicken say now?).
-
IPChicken.com appears to be down. Maybe it was their issue.
-
Perhaps something in your ISP?
ipchicken.com works fine for me in Pacific NorthWest (or Pacific SouthWest - Canada :) )You don't happen to have Snort/Suricata/Squid involved in this mix do you?
-
your browser using a proxy be it intentional or a hijack, you have a vpn setup on client or pfsense..
Unless you are using something to send your traffic elsewhere be it vpn or proxy.. Your public IP that pfsense gets on its wan would be the public IP you should see when going to these IP checkers online.
-
Sounds like your ISP has you on an internal network, I get the same thing from my ISP. Call your ISP and ask them if that's the case.
I had to request a static public IP to solve my issue (double NAT). My WAN is still a private IP but I at least I have control of my network now.
-
My WAN interface is setup to get a public IP via DCHP from Comcast.
You cannot setup it to get a public IP, sorry. What you have now is probably 'a dynamic IP via DCHP'.
What is your current WAN IP exactly? Feel free to mask 2 last octets. -
You cannot setup it to get a public IP, sorry. What you have now is probably 'a dynamic IP via DCHP'.
Whether an IP is dynamic or static doesn't influence whether it's public. On Comcast, he's getting a public IP via DHCP.
Sounds like it was just a temporary problem of some sort with one site. https://pfsense.org/ip.php and https://forum.pfsense.org/ip.php are two more you can use to check your IP. Those don't cache anything, what it displays is definitely the IP your request is coming from.
-
@cmb:
Whether an IP is dynamic or static doesn't influence whether it's public.
Exactly. Fully agree.
What I'm trying to say that the customer will get whatever IP assigned by the ISP.
There is no (to my knowledge) configuration option in pfSense 'to get a public IP', that's an ISP's decision.Sorry, I missed that OP was able to see the right IP on another site.
-
Squid could be the culprit
-
It is quite interesting to find this article, as I'm having a similar issue. I have an Xfinity XB7 modem that I set to bridge mode. My pfSense WAN IP is different than my XB7s WAN IP. For instance, the XB7 obtained, via DHCP, 174.51.x.x. My pfSense WAN IP, again obtained via DHCP, is 98.245.x.x. I'm able to get on the internet, so no big deal. One thing that I do see also is consistent denied traffic from the 174.51.x.x IP to the 98.245.x.x IP.
I've cleared cache and what not, tried from multiple hosts on my network and all of them see the same thing. When I lookup what my external IP is, it's the 98.245.x.x IP. I also tried cloning the MAC of the XB7 onto the WAN interface for the pfSense, which the firewall now shows the right IP, but I can't get online. I also statically assigned the WAN IP on the pfSense to the IP that the XB7 obtained. I've rebooted multiple times but to no avail. I'm thinking now this might be something on Comcasts side, but figured I'd ask. Cheers!
-
That's normal for Comcast.
My ISP does the same to us from time to time.
