Why can i ping a private IP on the internet?

Rickster

Rickster

EVGA Fanatic
Joined
Jul 31, 2012
Messages
23,317
Reaction score
5,607
Location
Joe'berg
Not using a VPN or anything like this. I am actually trying to setup a Lan to Lan VPN, my PC router at home is 192.168.0.1, I thought my VPN was working when i decided to disconnect the VPN but i can still ping whatever device that is.


Code: 
Tracing route to 192.168.0.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Test.router [192.168.1.1]
  2     2 ms     1 ms     2 ms  192.168.8.1
  3     *        *        *     Request timed out.
  4    44 ms    44 ms    38 ms  10.104.38.70
  5    76 ms     *       76 ms  192.168.0.1
 
Last edited:
Rickster said:
Not using a VPN or anything like this. I am actually trying to setup a Lan to Lan VPN, my PC at home is 192.168.0.1, I thought my VPN was working when i decided to disconnect the VPN but i can still ping whatever device that is.


Code: 
Tracing route to 192.168.0.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Test.router [192.168.1.1]
  2     2 ms     1 ms     2 ms  192.168.8.1
  3     *        *        *     Request timed out.
  4    44 ms    44 ms    38 ms  10.104.38.70
  5    76 ms     *       76 ms  192.168.0.1
Click to expand...
those are all private IPs so unless you doing something funky, its your ISP, and do a trace to a public IP so you can see how may private IPs are in the hops
 
so you both have the same ISP?

you should not route bogons, and if I disable telkom does a better job of denying than afrihost:

traceroute to 192.168.0.1 (192.168.0.1), 64 hops max, 52 byte packets
1 172.16.8.1 (172.16.8.1) 11.575 ms 3.910 ms 3.441 ms
2 * * *
3 165-73-14-113.ip.afrihost.co.za (165.73.14.113) 42.676 ms
165-73-14-137.ip.afrihost.co.za (165.73.14.137) 9.178 ms 8.381 ms
4 169-1-21-148.ip.afrihost.co.za (169.1.21.148) 9.753 ms 7.601 ms 7.655 ms
5 169-1-21-132.ip.afrihost.co.za (169.1.21.132) 10.773 ms
169-1-21-133.ip.afrihost.co.za (169.1.21.133) 15.649 ms 9.486 ms
6 100.127.2.170 (100.127.2.170) 11.494 ms 10.263 ms
169-1-21-133.ip.afrihost.co.za (169.1.21.133) 13.366 ms
7 100.127.2.170 (100.127.2.170) 10.044 ms 8.188 ms 9.967 ms
8 * * *

traceroute to 192.168.0.1 (192.168.0.1), 64 hops max, 52 byte packets
1 172.16.8.1 (172.16.8.1) 7.349 ms 3.162 ms 3.297 ms
2 * * *
3 105-187-235-41.telkomsa.net (105.187.235.41) 18.376 ms 8.862 ms 8.645 ms
4 * * *
 
From my home PC via afrihost: My router is 192.168.0.1

Code: 
Tracing route to 192.168.0.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1

Trace complete.

I was using an MTN Sim earlier
 
Looks like you're on MTN?
It's hilarious, their routers arent configured to block private IP ranges traversing their networks. I had this same issue when I was on Supersonic uncapped LTE.
 
Well your traffic is following your default route.
Your ISP is not blocking private ranges and seems like they have routing for private ranges inside whatever network you are in (probably a VRF). You are most likely hitting devices on internal infrastructure of the ISP

Its poor configuration their side, but it happens
 
Somehow this works ?
Anyone have an idea on why

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 3 ms 1 ms 1 ms 10.20.0.1
2 7 ms 4 ms 4 ms *****.ip.afrihost.co.za [****]
3 8 ms 4 ms 4 ms 169-1-21-171.ip.afrihost.co.za [169.1.21.171]
4 7 ms 4 ms 5 ms 169-1-5-202.ip.afrihost.co.za [169.1.5.202]
5 26 ms 24 ms 24 ms 100.127.4.250
6 * * * Request timed out.

Tracing route to 10.0.0.2 over a maximum of 30 hops

1 3 ms 1 ms 1 ms 10.20.0.1
2 4 ms 4 ms 5 ms ****ip.afrihost.co.za [****]
3 10 ms 4 ms 4 ms 169-1-21-171.ip.afrihost.co.za [169.1.21.171]

Telkom LTE
Tracing route to 10.0.0.2 over a maximum of 30 hops

1 5 ms 2 ms 2 ms 172.20.10.1
2 * * * Request timed out.
3 23 ms 34 ms 18 ms 105-187-234-162.telkomsa.net [105.187.234.162]
4 51 ms 26 ms 23 ms 105-187-253-74.telkomsa.net [105.187.253.74]

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 172.20.10.1
2 * * * Request timed out.
3 47 ms 16 ms 17 ms 105-187-234-166.telkomsa.net [105.187.234.166]
4 40 ms 21 ms 21 ms 105-187-253-74.telkomsa.net [105.187.253.74]
5 * * * Request timed out.

Tracing route to 192.168.8.1 over a maximum of 30 hops (A common IP on LTE with Huawei Routers)

1 4 ms 2 ms 2 ms 172.20.10.1
2 * * * Request timed out.
3 50 ms 19 ms 33 ms 105-187-234-166.telkomsa.net [105.187.234.166]
4 42 ms 22 ms 20 ms 105-187-253-74.telkomsa.net [105.187.253.74]
5 * * * Request timed out.
 
William1102 said:
Somehow this works ?
Anyone have an idea on why

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 3 ms 1 ms 1 ms 10.20.0.1
2 7 ms 4 ms 4 ms *****.ip.afrihost.co.za [****]
3 8 ms 4 ms 4 ms 169-1-21-171.ip.afrihost.co.za [169.1.21.171]
4 7 ms 4 ms 5 ms 169-1-5-202.ip.afrihost.co.za [169.1.5.202]
5 26 ms 24 ms 24 ms 100.127.4.250
6 * * * Request timed out.

Tracing route to 10.0.0.2 over a maximum of 30 hops

1 3 ms 1 ms 1 ms 10.20.0.1
2 4 ms 4 ms 5 ms ****ip.afrihost.co.za [****]
3 10 ms 4 ms 4 ms 169-1-21-171.ip.afrihost.co.za [169.1.21.171]

Telkom LTE
Tracing route to 10.0.0.2 over a maximum of 30 hops

1 5 ms 2 ms 2 ms 172.20.10.1
2 * * * Request timed out.
3 23 ms 34 ms 18 ms 105-187-234-162.telkomsa.net [105.187.234.162]
4 51 ms 26 ms 23 ms 105-187-253-74.telkomsa.net [105.187.253.74]

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 2 ms 2 ms 2 ms 172.20.10.1
2 * * * Request timed out.
3 47 ms 16 ms 17 ms 105-187-234-166.telkomsa.net [105.187.234.166]
4 40 ms 21 ms 21 ms 105-187-253-74.telkomsa.net [105.187.253.74]
5 * * * Request timed out.

Tracing route to 192.168.8.1 over a maximum of 30 hops (A common IP on LTE with Huawei Routers)

1 4 ms 2 ms 2 ms 172.20.10.1
2 * * * Request timed out.
3 50 ms 19 ms 33 ms 105-187-234-166.telkomsa.net [105.187.234.166]
4 42 ms 22 ms 20 ms 105-187-253-74.telkomsa.net [105.187.253.74]
5 * * * Request timed out.
Click to expand...

I answered this above
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X