DL-WRX36 on 24.10.0 cant 'opkg update'

I've got my DL-WRX36 onto the 24.10.0 release. All seemed to be working, but I just tried to issue 'opkg update' as a precursor to adding some extra packages, and I get:

root@router.dev.lan:~# opkg update
Downloading https://downloads.openwrt.org/releases/24.10.0/targets/qualcommax/ipq807x/packages/Packages.gz
SSL error: NET - Sending information through the socket failed
*** Failed to download the package list from https://downloads.openwrt.org/releases/24.10.0/targets/qualcommax/ipq807x/packages/Packages.gz

The same error is repeated for each feed, and each feed takes many seconds to fail. But I can ping the download server, so I think I do have basic connectivity working:

root@router.dev.lan:~# ping downloads.openwrt.org
PING downloads.openwrt.org (146.75.74.132): 56 data bytes
64 bytes from 146.75.74.132: seq=0 ttl=57 time=49.255 ms
64 bytes from 146.75.74.132: seq=1 ttl=57 time=40.199 ms
64 bytes from 146.75.74.132: seq=2 ttl=57 time=40.025 ms
64 bytes from 146.75.74.132: seq=3 ttl=57 time=39.367 ms
^C
--- downloads.openwrt.org ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 39.367/42.211/49.255 ms

So I attempted to wget the package file instead:

root@router.dev.lan:~# wget -vvv https://downloads.openwrt.org/releases/24.10.0/targets/qualcommax/ipq807x/packages/Packages.gz
Downloading 'https://downloads.openwrt.org/releases/24.10.0/targets/qualcommax/ipq807x/packages/Packages.gz'
Connecting to 151.101.190.132:443
SSL error: NET - Sending information through the socket failed
Connection error: Connection failed

And got a very similar message about an "SSL error", so I tried downloading a random HTTP page from the Internet (which took some finding, but shouldn't require the use of SSL):

root@router.dev.lan:~# wget -vvv http://www.communitycomposting.ca/index.phtml
Downloading 'http://www.communitycomposting.ca/index.phtml'
Connecting to 216.251.32.98:80
Connection error: Connection timed out

So. Not a problem with SSL, per se, but an actual routing problem?
This is confusing though, because this router is connected to the Internet with an RNDIS modem, and establishes a wireguard site-to-site link, over which I administer the router. And that wireguard tunnel is working just fine. Indeed, if I wget a file from a host on the other (my) side of the wg tunnel to the DL-WRX36, it works perfectly:

root@router.dev.lan:/~# wget http://house.war.lan/index.php
Downloading 'http://house.war.lan/index.php'
Connecting to 192.168.252.20:80
Writing to 'index.php'

Download completed (19772 bytes)

Here's the routing table (with the tunnel up, obviously):

root@router.dev.lan:/tmp# route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
81.187.30.0     0.0.0.0         255.255.255.0   U     0      0        0 site2site
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.43.0    0.0.0.0         255.255.255.0   U     0      0        0 br-lan
192.168.100.0   0.0.0.0         255.255.255.252 U     0      0        0 site2site
192.168.100.1   0.0.0.0         255.255.255.255 UH    0      0        0 site2site
192.168.155.0   0.0.0.0         255.255.255.0   U     0      0        0 site2site
192.168.252.0   0.0.0.0         255.255.252.0   U     0      0        0 site2site
212.159.xx.xx   192.168.1.1     255.255.255.255 UGH   0      0        0 eth0

Which all looks pretty much as I'd expect.

Meanwhile, my "user" at the remote site is telling me that their internet isn't working. So this isn't just affecting the router itself, but any device connected to it too.

At this point I'm out of ideas. I retained this (previously working) configuration across the install of 24.10.0, only changing the RNDIS device name in the interface definition to match the changed device name returned by the 24.10.0 version of kmod-usb-net-rndis so I'm struggling to understand what has changed to suddenly stop this from working.

Suggestions gratefully received.

This morning, everything is working perfectly. :scream:

I've been through the configuration again, and I still can't see any issues with the router configuration. I've just rebooted, and everything continues to run properly. I have no root cause for the problems of yesterday, or why everything is now working perfectly today. Or why my wireguard tunnel worked perfectly the whole time...

Unless... maybe, there was a problem in the ISP network that affected TCP but not UDP traffic. Which feels like a bit of a reach, to be honest. So for now, I'm crossing my fingers, and continuing to monitor the situation.

Perhaps the downloads server was down...

1 Like

I don't think so in this case, because I was able to download the Package file etc with my laptop (on a different ISP), and I also wasn't able to download content from other websites to the DL-WRX36 either. It was definitely something related to either the DL-WRX36, or it's connection to the Internet. Given it's working again now (and I've still made no changes), I'm minded to think there was a transitory problem with the ISP network.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.