[SOLVED] linuxquestions.org is blocked here in China

kite · 06-15-2013, 07:10 AM

Well, finally. I need to visit here through tunnelling now. Nothing could be more annoying than this.

H_TeXMeX_H · 06-15-2013, 08:33 AM

So, who is blocking you, this site or the Chinese firewall ?

kite · 06-15-2013, 08:56 AM

The nasty Chinese Great Firewall! This is a government against its people.

tronayne · 06-15-2013, 01:07 PM

Looks like somebody's watching and reading, see: http://www.linuxquestions.org/questi...3/#post4965354.

tomtomjkw · 06-15-2013, 05:28 PM

I'm not exactly too proud to say that Polish major internet providers had lived up to Chinese standards - I've not been able to browse linuxquestions.org from my home or office for about a month...

Celyr · 06-15-2013, 05:32 PM

What? It should not be possible. Poland is in the UE. There are laws about net neutrality.

guanx · 06-15-2013, 05:36 PM

Quote:

Originally Posted by kite

The nasty Chinese Great Firewall! This is a government against its people.

Can you prove it? Is it a connection reset? What happens if you connect to http://75.126.162.205

tomtomjkw · 06-16-2013, 03:27 AM

Here are the details. Maybe I'm overreacting, but there's definitely something not right:

1. Local output from my current localization (small local provider):

Quote:

tomtom@tomtom:~$ lynx --dump http://ipecho.net/plain
91.201.121.208

tomtom@tomtom:~$ ping linuxquestions.org
PING linuxquestions.org (75.126.162.205) 56(84) bytes of data.
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=1 ttl=54 time=159 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=2 ttl=54 time=161 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=3 ttl=54 time=166 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=4 ttl=54 time=171 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=5 ttl=54 time=165 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=6 ttl=54 time=161 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=7 ttl=54 time=161 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=8 ttl=54 time=163 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=9 ttl=54 time=163 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=10 ttl=54 time=168 ms
64 bytes from www.linuxquestions.org (75.126.162.205): icmp_req=11 ttl=54 time=163 ms
^C
--- linuxquestions.org ping statistics ---
12 packets transmitted, 11 received, 8% packet loss, time 11016ms
rtt min/avg/max/mdev = 159.396/164.223/171.823/3.338 ms

2. So let's ssh home (one of 3 biggest providers in Poland):

Quote:

pchlatom@serwer:~$ lynx --dump http://ipecho.net/plain
77.253.177.69

pchlatom@serwer:~$ ping linuxquestions.org
PING linuxquestions.org (75.126.162.205) 56(84) bytes of data.
^C
--- linuxquestions.org ping statistics ---
55 packets transmitted, 0 received, 100% packet loss, time 54181ms

Maybe there's some weird www blacklist that for some nonsensical reason contains linuxquestions.org and is being used by both Polish and Chinese providers?

Celyr · 06-16-2013, 05:11 AM

Can you try a traceroute?

kkady32 · 06-16-2013, 05:21 AM

I'm from Romania and last week i cannot acces LQ 3 days.I write an e-mail to LQ,give my IP.I receive an email from LQ and now is all ok.You cann try this and when problem is from LQ then this will be solved.

tomtomjkw · 06-16-2013, 05:25 AM

Traceroute from current location:

Quote:

