| View previous topic :: View next topic |
| Author |
Message |
xtertristl
Joined: 21 Oct 2009
|
 Posted: Thu Jun 23, 2011 11:07 pm Post subject: Blocked Sites |
 |
|
Hey all I'm currently teaching in Incheon and have noticed today that all my gaming news websites have been blocked for ex. http://ign.com/ I'm getting really board at work with nothing to read.
Does anyone know the process for getting a site unblocked is it worth my time or should I just proxy my way around it?
Also I'm getting a different block something from the SECUI NXG blocking my news from this news site. http://www.theglobeandmail.com/
Same question as above.
Thanks in Advance |
|
| Back to top |
|
 |
teachingld2004
Joined: 29 Mar 2004
|
| Posted: Tue Jun 28, 2011 6:11 am Post subject: blocked sites |
|
|
Easy to fix.
Go to a pc room with a usb
download UltraSurf
and put it onto the usb. Put it on your computer. I did it, and if I can do it, anyone can. |
|
| Back to top |
|
|
djloekee27
Joined: 08 Sep 2010
|
| Posted: Tue Jun 28, 2011 6:12 pm Post subject: Re: Blocked Sites |
|
|
| xtertristl wrote: |
Hey all I'm currently teaching in Incheon and have noticed today that all my gaming news websites have been blocked for ex. http://ign.com/ I'm getting really board at work with nothing to read.
Does anyone know the process for getting a site unblocked is it worth my time or should I just proxy my way around it?
Also I'm getting a different block something from the SECUI NXG blocking my news from this news site. http://www.theglobeandmail.com/
Same question as above.
Thanks in Advance |
use their ip address.
ign is 61.111.58.27
theglobeandmail is 199.246.67.250
i pinged ign at that is what i got but it's not working in my browser. but other ip addresses for sites like photobucket, myspace and mediafire work. |
|
| Back to top |
|
|
archmagos
Joined: 14 Nov 2006
|
| Posted: Wed Jun 29, 2011 4:49 pm Post subject: Re: Blocked Sites |
|
|
| xtertristl wrote: |
| Hey all I'm currently teaching in Incheon and have noticed today that all my gaming news websites have been blocked for ex. http://ign.com/ I'm getting really board at work with nothing to read. |
You should be aware that www.ign.com are just ign.com are probably not being treated in the same way. This could be deliberate or a simple omission on somebody's part.
Here is a successful traceroute from Busan to www.ign.com:
| Code: |
1 119.217.50.193 (119.217.50.193) 0.567 ms 0.517 ms 0.492 ms
2 211.220.188.129 (211.220.188.129) 0.401 ms 0.414 ms 0.350 ms
3 59.22.53.252 (59.22.53.252) 0.397 ms 0.357 ms 0.314 ms
4 112.174.161.209 (112.174.161.209) 0.669 ms 0.512 ms 0.482 ms
5 112.174.236.137 (112.174.236.137) 1.847 ms 1.497 ms 0.936 ms
6 112.174.55.209 (112.174.55.209) 7.163 ms 7.122 ms 7.140 ms
7 112.174.82.14 (112.174.82.14) 6.938 ms 7.252 ms 6.976 ms
8 112.174.84.166 (112.174.84.166) 7.295 ms 7.366 ms 7.152 ms
9 112.174.88.246 (112.174.88.246) 190.168 ms 190.208 ms 190.177 ms
10 ae0-106.sjc10.ip4.tinet.net (213.200.66.169) 178.331 ms 178.022 ms 178.136 ms
11 pacnet-gw.ip4.tinet.net (77.67.68.234) 182.329 ms 182.378 ms 182.215 ms
12 gi4-0-0.gw2.sin3.asianetcom.net (202.147.61.226) 228.838 ms 228.769 ms 229.056 ms
13 AKT-0013.asianetcom.net (203.192.163.234) 231.353 ms 230.846 ms 230.973 ms
14 a96-17-180-155.deploy.akamaitechnologies.com (96.17.180.155) 229.914 ms 229.959 ms 229.798 ms |
Now, compare it to ign.com:
| Code: |
1 119.217.50.193 (119.217.50.193) 0.502 ms 0.506 ms 0.479 ms
2 211.220.188.129 (211.220.188.129) 0.391 ms 0.393 ms 0.359 ms
3 59.22.53.252 (59.22.53.252) 0.323 ms 0.502 ms 0.660 ms
4 112.174.161.209 (112.174.161.209) 0.883 ms 0.546 ms 0.467 ms
5 112.174.237.133 (112.174.237.133) 1.811 ms 1.343 ms 0.953 ms
6 220.73.149.205 (220.73.149.205) 7.742 ms 7.611 ms 7.153 ms
7 112.174.82.202 (112.174.82.202) 76.284 ms 7.020 ms 6.995 ms
8 112.174.84.34 (112.174.84.34) 7.286 ms 7.219 ms 7.150 ms
9 112.174.87.118 (112.174.87.118) 171.139 ms 171.150 ms 171.186 ms
10 so-7-0-1.edge2.LosAngeles1.Level3.net (4.71.134.17) 147.897 ms 147.898 ms 147.827 ms
11 * * *
12 Savvis-Level3.Dallas3.Level3.net (4.68.110.94) 145.732 ms 145.747 ms 145.836 ms
13 cr2-tengig-0-7-4-0.lay.savvis.net (204.70.198.9) 142.654 ms 142.691 ms 142.026 ms
14 cr2-tengig0-7-0-0.sanfrancisco.savvis.net (204.70.196.198) 144.315 ms 144.366 ms 144.692 ms
15 er1-te-2-0-1.SanJose3Equinix.savvis.net (204.70.200.234) 144.531 ms 144.456 ms 144.691 ms
16 hr1-te-2-0-0.santaclarasc5.savvis.net (204.70.200.206) 157.749 ms 157.644 ms 157.766 ms
17 216.33.4.58 (216.33.4.58) 144.881 ms 289.362 ms 208.394 ms
18 * 64.14.0.122 (64.14.0.122) 325.803 ms !X *
19 64.14.0.122 (64.14.0.122) 143.921 ms !X * 144.423 ms !X |
Essentially, ign.com takes a different path (more hops and is a lot slower) and is filtered by the server 64.14.0.122 right at the end (as indicated by the !X). Thus, entering ign.com will not result in a redirect to the correct site www.ign.com (as would occur with many sites). This is just probably temporary behaviour though.
| djloekee27 wrote: |
use their ip address.
ign is 61.111.58.27
...
i pinged ign at that is what i got but it's not working in my browser. |
See above to understand why this happens. The solution? Just use www.ign.com in case things do break.
Generally, it is preferable to avoid using fixed ips when browsing. Firstly, my route did no go through this ip address at any point. Second, hop 14 of the first traceroute indicates that ign is delivered over Akamai's CDN at particular ip address, which obviously could change as Akamai load-balances demand on its servers. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
