firewall4 is meant to replace firewall in this release. If you have already migrated, that's great and what everyone should do, if possible. However, be aware that at this moment, some things (such as mwan3 or banip) still don't work. See https://github.com/openwrt/packages/issues/16818
3 Likes
I see what you mean. I confirmed using serial console how to switch from master to slave boot.
The first method is to flash using the stock firmware and it will switch on the reboot.
The second is to power cycle the router to force the switch. Sometimes it will switch from the master to the slave boot on the first or second attempt. Check if it hasn't switched yet by opening the stock firmware page in a browser.
It always switches on the third attempt.
Evidently the non-ubi images should not be flashed currently. Not much is functional in the kernel image for trying out OpenWrt and using it to flash the sysupgrade image resulted in a boot failure with my RT3200.
Somehow I appear to have screwed up the ubi install too. Presumably I flashed the recovery ubi image twice instead of the recovery-installer ubi image the second time but will try again soon using the serial console.
1 Like
Can I just say I am so sorry. Once set up this is a fantastic router and I hope you get this resolved very soon.
3 Likes
Thx for the advise, Daniel. Actually I got it working. I tried powercycling several times, but what worked was just to type reboot using SSH. Afterwards I could flash the installer image. Great work.
Unfortunately I ran into another issue. Just wanted to install OpenVPN and got the following error message.
cannot find dependency kernel (= 5.10.90-1-200597be5decdb54cc9b83cba4aad31e) for kmod-tun
Hope there is a solution for that as this is one of major use case.
1 Like
donwload auc
in putty put auc and wait sysupgrade then you can use the vpn normally
3 Likes
How do we migrate to firewall4 from firewall, it owuld be great to post the step for some of us that are still behind. Thank you.
1 Like
I am waiting on 408 to get published, how much longer>?
1 Like
I would suggest to take the fw4 discussions, including package installability, to a new, dedicated topic - it's not specific to this device at all, but the same for all OpenWrt devices.
The switch between fw3 to fw4 is happening mostly behind the scenes, /etc/config/firewall is the same between both, fw3/ fw4 both take this as input and generate the matching iptables vs nftables configurations out of that. Things where some thought might be needed, are /etc/firewall.user or manual iptables calls, as well as (non-default) addon package that hook in deeply into fw3 internals and will need porting to fw4 (e.g. mwan3, banip, but also others).
2 Likes
ok i will create a subject or openwrt ninja if he want for our because i'm interested too , thanks
subject create
here
2 Likes
EDIT: Restoring mtd5 then factory reset was enough and now I have successfully installed UBI OpenWrt!
Thanks daniel.
I used serial console option 2 to flash FW_RT3200_1.0.01.101415_prod.img which allowed it to successfully boot again.
When I load the stock firmware page it says it's a Linksys AX3200 Gigabit WiFi Router E8420. 
Currently mtd5 contains only sw_version=1.0.0.1.
Would a stock firmware factory reset after flashing a mtd5 backup be enough for another attempt at installing UBI OpenWrt?
1 Like
What will happen with respect to the installer when the RT3200 becomes supported by an official OpenWrt release? Presumably individuals will all be on different installer versions. And are we getting nearer to official support?
4 Likes
Sorry to add one more question to the pool...
Has been solved the problem with the firewall module?
Should I sysupgrade my router that has been flashed a couple of weeks ago ( OpenWrt SNAPSHOT r18437-92820cc5b9 / LuCI firewall4 branch git-21.357.58153-63d9bcb) in order to get possible bugs fixed,or should I wait some more time?
It seems my version has already firewall4 installed, if version description is correct.
I am having some problems activating fast transition 802.11r and management fram protection 802.11w in some android device (android 10 at least).
Some other old windows laptops with wifi can't connect either.
I don't think it is a specific model problem, but it seems that nobody has the same problem here.
I would like to upgrade to see if it has been solved, but don't want to break the router config that now is working OK, if there are still problems with the firewall.
Yes. A fix has been applied and the buildbot has compiled images containing it over night. Everything is back to how it was in that regard, so further intervention needed what-so-ever.
You can just go ahead, there is afaik no reason to wait at this moment.
The problems you are describing sound more like client-side issues which may be solved by updating the wifi drivers/firmware (or Android ROM) on the client.
3 Likes
May be, I had problems with a windows machine (surface 3) not able to connect that were solve finding a proper driver upgrade (not an easy task).
But Android devices cannot just upgrade the wifi driver you only have firmware upgrades, and manufactures abandoned your devices short after being launched.
That is why I don't lke Android at all nor google's way of doing things.
In the case of the windows machines the have problems connecting to the wifi even with no managemen frame protection or fast transitions.
In the case of android new devices (Android 11) won't connect if you do not activate 802.11w at least as optional, and other ones (android 10) won't connect if you have 802.11r and 802.11w optional at the same time.
So I had to disable fast transitions at all.
Thank you for your answer, I will shortly sysupgrade my router.
The buildbot has completed now so that you can now use either auc on the command line or System -> Attended Sysupgrade in LuCI Web-UI to upgrade to the most recent snapshot. Then you should be able to install also all kernel modules needed, e.g. for OpenVPN.
2 Likes
I will update the installer to use the released ImageBuilder instead of picking the current snapshot build.
However, everybody already on the UBI layout can of course just sysupgrade to the release images, no need to run the installer again.
People having used different versions of the installer (all above v0.5.3) is ok in terms of being able to just sysupgrade to the upcoming 22.xx OpenWrt release. And yes, as all targets have arrived on Linux 5.10, we are going to branch-off for the release very soon.
7 Likes
Wel I have sysupgraded to the recent snapshot.
No problems detected for now.
Great to know we are close to be integrated in general master branch.
How do we know the version of the installer we have?
It does no seem to show anywhere in the interface...
If you enter into the recovery image (various methods - I used to end up there when the router crashed, not so much recently) you can check the OpenWRT release string and compare with the releases page.
1 Like
The installer itself doesn't leave a version anywhere on the system. You can, however, check the version of U-Boot which created the environment on first-boot, which is hence the version which came with the installer:
fw_printenv ver
To update the recovery image written by the installer, first make sure you have a working production system (to have a fall-back in case something goes wrong). Note that you will loose all configuration as the new recovery image may need more space as the old one and hence rootfs_data needs to be removed during the procedure (it is re-created by U-Boot on reboot).
Boot into recovery and do this:
cd /tmp
wget https://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/openwrt-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery.itb
ubirmvol /dev/ubi0 -N recovery
ubirmvol /dev/ubi0 -N rootfs_data
ubimkvol /dev/ubi0 -N recovery -s $(cat openwrt-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery.itb | wc -c)
ubiupdatevol /dev/ubi0_2 openwrt-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery.itb
reboot
If you really want to update U-Boot and/or TF-A, you can do so with the serial console attached (there are options for updating in the boot menu) or by writing it using mtd and kmod-mtd-rw. There is no fallback, so if something goes wrong, you have to connect JTAG and have fun with OpenOCD.
insmod mtd-rw i_want_a_brick=1
# to update bl2/Preloader (should never be needed unless you wanna switch to home-brew secure-boot system ;)
cd /tmp
wget https://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/openwrt-mediatek-mt7622-linksys_e8450-ubi-preloader.bin
mtd write openwrt-mediatek-mt7622-linksys_e8450-ubi-preloader.bin /dev/mtd0
# to update U-Boot and ARM Trusted Firmware BL31
cd /tmp
wget https://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/openwrt-mediatek-mt7622-linksys_e8450-ubi-bl31-uboot.fip
mtd write openwrt-mediatek-mt7622-linksys_e8450-ubi-bl31-uboot.fip /dev/mtd1
# clear ubootenv and ubootenv2 UBI volumes, so environment is re-created by updated U-Boot
ubiupdatevol -t /dev/ubi0_0
ubiupdatevol -t /dev/ubi0_1
reboot
Do not re-run the installer, as you will loose your backups of the vendor bootchain.
6 Likes
I am having an issue running the latest SS and downloading packages, I keep getting the following error upon refreshing the pkg list via GUI:
Collected errors:
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/packages/Packages.gz, wget returned 5.
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/base/Packages.gz, wget returned 5.
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/targets/mediatek/mt7622/kmods/5.10.90-1-200597be5decdb54cc9b83cba4aad31e/Packages.gz, wget returned 5.
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/luci/Packages.gz, wget returned 5.
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/packages/Packages.gz, wget returned 5.
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/routing/Packages.gz, wget returned 5.
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/telephony/Packages.gz, wget returned 5.