traceroute to linuxquestions.org (75.126.162.205), 30 hops max, 60 byte packets
1 11.1.5.1 (11.1.5.1) 15.397 ms 20.266 ms 51.673 ms
2 bras.multimetro.pl (91.201.120.1) 52.426 ms 53.119 ms 55.211 ms
3 te4-2.214.ccr01.waw02.atlas.cogentco.com (149.11.6.65) 61.077 ms 89.661 ms 91.749 ms
4 te0-6-0-5.ccr21.waw01.atlas.cogentco.com (154.54.39.165) 92.816 ms te0-1-0-5.ccr21.waw01.atlas.cogentco.com (154.54.39.169) 93.896 ms te0-6-0-5.ccr21.waw01.atlas.cogentco.com (154.54.39.165) 94.964 ms
5 te0-3-1-2.ccr42.ham01.atlas.cogentco.com (154.54.73.121) 112.589 ms te0-2-1-2.ccr42.ham01.atlas.cogentco.com (154.54.56.173) 122.669 ms te0-4-1-2.ccr42.ham01.atlas.cogentco.com (154.54.60.165) 143.702 ms
6 te0-1-0-3.mpd21.ams03.atlas.cogentco.com (130.117.50.53) 147.584 ms te0-0-0-3.ccr21.ams03.atlas.cogentco.com (130.117.50.41) 40.849 ms te0-1-0-3.mpd22.ams03.atlas.cogentco.com (130.117.50.37) 32.512 ms
7 te0-1-0-0.ccr21.ams04.atlas.cogentco.com (154.54.39.110) 50.438 ms te0-1-0-3.ccr21.ams04.atlas.cogentco.com (130.117.49.10) 64.823 ms 74.322 ms
8 adm-b5-link.telia.net (80.239.128.237) 105.964 ms adm-b3-link.telia.net (213.248.85.109) 219.184 ms adm-b5-link.telia.net (80.239.160.13) 224.365 ms
9 adm-bb4-link.telia.net (213.155.130.42) 241.685 ms adm-bb3-link.telia.net (213.155.136.248) 238.367 ms adm-bb4-link.telia.net (213.155.130.42) 247.240 ms
10 prs-bb2-link.telia.net (213.155.137.161) 251.624 ms prs-bb1-link.telia.net (213.155.137.151) 253.022 ms prs-bb1-link.telia.net (213.155.137.139) 91.051 ms
11 ash-bb3-link.telia.net (80.91.251.98) 177.412 ms ash-bb3-link.telia.net (80.91.252.36) 184.974 ms ash-bb4-link.telia.net (80.91.251.247) 212.848 ms
12 ash-b1-link.telia.net (213.155.136.39) 176.687 ms ash-b1-link.telia.net (213.155.130.73) 182.036 ms ash-b1-link.telia.net (80.91.248.163) 196.032 ms
13 xe-3-0-1.bbr01.eq01.wdc02.networklayer.com (213.248.78.130) 193.854 ms 192.955 ms 196.964 ms
14 ae0.bbr01.tl01.atl01.networklayer.com (173.192.18.153) 208.037 ms 201.657 ms 212.590 ms
15 ae13.bbr02.eq01.dal03.networklayer.com (173.192.18.134) 236.803 ms 237.713 ms 240.170 ms
16 ae7.bbr01.eq01.dal03.networklayer.com (173.192.18.208) 216.549 ms ae1.dar01.sr01.dal01.networklayer.com (173.192.18.255) 223.265 ms ae7.bbr01.eq01.dal03.networklayer.com (173.192.18.208) 217.354 ms
17 po2.fcr02.sr04.dal01.networklayer.com (66.228.118.182) 228.215 ms ae0.dar01.sr01.dal01.networklayer.com (173.192.18.211) 248.711 ms po1.fcr02.sr04.dal01.networklayer.com (66.228.118.178) 224.950 ms
18 www.linuxquestions.org (75.126.162.205) 222.614 ms 233.597 ms po2.fcr02.sr04.dal01.networklayer.com (66.228.118.182) 232.584 ms

Traceroute from home:

Quote:

traceroute to linuxquestions.org (75.126.162.205), 30 hops max, 60 byte packets
1 11.1.5.1 (11.1.5.1) 0.317 ms 0.398 ms 0.465 ms
2 Jaworzno-bras2.inetia.pl (195.114.190.151) 13.782 ms 13.873 ms 16.496 ms
3 81.210.127.68 (81.210.127.68) 22.179 ms 22.368 ms 22.536 ms
4 xe-5-3-1.fra61.ip4.tinet.net (141.136.97.105) 33.688 ms 34.338 ms 35.524 ms
5 as1299.ip4.tinet.net (77.67.95.182) 38.983 ms as1299.ip4.tinet.net (77.67.67.194) 39.935 ms as1299.ip4.tinet.net (77.67.82.242) 40.899 ms
6 ffm-bb1-link.telia.net (80.91.251.249) 42.373 ms 29.964 ms 30.893 ms
7 ash-bb3-link.telia.net (213.155.135.57) 138.225 ms ash-bb3-link.telia.net (80.91.246.58) 139.957 ms 140.449 ms
8 ash-b1-link.telia.net (80.91.248.157) 140.993 ms ash-b1-link.telia.net (80.91.248.163) 142.182 ms ash-b1-link.telia.net (80.91.248.157) 143.081 ms
9 xe-3-0-1.bbr01.eq01.wdc02.networklayer.com (213.248.78.130) 144.337 ms 145.022 ms 146.211 ms
10 * * *
11 ae13.bbr02.eq01.dal03.networklayer.com (173.192.18.134) 180.998 ms 183.274 ms 182.976 ms
12 ae1.dar01.sr01.dal01.networklayer.com (173.192.18.255) 183.897 ms ae1.dar02.sr01.dal01.networklayer.com (173.192.18.213) 155.856 ms 189.974 ms
13 po1.fcr02.sr04.dal01.networklayer.com (66.228.118.178) 157.052 ms ae7.dar02.sr01.dal01.networklayer.com (66.228.118.238) 158.484 ms 189.684 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Celyr · 06-16-2013, 05:43 AM

So actually is lq provider filtering you, not the opposite

k3lt01 · 06-16-2013, 05:56 AM

Quote:

Originally Posted by kite

Well, finally. I need to visit here through tunnelling now. Nothing could be more annoying than this.

Just wondering how is this a Slackware issue?

273 · 06-16-2013, 06:08 AM

I don't think it is the country blocking this site in either case, if you haven't already I suggest a read of this thread:
http://www.linuxquestions.org/questi...xy-4175463390/

TobiSGD · 06-16-2013, 06:20 AM

We had issues with a mass attack of spammers in the near past, which led us to block certain IP ranges. If you have problems with reaching LQ and you are not blocked by your government please report that to this thread, so that Jeremy can look into it.