Is there anyway to check if unifi is on public or private ip without going thru the wifi router to check?

Such as using traceroute etc. kind of commands.

I use Windows for this test.
500Mbps link, so supposedly on public IP.

How to interpret:
Gateway connects at least 2 disjointed network, so there are at least 2 interfaces, one facing you (inside), another facing away from you. But, for 2 gateways to talk to each other on IPv4 network, the interfaces facing each other need to be on same subnet.

Traceroute returns ping from the inside-facing interface of each gateway hop.
In my case, I only have 1 layer of router inside my home network, thus the very next hop is the inside-facing interface of a router that is no longer inside my home network.
Since the inside interface of that 2nd router is on public IP, I can assume that the external interface on my router is also public IP on the same subnet.

Logically, if you see many more responses from private IP before you get response from the first public IP, and you do not recognise those private IP as being part of your own network, then it can already be assumed that your router is assigned private IP.

https://iknowwhatyoudownload.com/en/peer/
this website tracks IP in DHT for torrent. If u see the list saw a lot stuff which u do not personally torrent then u know someone is sharing the IP which means it was private. since public ip is unique to ur household only but several private ip will share a same public ip under tm

This post has been edited by akhito: Yesterday, 09:51 AM

My torrent client say port blocked on router/gateway after private ip

Here's the least technical way I can think of.
1. Get your ipv4 from https://www.whatsmyip.org.
2. Ping the address from from your phone mobile data.
3. If can ping, then turn off your house wifi router.
4. If ping stops then your house is public IP.
5. If ping continues then your house is private IP.

yes i am existing 100Mbps plan only no change and no upgrade
no apply 30mbps i apply 100mbps since may 2019

Hi guys, wta, I live in high rise building, just now contractor came and told that the old cabling is copper wires, then they need to pull fibre cable from 18th to 20th floor which cost me around rm200-300, is this normal? From what I learn, cabling outside my premise is free right?

"they need to pull fibre cable from 18th to 20th floor"
Your cable route is a bit complicated and therefore charged as a Non-standard installation

They told this building can only do cabling by ceiling, so I suppose this charges is normal right?

When watching Twitch, my Playback Bitrate go up and down. Is this normal? Any way to solve it except using VPN?

Hmm just tried visit the website by connecting home internet (LAN cable)
ping the address by connecting phone hotspot and unplug LAN cable
Unable to ping

Router may be blocking/ignoring pings as a security thing

Yes, possible.

Can be 2 possibility:
1. You're on public IP and your house router is ignoring ping. Possible but unlikely.
2. You're on private IP and the router doing CGNAT for you is ignoring pings. Highly likely.

So most probably, I'd say that you're on private IP.

My neighbour on Unifi 100Mbps still getting public IP.


Start to ping from my Unifi and then I reboot his router.


This post has been edited by soonwai: Today, 12:50 AM

Depends on router also. I think Asus router (at least for merlin) the default behavior is to ignore ping?

Possible. If ping not working then cannot use ping to test.

Both traceroute and ping uses ICMP, but their working differs.

PING sends ICMP Type 8 ("echo") and the destination responds with ICMP Type 0 ("echo reply").

TRACEROUTE manipulates TTL value of IP packets, and as a packet passes through each gateway, its TTL value is decreased. Remote gateway that the packet ends up with TTL=0 returns ICMP Type 11 ("time exceeded").

So if you can't use PING, then use TRACEROUTE.

If you just want to determine whether your router is assigned public IP or private IP, then using TRACEROUTE is sufficient. Just one step, and you should learn to be able to interpret it. And command is similar and repeatable on any operating system.

No need to query remote whatsmyip, no need to check inside router's info page, no need to ping here and there, no need to cross fingers in hoping to (not) hit open port on router's external interface.

Oltromen Ripot has posted twice already with very good explanations. Perhaps examples will help westlife. Do a traceroute and see which of the below is closest to yours.

This is private IP. (Digi mobile data) whatismyip: 115.164.213.14


This is public IP. (Unifi 800) whatismyip: 175.142.125.212 (see how this IP corresponds to #2 below)


* anything beginning with a 10 and 172.16 to 172.31 are private IPs.

This post has been edited by soonwai: Today, 05:20 AM

Home network is usually flat with only 1 router.
But companies can have multiple layer of routers. It might not be 1st in the traceroute result.
One needs to determine where is the network border; which IP is internal-facing interface IP of the edge-most router.

The required "skill" is in interpreting what comes right after your edge-most router.
Because in IP network, adjacent gateways facing each other need to be in same subnet in order to be able to talk to each other.

If the 1st gateway outside of your network is public IP, then your edge-most external-facing WAN interface have public IP.

If the 1st gateway outside of your network is private IP, then your edge-most external-facing WAN interface have private IP.

And it is almost certain that ISPs will not block/prohibit ICMP Type 11 ("time exceeded") response coming from the gateway that is assigned as your router's gateway.
It will be crazy if their own technician cannot perform troubleshooting with a key tool.

Also note; 10.0.0.0/8 was previously used for internal routing of those internet providers. As seen in the Unifi example, some of those network interconnections are still using it in their internal networks.
So if you see a pattern like public-private-private-private-public IP sequences, ignore them.
Since the intent is to determine whether your WAN interface is on public IP or private IP, interpreting what's next to your network border is sufficient for the scope.