Git.openwrt.org closed to Russians?


#1
$ git clone https://git.openwrt.org/openwrt/openwrt.git
Клонирование в «openwrt»…
fatal: unable to access 'https://git.openwrt.org/openwrt/openwrt.git/': Failed to connect to git.openwrt.org port 443: Время ожидания соединения истекло

$ torsocks git clone https://git.openwrt.org/openwrt/openwrt.git
Клонирование в «openwrt»…
remote: Enumerating objects: 456955, done.
remote: Counting objects: 100% (456955/456955), done.
remote: Compressing objects: 100% (125680/125680), done.
remote: Total 456955 (delta 315779), reused 451672 (delta 311897)


#2

Alternatively you can use GitHub
git clone https://github.com/openwrt/openwrt.git


#3

I think you may provide output of the following commands to help others further diagnose the problem.

traceroute -n git.openwrt.org

#4
./scripts/feeds update -a

call to git.openwrt.org


#5
$ traceroute -n git.openwrt.org
traceroute to git.openwrt.org (46.101.214.210), 30 hops max, 60 byte packets
 1  195.74.82.12  0.659 ms  1.245 ms  1.500 ms
 2  172.16.21.11  0.376 ms  0.371 ms  0.368 ms
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


#6


You can easily also include the telephony package repo the same way if you want
I personally don't see it as issue to "outsorcing" it GitHub but some have a strong opinions about it.


#7

From other provider:

$ traceroute -n git.openwrt.org
traceroute to git.openwrt.org (46.101.214.210), 30 hops max, 60 byte packets
 1  192.168.10.1  1.298 ms  1.864 ms  2.347 ms
 2  100.83.255.144  26.557 ms  28.697 ms  29.111 ms
 3  100.64.4.2  36.155 ms  37.622 ms  41.112 ms
 4  213.59.211.237  39.165 ms  42.560 ms  44.023 ms
 5  62.115.151.97  96.330 ms  96.614 ms  100.821 ms
 6  62.115.151.96  103.886 ms  105.104 ms  107.113 ms
 7  62.115.121.10  89.477 ms 62.115.137.166  93.743 ms 62.115.116.161  77.147 ms
 8  62.115.120.6  94.171 ms  89.982 ms 62.115.120.0  75.247 ms
 9  80.239.128.23  77.884 ms  78.505 ms 80.239.128.21  99.800 ms
10  * * *
11  46.101.214.210  67.881 ms  64.972 ms  64.832 ms

but

$ git clone https://git.openwrt.org/openwrt/openwrt.git
Клонирование в «openwrt»…
fatal: unable to access 'https://git.openwrt.org/openwrt/openwrt.git/': Failed to connect to git.openwrt.org port 443: Время ожидания соединения истекло


#8

I think I saw someone from Russia having the same problem a while ago. Maybe it shares IP(-range) with someone Putin doesn't like. You could try https://github.com/openwrt/openwrt instead, but I don't know if you can get the feeds that way.


#9

Thanks! By this way - it works.


#10

There's internet censorship in Russia.
They use DNS/IP-based content-filtering.
To override it you should utilize VPN/Tor/etc.


#11

This post was flagged by the community and is temporarily hidden.


#12

46.101.214.210 blocked in censorship war against Telegram. You can check in here — blocklist.rkn.gov.ru.


#13

I can confirm this. I wrote to authorities and received a reply that only site maintainers can apply for unblocking. Block was related to Telegram ban.

github is not always a solution, because some projects located at git.openwrt.org are needed to be downloaded at times. Not only feeds and luci that are also available at github.

It is easy to workaround by using IPv6, vpn, proxy or other ways.

But maybe somebody can write to RKN to unblock the address? If there is nothing Telegram related on that IP, they'll unblock it.


#14

Maybe @thess can help?


#15

The problem is that there is a court decision regarding that IP, how stupid it may sound.
They need a letter from the domain owner to start the revert process.

I am a lawyer and if any help is needed, I can provide.

Although it is a stupid and annoying problem.


#16

openwrt.org is owned by SPI (Software in the Public Interest). Someone from there or perhaps @blogic would be the ones to handle that request.


#17

@Pilot6
..or mirror all repos as read-only?


#18

What do you mean? If they could be mirrored from another IP, that would be a great solution.
Just one redirection from somewhere not banned.


#19

The whole government censorship system is completely idiotic and ridiculous.
Incorrect blocking of some addresses and even subnets is common.
It happens every now and then and has been going on for several years already.
You can try to fight it, but you can't fight for all the incorrectly blocked resources.
Leaving aside that "blocked incorrectly" is an oxymoron, because censorship is evil by itself.


#20

I doubt that a specific address can be unblocked because the entire subnet was blocked.