I did a test. Through China Telecom, blocked. Through Unicom mobile network, not blocked. I will do a traceout when I am back home.
|
FireFox Tool to change IP Location
Quote:
I discovered all kinds of plugins and extensions for Browsers that can change your physical location. Like Google did not recognize Saipan as the USA so our Google Voice got charged extra money for long distance. I changed our physical location to Mountain View California, and that way got FREE Phone through Google Voice anywhere in the world :) It worked too for shopping. Saipan will not allow electronics or appliances to be purchased through the mail or online. And also, places like Amazon and eBay the Sellers have restrictions on what Countries they Sell to. We used the IP Plugin to do the shopping without trouble, and right at the last minute when doing the funds part (pay) THEN add the correct shipping and billing, and most of the time the bots did not catch it. An example is linked below. I do not remember exactly which tools we used. There are a bunch out now so try a few. Or build your own. We need more of these as the we get more and more attacked in these ways online. https://addons.mozilla.org/en-us/fir...ddon/anonymox/ May the Source Be With You Always!!! |
Quote:
Naive question, possibly. |
Quote:
|
My trace route via china telecom ISP. It looks like that I blamed the wrong party. I am blocked somewhere in US.
traceroute linuxquestions.org traceroute to linuxquestions.org (75.126.162.205), 64 hops max, 52 byte packets 1 192.168.0.1 (192.168.0.1) 1.544 ms 1.100 ms 1.141 ms 2 183.38.88.1 (183.38.88.1) 27.221 ms 26.340 ms 792.530 ms 3 119.136.1.85 (119.136.1.85) 24.671 ms 45.729 ms 24.810 ms 4 121.15.179.94 (121.15.179.94) 25.470 ms 27.250 ms 24.068 ms 5 121.34.242.234 (121.34.242.234) 43.872 ms 27.370 ms 27.434 ms 6 202.97.33.238 (202.97.33.238) 28.123 ms 32.626 ms 166.234 ms 7 202.97.60.146 (202.97.60.146) 27.132 ms 28.780 ms 27.499 ms 8 202.97.58.230 (202.97.58.230) 201.710 ms 201.444 ms 238.237 ms 9 202.97.50.34 (202.97.50.34) 199.869 ms 197.014 ms 204.046 ms 10 xe-5-3-2.edge3.losangeles1.level3.net (4.71.136.109) 413.271 ms 198.743 ms 198.928 ms 11 ae-4-90.edge1.losangeles6.level3.net (4.69.144.208) 196.186 ms ae-3-80.edge1.losangeles6.level3.net (4.69.144.144) 187.063 ms 385.991 ms 12 te2-5.bbr01.cs01.lax01.networklayer.com (4.26.0.70) 185.496 ms * * 13 ae7.bbr01.cs01.lax01.networklayer.com (173.192.18.166) 203.209 ms * 327.763 ms 14 ae19.bbr01.eq01.dal03.networklayer.com (173.192.18.140) 307.216 ms 307.017 ms 228.832 ms 15 ae0.dar01.sr01.dal01.networklayer.com (173.192.18.211) 226.973 ms ae0.dar02.sr01.dal01.networklayer.com (173.192.18.253) 219.280 ms 220.052 ms 16 po2.fcr02.sr04.dal01.networklayer.com (66.228.118.182) 332.935 ms 423.559 ms po1.fcr02.sr04.dal01.networklayer.com (66.228.118.178) 710.695 ms 17 * * * 18 * * * 19 * * * 20 * * * |
same was to me,traceroute stop to *networklayer.com,with another ISP (same country)was no problem.
|
I sent a traceroute record to the admin of LQ and the problem is solved.
|
All times are GMT -5. The time now is 10:32 PM. |