What about these then?

72.25.81.133 (172.25.81.133)                        176.625ms asymm  6
 6:  172.29.253.34 (172.29.253.34)                        208.708ms asymm  8
 7:  172.31.16.193 (172.31.16.193)                        186.462ms asymm  8
 8:  172.31.35.138 (172.31.35.138)                        206.554ms asymm 10
 9:  172.31.8.134 (172.31.8.134)                          226.454ms asymm 10
10:  172.25.82.62 (172.25.82.62)                          206.389ms asymm  9
11:  192.168.2.10 (192.168.2.10)

All of them are RFC1918 IPs. Not to be used in a public n/w

On Tue, Oct 9, 2012 at 1:27 PM, Nirmalya Lahiri
<[email protected]> wrote:
> Hi everyone,
>  today I have discover a critical network infrastructure which is almost 
> impossible. I believe very few people have seen this before.
>
>  The story is .... in my office we have leased internet connection with 
> static IP from TATA Communication Ltd. In my local network I have configured 
> network ip (192.168.7.0). So all the PC in my local network has the IP of the 
> range 192.168.7.1 to 192.168.7.253.
>
>  For a experimental purpose yesterday I have ping to 192.168.2.10... It 
> should not return reply. But unfortunately I got reply from a host. After 
> investigation I have found that the host is outside of my local network. 
> Please look into the tracepath report from my local PC to that unknown host.
>
> nirmalya@nirmalya-desktop:~$ tracepath  192.168.2.10
>  1:  nirmalya-desktop.local (192.168.7.103)                 0.141ms pmtu 1500
>  1:  192.168.7.51 (192.168.7.51)                            0.706ms
>  1:  192.168.7.51 (192.168.7.51)                            0.700ms
>  2:  115.115.147.137 (115.115.147.137)                    150.228ms
>  3:  121.240.2.54 (121.240.2.54)                          188.099ms asymm  6
>  4:  121.240.2.57 (121.240.2.57)                          175.322ms asymm  6
>  5:  172.25.81.133 (172.25.81.133)                        176.625ms asymm  6
>  6:  172.29.253.34 (172.29.253.34)                        208.708ms asymm  8
>  7:  172.31.16.193 (172.31.16.193)                        186.462ms asymm  8
>  8:  172.31.35.138 (172.31.35.138)                        206.554ms asymm 10
>  9:  172.31.8.134 (172.31.8.134)                          226.454ms asymm 10
> 10:  172.25.82.62 (172.25.82.62)                          206.389ms asymm  9
> 11:  192.168.2.10 (192.168.2.10)                          217.967ms reached
>      Resume: pmtu 1500 hops 11 back 247
>
>
> In this report 192.168.7.103 is my personal PC, 192.168.7.51 is internal IP 
> of router, 115.115.147.137 is gateway IP of our leased internet connection.
>
> I have already reported it to TATA Communication Ltd. They give us commitment 
> to solve it by 24hour.
>
> Have anyone see this before?
>
> ---
> [Nirmalya Lahiri]
> +  -           [+91-9433113536]
> _______________________________________________
> ILUGC Mailing List:
> http://www.ae.iitm.ac.in/mailman/listinfo/ilugc



-- 
Gayatri Hitech
http://gayatri-hitech.com
_______________________________________________
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc

Reply via email to