One year and flow offloading not work... Stick to swconfig and old releases, but thanks.
4 Likes
Hi all.
Successfully installed 21.02.3 on
- Netgear WNR3700v2 (ath79 generic)
- Netgear R6220 (mt7621)
I have / manage other devices, but I will rather install 22.03 rc1.
There is a lot of activity these days, with three versions release in a week !
Thanks to the dev team and any contributors.
On my WRT3200ACM, I tried using 21.02.3 with the exact same wireless config that has been rock solid on 21.02.2.
However, I have had constant wireless connectivity issues on 21.02.3 that I had no choice but to switch back to 21.02.2 on the other partition.
For now, I will wait for more feedback from other mwlwifi users before trying to upgrade again.
1 Like
It would be useful if these announcements flagged which changes are actually only available in the new base firmware and which are available as (i.e. opkg) updates and can be applied on top of a previous base firmware.
For example, if the three:
- wolfssl: Fix multiple security problems (CVE-2022-25638, CVE-2022-25640)
- openssl: Fix security problem (CVE-2022-0778)
- zlib: Backport security fix for a reproducible crash in compressor
were all released as opkg updates for 21.02.2, then the urgency of a full firmware upgrade to 21.02.3 is less so and that would be useful to know.
2 Likes
wifi works great on raspberry pi 4b. I used the 64bit 21.02.3 image.
There have been some ramips issue discussions recently
- D-Link DIR-2660-A1 Internet Speed
- OpenWrt on MT7621/MT7615N devices with 5GHz problems - #56 by rakantoh
Does anyone know, if some of these issues are already adressed in SR3?
Thank you. I upgraded a GL-MV1000 and a RB750Gr3. They seem to work OK (with WireGuard, adBlock, BanIP, vnStat, VPN Policy Routing).
But the IPV4 Traceroute under Network, Diagnostics, returns the following error message on the GL-MV1000 :
Error: XHR request timed out
I havent tested that on the Mikrotik yet.
Edit : it seems that this traceroute problem comes from the ProtonVPN WireGuard VPN that I have just recently started to use. Ping works but traceroute does not until the destination is finaly reached and answers.
I used image builder for Gl.Inet AR750 and 300N to include OpenVPN with this 21.02.3 version and deployed it on two test routers. I didn't find any problems, they both came right back up and reconnected their VPN connections.
I am using this snapshot OpenWrt SNAPSHOT, r19481-a5ac8ad0ba and its working fine on DIR-2660-A1 but 21.02.3 not sure.
Upgraded WAC104, no issues.
Upgraded WRT1900ACSv1, didn't come back from restart, activity LEDs out (not including LAN port LEDs). Power cycle fixed it.
J
Thank you very much to all devs and the community for 21.02.3
21.02.3 works fine on my device.
OpenWrt ist a great project! Thanks!
I did lots of upgrades, it took me about 8min. In the past the process was a few hours!
1 Like
Noticed this initially in 21.02.2, and is still happening in 21.02.3 on an Archer C7 v2 using either the CT or CT-smallbuffers drivers.
The single guest network on 5 GHz locks up on reboot.
Nothing else is active on 5 GHz.
Syslog shows the following error -
daemon.warn dnsmasq-dhcp[3573]: DHCP packet received on wlan0-1 which has no address
wlan0-1 being the guest wifi.
The network interface shows -
DEVICE_CLAIM_FAILED error where the IPv4 CIDR IP address should be.
Interestingly, I was able to track it down to channel and channel width.
The issue occurs if channel 149 or 153 is used with 40 MHz channel width.
It may occur on other channels as well.
Changing it to 20 MHz (on 149 and 153) resolved it.
Running wifi up when the channel width is set to 40 also resolves it...until the next reboot.
2 Likes
Thanks for the heads up.
Will use 19.07.10 with C7 for now.
1 Like
Hi all, installed 21.02.3 on D-Link DWR-921 with no issues.
Seems to be stable with 10h uptime. Still shows up as rev C1 but it's rev C3.
Big thanks to all contrubutors 
1 Like
Used the imagebuilder to add all my packages and configs.
From 21.02.2 to 21.02.3 on a raspberry pi 4b
|Model|Raspberry Pi 4 Model B Rev 1.2|
|Architecture|ARMv8 Processor rev 3|
|Target Platform|bcm27xx/bcm2711|
|Firmware Version|OpenWrt 21.02.3 r16554-1d4dea6d4f / LuCI openwrt-21.02 branch git-22.083.69138-0a0ce2a|
|Kernel Version|5.4.188|
No issues at all.
Same here (imagebuilder) - tplink mr200
Hi, I'm trying to install USB overlay on my TP-Link TD-W8970W (Lantiq platform).
The space is very limited but previously I was able to install USB flashdisk support on version 21.02.1.
Following the openwrt guide for extroot_configuration command
opkg install block-mount kmod-fs-ext4 e2fsprogs
finished OK. I omitted fdisk package because there is not enough space left on device.
On the flashdisk system and swap partitions are already prepared so I don't need fdisk package.
The problem is that after reboot I don't see any /dev/sda* devices and "block info" won't show the USB partitions. Is this a bug, or the fdisk package is required now?
Thanks a lot for help.
Hi,
I've been looking at the discussions in the flow offloading threads, and I was encouraged by the latest here, although I don't understand everything 100%. It sounded like it was finally solved though: https://github.com/openwrt/openwrt/pull/4849
Can you please prioritize reviewing/testing those fixes for the next release? With fiber coming in my area, and many others, performance is becoming more and more important. I would bet a lot of people are still running 19.x because of this issue alone, and it's now been about a year.
I know it's a volunteer project, and I'm sorry I don't have enough knowledge to contribute myself, but for me this functionality is very important.
Thanks
Upgraded my WR1300, no issues so far
Upgraded my 2xR7800 and a E4200V2 (not using Wifi from that) from 21.02.2 with keep settings, no issues so far.
Keep up the good work devs!