Google.com/ipv6 detects wrong ipaddress


Recommended Posts

As mentioned already PK does filtering? It could be possible your going through a transparent?

The conclusion that the request did not come via a proxy is based on the absense of the Via, Forwarded, X-Forwarded-For and Client-ip headers. It is still possible that a proxy is handling the request without announcing itself in the recommended way.

Is it possible your just getting this page from google from an old cache? Doubt it if that timestamp was correct.

But you say you get that same page, with same "wrong" ip using all 4 of your different ISP connections??? That would point to something after your ISP then, not up to speed on what PK does for internet filtering and such. But I would guess that maybe they could be doing something sneaky on the backend, etc.

Link to comment
Share on other sites

ummm....

I will inspect it further with my ISP, one Network engineer is my friend in the ISP, he always said, they don't use any Cashing Server, and as country level is concern, I know we have 2 Gateways, and PTA (authority) don't filter traffic. they just order the ISP's to do the job.

Thanks for your help.

Link to comment
Share on other sites

As requested before a traceroute would be of interest.. But normal icmp trace might not be very helpful, try a tcptraceroute

example from my box - just snipped out my isp gateway for privacy reasons - after that hop it is of no concern.

root@ubuntu:/home/budman# tcptraceroute -i eth0 google.com 80

traceroute to google.com (74.125.225.34), 30 hops max, 60 byte packets

1 pfsense.local.lan (192.168.1.253) 0.421 ms 0.275 ms 0.270 ms

2 c-24-13-xx-1.hsd1.il.comcast.net (24.13.xx.1) 15.471 ms 16.673 ms 29.268 ms

3 * * *

4 te-1-2-0-5-ar01.area4.il.chicago.comcast.net (68.87.230.53) 21.723 ms 21.684 ms 21.612 ms

5 pos-3-6-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.95.9) 21.504 ms 21.443 ms 21.417 ms

6 pos-1-1-0-0-pe01.350ecermak.il.ibone.comcast.net (68.86.86.38) 21.275 ms 19.220 ms 18.868 ms

7 66.208.228.202 (66.208.228.202) 17.870 ms 22.007 ms 22.622 ms

8 209.85.254.120 (209.85.254.120) 98.548 ms 98.375 ms 17.886 ms

9 ord08s06-in-f2.1e100.net (74.125.225.34) <syn,ack> 17.578 ms 17.665 ms 17.625 ms

Here is normal traceroute

traceroute to google.com (74.125.225.36), 30 hops max, 60 byte packets

1 pfsense.local.lan (192.168.1.253) 0.499 ms 0.486 ms 0.410 ms

2 c-24-13-xx-1.hsd1.il.comcast.net (24.13.xx.1) 14.158 ms 14.096 ms 25.737 ms

3 te-1-2-ur08.mtprospect.il.chicago.comcast.net (68.85.131.153) 12.569 ms 13.742 ms 13.613 ms

4 te-3-1-ur02.epeoria.il.chicago.comcast.net (68.85.176.61) 17.014 ms 17.893 ms 17.975 ms

5 pos-3-7-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.90.53) 19.216 ms 19.143 ms 19.077 ms

6 pos-1-5-0-0-pe01.350ecermak.il.ibone.comcast.net (68.86.87.126) 14.880 ms 19.496 ms 19.413 ms

7 66.208.228.202 (66.208.228.202) 18.150 ms 23.787 ms 19.298 ms

8 209.85.254.120 (209.85.254.120) 18.320 ms 18.222 ms 17.905 ms

9 209.85.250.28 (209.85.250.28) 18.049 ms 17.874 ms 17.274 ms

10 ord08s06-in-f4.1e100.net (74.125.225.36) 16.033 ms 19.509 ms 19.393 ms

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.