OpenWrt SNAPSHOT r22302 on MR8300

ivpatrick · March 22, 2023, 4:25pm

Hi @clauded @badulesia
I am having the same problem on my MR8300 too on the last few snapshot builds too. I tried this over a period of 4-5 days and finally filed a bug report. Thats the one mentioned in this thread too.

github.com/openwrt/openwrt

snapshot builds do not install correctly - Mar 2023 builds

opened 09:28AM - 21 Mar 23 UTC

infantvin

bug

### Describe the bug I am flashing the snapshot build using the LUCI GUI on my …MR8300 and whenever the flash is done, the router does not boot. In fact, it never reboots post the flash. I have waited for more than 5-10 minutes in cases and found that the router never responds. I have to turn off power 3 times to get back to the previous firmware that was installed. This means that whatever version is being installed does not work. I am not sure what logs need to be collected to help you analyze the issue, but if you need please send me information on how to gather this and I will send it across to you. All snapshot builds are downloaded from here https://downloads.openwrt.org/snapshots/targets/ipq40xx/generic/ File name is linksys_mr8300-squashfs-sysupgrade.bin I have tried with the files since Mar 18 until Mar 21 2023 and faced the same problem with all of them. Thanks. ### OpenWrt version NA as the router cannot be reached post the flash ### OpenWrt target/subtarget ipq40xx/generic ### Device Linksys MR8300 (Dallas) ### Image kind Official downloaded image ### Steps to reproduce Run a MR8300 with any existing openwrt image from say Feb or so and then flash using the snapshot images from any day from Mar 18 until today. Router will not boot and the wired connection from the PC to the router will keep saying its trying to connect and fails. This can happen indefinitely and does not correct over time. ### Actual behaviour orange LED flashes signifying that the flash is happening. However, the router never reboots like it is supposed to and it just stays with the blue LED steady and does not respond to pings to the 192.168.1.1 address. DHCP assignment to a wired device will fail as the device will fail to reach the router which indicates that its not responding. ### Expected behaviour Normally, the image flash will cause the router to reboot, the blue LED to blink and then it becomes steady indicating the router has booted. The pings to 192.168.1.1 should be successful. ### Additional info Please let me know if you need anything. I can get it for you. However the flash itself has failed and I cannot reach the router when this issue happens, so I really dont know what information to gather and give to you. ### Diffconfig _No response_ ### Terms - [X] I am reporting an issue for OpenWrt, not an unsupported fork.

According to the issue mentioned above, it looks like some nftables related issue. You can read through it.