Note - I do not believe this is related to the current build queue issue as I haven't been able to reach the server at all for months.
All my traffic to sysupgrade.openwrt.org seems to be getting blocked. The name resolves to asu-02.infra.openwrt.org [45.140.183.87] for me, which I believe is correct. However nothing loads it just times out, both on my router and from any systems behind my router. This started around the time the 24.10 releases became available. A traceroute indicates traffic is getting as far as gw0.scc.kae.bb.vzffnrmo.de [45.140.183.69] and then it just gets discarded.
If I use my cell phone to open the page, or visit a friend's house who uses a different ISP, the page loads just fine, so it's my public IP that seems to be the problem. I am with a small Canadian residential ISP who has given me an address in the 45.44.69.x range and I don't know why blocking this range would be necessary. It used to work.
Can anyone contact the admins and get my address unblocked?
I got an error earlier as well. I didn't try traceroute, but I do think that this is related to the general problems facing the sysupgrade server. My guess is that the server is still having issues and that your IP is not blocked. However, I don't administer that server, so I cannot say with certainty.
tracert sysupgrade.openwrt.org
Tracing route to asu-02.infra.openwrt.org [45.140.183.87]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [local router ip]
2 9 ms 10 ms 9 ms 96.49.192.1
3 * * * Request timed out.
4 13 ms 10 ms 10 ms rc1st-be5.vc.shawcable.net [66.163.69.98]
5 10 ms 11 ms 17 ms 177.103.44.45.in-addr.arpa [45.44.103.177]
6 20 ms 12 ms 12 ms 81.104.44.45.in-addr.arpa [45.44.104.81]
7 14 ms 14 ms 14 ms van-b2-link.ip.twelve99.net [213.248.92.222]
8 14 ms 15 ms 13 ms sea-b1-link.ip.twelve99.net [62.115.138.38]
9 * 59 ms 59 ms chi-bb2-link.ip.twelve99.net [62.115.132.154]
10 * * * Request timed out.
11 146 ms 144 ms 143 ms ldn-bb2-link.ip.twelve99.net [62.115.139.247]
12 150 ms 149 ms 151 ms prs-bb2-link.ip.twelve99.net [62.115.133.239]
13 157 ms 154 ms 157 ms ffm-bb2-link.ip.twelve99.net [62.115.122.139]
14 157 ms 155 ms 155 ms ffm-b5-link.ip.twelve99.net [62.115.136.219]
15 158 ms 164 ms 160 ms universitt-ic-349246.ip.twelve99-cust.net [213.248.88.26]
16 159 ms 159 ms 160 ms stu-eti-a99-hu0-4-0-7.belwue.net [129.143.60.112]
17 162 ms 161 ms 160 ms kar-rz-a99-hu0-2-0-4.belwue.net [129.143.56.28]
18 * * * Request timed out.
19 * * * Request timed out.
20 160 ms 162 ms 163 ms gw0.scc.kae.bb.vzffnrmo.de [45.140.183.69]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Keep in mind that not all hops in a traceroute will respond. But I think that the lack of a ping response to the asu server is indeed indicative of an issue... at least at first glance.
No it did not actually. Just this weekend I finally got my PBR setup so that I redirect all sysupgrade.openwrt.org destined traffic through a VPS I have a wireguard tunnel on. Works great when using the VPS' routes.
I'll try to get a fresh capture of a traceroute tomorrow and post it. Interesting others are seeing this too. I did always find it strange that somehow I was the only one experiencing this out of all of the people on the internet which also clearly indicated that data leaves my router fine. Somewhere out in the internet ether something is wrong though.
Ah now you've given me an idea. I too happen to have a WireGuard VPN set up to a friend's house. When I configure PBR to route all traffic to sysupgrade.openwrt.org over the VPN, it works!
tracert sysupgrade.openwrt.org
Tracing route to asu-02.infra.openwrt.org [45.140.183.87]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms [local router IP]
2 27 ms 26 ms 26 ms [WireGuard VPN]
3 27 ms 28 ms 27 ms [remote router IP]
4 36 ms 35 ms 35 ms 50.68.224.1
5 36 ms 37 ms 34 ms rc1st-be106-1.vc.shawcable.net [64.59.151.141]
6 42 ms 35 ms 35 ms 24.244.60.13
7 36 ms 41 ms 35 ms 24.83.252.66
8 * 37 ms * 24.83.250.1
9 42 ms 41 ms 42 ms rc2wt-be50-1.wa.shawcable.net [66.163.70.106]
10 83 ms 63 ms 63 ms rc1wt-be18-1.wa.shawcable.net [66.163.64.81]
11 * 42 ms * sea-b1-link.ip.twelve99.net [213.248.67.224]
12 84 ms 84 ms * chi-bb2-link.ip.twelve99.net [62.115.132.154]
13 * * * Request timed out.
14 173 ms 171 ms 171 ms ldn-bb2-link.ip.twelve99.net [62.115.139.247]
15 192 ms 179 ms 174 ms prs-bb2-link.ip.twelve99.net [62.115.133.239]
16 191 ms 186 ms 181 ms ffm-bb2-link.ip.twelve99.net [62.115.122.139]
17 183 ms 182 ms 182 ms ffm-b5-link.ip.twelve99.net [62.115.114.91]
18 182 ms 182 ms 183 ms universitt-ic-349246.ip.twelve99-cust.net [213.248.88.26]
19 189 ms 190 ms 190 ms stu-eti-a99-hu0-4-0-11.belwue.net [129.143.57.126]
20 193 ms 195 ms 202 ms kar-rz-a99-hu0-1-0-0.belwue.net [129.143.60.77]
21 * * * Request timed out.
22 * * * Request timed out.
23 191 ms 193 ms 190 ms gw0.scc.kae.bb.vzffnrmo.de [45.140.183.69]
24 201 ms 199 ms 196 ms sysupgrade.openwrt.org [45.140.183.87]
Trace complete.
It's an ugly hack but I'll take it
One possibly relevant thing to note - it appears from this trace and my earlier trace that both of us are using shawcable.net as our ISP while theirs works and mine doesn't. This is only partially correct - in my case I am paying a 3rd party ISP who subcontracts the connection back to Shaw where as my friend buys their service from Shaw directly. I think this means I get my public IP assigned from a different block than direct customers.
Well I am afraid that the traceroute from my VPS' wireguard tunnel is less than helpful since apparently my VPS provider doesn't return traceroute info.
As for the local route using my AT&T ISP router, here is the current traceroute for that:
However, mine just bounces around after that same hop endlessly. Same error returned in a browser when I navigate to https://sysupgrade.openwrt.org (connection reset)
My VPS route returns pages in a browser and pings exactly as I would expect.
Here's curl output from a linux machine I have routing through the non-working AT&T route:
**user@pi4**:**~**$ curl -v -4 https://sysupgrade.openwrt.org
* Host sysupgrade.openwrt.org:443 was resolved.
* IPv6: (none)
* IPv4: 45.140.183.87
* Trying 45.140.183.87:443...
* connect to 45.140.183.87 port 443 from x.x.x.5 port 47436 failed: Connection timed out
* Failed to connect to sysupgrade.openwrt.org port 443 after 135450 ms: Couldn't connect to server
* Closing connection
curl: (28) Failed to connect to sysupgrade.openwrt.org port 443 after 135450 ms: Couldn't connect to server
Unfortunately the only other GUI based machine I have is an "Always on VPN" machine that won't route through that connection so I can't get a tcpdump of that particular error in the browser.
