Hello!
I have a router TP-Link Archer MR200 v1. It was running OpenWrt 19.07.4 and everything was ok. I could connect through lan or wifi to the (lte) internet.
Now I upgraded OpenWrt to 24.10.0 and can not connect to the internet. Wifi and lan is ok and I can connect to the OpenWrt UI at 192.168.1.1.
Maybe I need to configure something for the lte modem to work? What should I try?
BR
Fido
Now I tried to downgrade back to 19.07.4 using openwrt-19.07.4-ramips-mt7620-ArcherMR200-squashfs-sysupgrade.bin, but getting this scary popup that image is not compatible
https://openwrt.org/docs/guide-user/network/wan/wwan/ltedongle
but the modem won't magically start working after you've downgraded, same config have to be done there too.
Not really scary, because you know , that the image you want to flash worked in the past, because compatible with your device. The sysupgrade-process/-utility had several changes during openwrts version history. And changes of behaviour, unfortunately. Anyway, there is the "-F" option in your actual sysupgrade utility, when used from CLI, which forces the flash process, bypassing the checks leading to your actual LuCI warning.
Thus, in your case, switch the working dir to /tmp, first.
then download something like openwrt-19.07.4-ramips-mt7620-ArcherMR200-squashfs-sysupgrade.bin to fw.bin, and the sysupgrade -F -n -v fw.bin . Your downgrade is quite a few versions, thus, it might be a good idea to do it in several steps, first down to 23.x, then 22.xxx, 21.xx, then 19.07 . This process still has some small risks, though. Because of next post in this thread, you might have found a bug in the 24.0 release for your device, as it worked with 23.05 . May be, first to try flashing the 23.05 image. Which MIGHT not generate the scary error msg.
I have this device but retired it a few months ago with 23.05.
It's not using any 3/4G protocol - all the stuff is done in embedded modem OS (some android) - it's exposing the wan as a usb0 interface as a simple dhcp client (so double nat - maybe more considering ISP one)
Indeed it is probably a bug in the 24.10.0. As per your instructions I downgraded to 23.05.5 and it works like a charm, right out of the box.
Thank you guys for your help!
although I intend to sell the device maybe I'll test the 24.10 and hopefully find more about the bug/a fix/workaround soon.
There were some changes to the device name hueristic in mainline linux recently, causing renames from usbX to ethX. This was also backported to v6.6 stable. Maybe that's the problem here?
I can confirm the nic name change:
[ 20.615968] rndis_host 1-1:1.0 eth1: register 'rndis_host' at usb-101c0000.ehci-1, RNDIS device, b1:aa:b1:aa:b1:aa
I'm trying to fix this and push a patch.
usbX to ethX issue fixed by https://github.com/openwrt/openwrt/pull/17757. Fix will be there once 24.10.1 is released
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.