Good evening to all,
I've a MR8300 (fw 1.1.10.210186 MR8300v1.1) and the "short" question: I'm trying to install openwrt-23.05.4-ipq40xx-generic-linksys_mr8300-squashfs-factory.bin from OEM GUI (from wiki for my device https://openwrt.org/toh/linksys/mr8300 I'm at "Second step"... already set the correct parameter for the boot...) because I would like to maintain for some time the OEM GUI that's already setup. But when I come back to OEM and flash a 23.05 my device come back but I cannot access to luci (192.168.1.1, nor any other ip that I set before the change with the 22.03.7 fw).
Is it possible flahs with OEM or I need to follow another guide?
Now, I was able to come back with the Recovery Automatic... How can I continue?
Your English is a bit hard to understand, but I guess this could exactly be your issue:
the doc on https://openwrt.org/toh/linksys/mr8300 is clear about this: you cannot install 23.05 on mr8300 directly from the vendor OEM firmware.
Due to mr8300 oddities, you need to install 22.05.x first and then sysupgrade to 23.05.x (meaning you boot into OpenWRT 22 and the use the v22 OpenWRT flash firmware menu to upgrade to 23) . And you are right, this second sysupgrade step will overwrite the other OEM partition, removing your OEM fallback partition. You will end up with OpenWRT v22 in one and v23 in the other partition.
But the doc of this particular mr8300 also says: "Since 22.03.3, OpenWrt has the ability to flash an OEM firmware image, that would restore the router to its original state."
I dont own the device, but I see no reason to not rely on this fallback option.
(Maybe you are "lucky" on top, as some dual partition devices recently had a bug that would sysupgrade into the same partition, as their switch partition mechanism was faulty)
yes, sorry I copied and paste and then didn't check the phrase...
I try to be more precise.
I already followed the guide for mr8300, so on 1 partition I have the original OEM GUI and in the other I tried to flash the 2 fws: starting flashing the 22.03 from OEM GUI, device rebooted and I was able to connect to Luci/ssh to 192.168.1.1, then I made a couple of modify: change the memory for the boot and changed the IP address of the device (set to 192.168.2.1 i. e.), rebooted again into v22 and checked that everything was fine (I could connect to Luci and ssh).
Then I went back to OEM GUI.
Here I started to flash the v23 but after a couple of minutes I try to connect to 192.168.2.1 but I'd didn't work, I try also 192.168.1.1 but same result... (obviously I changed IP address of desktop) I cannot also ping both IP address... flashing v23 I suppose that erase the previously configuration, so also the IP assigned.
I won't be of huge help, as I do not have the device.
I can only try helping to interpret the wiki page.
You wrote about boot memory, did you mean the part about "kernsize 500000"?
Is that parameter still present after setting it and rebooting v22? Maybe you have a typo in this part somewhere? As to me it sounds like a oroblem that could be related to this.
Also note that you have posted the URLs of the firmware bin files of v22.03.7 twice. This way we can't tell if you have picked the correct download for v23.
Kernsize was correct, I taken a screenshot after the reboot:
and the files were also good, my mistake was try to copy and paste via smartphone... too small the display, these are the files:
but probably I found the culprit...
fortunately I screenshoted completely the ssh konsole after the reboot for the parameter:
serverip=192.168.1.254
I don't know where it found this ip... it seems to have only changed the third octet,
Quite strange.
I'll try as soon as possible, probably It's necessary only flash again the v23 from OEM GUI... just to make change the partition at reboot. I hope
ok, found a couple of issue: it took the 192.168.1.1 but it also the ip of the modem attached to wlan port, and probably some confusing configuration on the enp2s0 network on my pc (wrong gateway).
Now I'm continuing with mac address filter and wireguard...
Thanks
Hi.
There is also something very simple to consider : the browser cache. At reboot, if you try to browse 192.168.1.1, the browser will redirect to a linksys page that doesn't exist anymore as you are on OpenWrt. Shuflle the cache or use a private seesion in the browser.
