OpenWrt 22.03.0-rc1 first release candidate

Used the imagebuilder to add all my packages and configs.

From 21.02.3 to 22.03.0-rc1 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 22.03.0-rc1 r19302-df622768da / LuCI openwrt-22.03 branch git-22.119.37115-66994a5|
|Kernel Version|5.10.111|

No issues at all. (not using WiFi)

Is there a nft-to-iptables-wrapper binary?
Like the iptabltes-to-nft one?

I'm not going to switch to nftables soon.
And some packages start to completely remove iptables support.

1 Like

The rc2 thread isn't up yet, but I tried building it and ran into a problem:

rfc1035.c: In function 'report_addresses':
rfc1035.c:1047:56: error: 'struct dnsmasq_daemon' has no member named 'workspacename'
 1047 |               if (!extract_name(header, len, &p, daemon->workspacename, 1, 0))
      |                                                        ^~
rfc1035.c:1049:66: error: 'struct dnsmasq_daemon' has no member named 'workspacename'
 1049 |               if (safe_name(daemon->namebuff) && safe_name(daemon->workspacename))
      |                                                                  ^~
rfc1035.c:1050:92: error: 'struct dnsmasq_daemon' has no member named 'workspacename'
 1050 | _event_bcast_connmark_allowlist_resolved(mark, daemon->namebuff, daemon->workspacename, attl);
      |                                                                        ^~

make[5]: *** [/home/barrakketh/ow/openwrt/build_dir/target-mips_24kc_musl/dnsmasq-full/dnsmasq-2.86/Makefile:166: rfc1035.o] Error 1
make[5]: Leaving directory '/home/barrakketh/ow/openwrt/build_dir/target-mips_24kc_musl/dnsmasq-full/dnsmasq-2.86/src'
make[4]: *** [Makefile:91: all] Error 2
make[4]: Leaving directory '/home/barrakketh/ow/openwrt/build_dir/target-mips_24kc_musl/dnsmasq-full/dnsmasq-2.86'
make[3]: *** [Makefile:200: /home/barrakketh/ow/openwrt/build_dir/target-mips_24kc_musl/dnsmasq-full/dnsmasq-2.86/.built] Error 2
make[3]: Leaving directory '/home/barrakketh/ow/openwrt/package/network/services/dnsmasq'
time: package/network/services/dnsmasq/full/compile#0.50#0.12#0.54
    ERROR: package/network/services/dnsmasq failed to build (build variant: full).
make[2]: *** [package/Makefile:116: package/network/services/dnsmasq/compile] Error 1
make[2]: Leaving directory '/home/barrakketh/ow/openwrt'
make[1]: *** [package/Makefile:110: /home/barrakketh/ow/openwrt/staging_dir/target-mips_24kc_musl/stamp/.package_compile] Error 2

There's an existing bug report that was migrated over to Github about the issue that has a link to the discussion about it and a patch since it's a dnsmasq bug.

1 Like

hello
I installed on TL-WDR3600 I had problems with the installation of opkg, it did not install and indicated that the partitions were blocked which was read-only

I reverted to the previous version

Hi all.
I have built and installed 22.03.0.rc2 on a R6220 (mt7621).
If you notice, factory and sysupgrade files have a release number, like a snapshot. Once installed, the system describes itself as a 22.03 snapshot, not rc2. Fun fact, the kernel is 5.10.116 while it's still .115 in master snapshot.

Decided to give this build a chance for WRT1900ACSv2. Upgraded to OpenWrt 22.03.0-rc1 r19302-df622768da from OpenWrt SNAPSHOT r18639-f5865452ac with retained configuration. Using with 5Ghz set to channel 36 (somehow using 40). I continue to have the following:

  • irqbalance enabled (from '0' to '1' in '/etc/config/irqbalance')
  • SQM QoS enabled
  • tx_amsdu disabled. Luci > startup > local startup (nano /etc/rc.local) the following commands:
echo "0" >> /sys/kernel/debug/ieee80211/phy0/mwlwifi/tx_amsdu
echo "0" >> /sys/kernel/debug/ieee80211/phy1/mwlwifi/tx_amsdu

3 days uptime.

Observed Issues

  • For some reason I have both nftables and iptables displaying in status. Currently uneducated in this area.
  • One PC did not connect to 5GHz network on Mixed WPA2/WPA3 PSK, SAE (CCMP) encryption. Forced to use WPA2 and disable WPA3.
  • Increased activity in log. ieee80211 phy1: Mac80211 start BA. See below.
  • iPhone dissociation/association frequently increased. (Observed as increased home/away toggling in home assistant - modified yaml code to mitigate)
(xx:xx:xx:xx:xx:xx is the same mac address)

Sun May 29 15:33:11 2022 kern.debug kernel: [   50.369254] ieee80211 phy0: Mac80211 start BA xx:xx:xx:xx:xx:xx
Sun May 29 15:33:11 2022 kern.debug kernel: [   50.428133] ieee80211 phy0: Mac80211 start BA xx:xx:xx:xx:xx:xx
Sun May 29 15:33:11 2022 kern.debug kernel: [   50.488141] ieee80211 phy0: Mac80211 start BA xx:xx:xx:xx:xx:xx
Sun May 29 15:33:11 2022 kern.debug kernel: [   50.538132] ieee80211 phy0: Mac80211 start BA xx:xx:xx:xx:xx:xx
Sun May 29 15:33:11 2022 kern.debug kernel: [   50.588546] ieee80211 phy0: Mac80211 start BA xx:xx:xx:xx:xx:xx
Sun May 29 15:33:11 2022 kern.debug kernel: [   50.648143] ieee80211 phy0: Mac80211 start BA xx:xx:xx:xx:xx:xx
Sun May 29 15:33:12 2022 kern.debug kernel: [   50.708153] ieee80211 phy0: Mac80211 start BA xx:xx:xx:xx:xx:xx
Sun May 29 15:33:12 2022 kern.debug kernel: [   50.768154] ieee80211 phy0: Mac80211 start BA xx:xx:xx:xx:xx:xx

Whoa RC3 days after RC2?

1 Like

Have you see that the maximum upload speed is equal to the lowest network speed of NIC connected?

example if have a device connected that have only 10 or 100 mbps the maximum upload speed is 10 or 100...

I have not made this observation. I only have one ethernet device and primarly use wlan.

For 22.03.0-rc2 and 22.03.0-rc3, are they still generating the files and the release/thread post is imminent? My target is not available for rc3. My target was only generated May 22 for rc2. Packages for rc2 appear to be publishing as late as today (May 27).

That probably means that RC2 has a flaw. I have reported here that it describes itself as a snapshot. We will know with the release announcement in a few days.

3 Likes

Precisely.

2 Likes

Yes I do see wrong password for my phones.

I upgraded my dumb AP - Wrt1900ACS from 21.02.3 to 22.03 RC1 with keeping settings. Both my phones showed Wrong Password and were not able to connect to WIFI. I had to revert back to 21.02.3 and it worked like a charm. Today I tested 22.03 RC3 and the wrong wifi password issue persisted. I reverted it back again.

No Idea what should be done? Is this a known issue with 22.03? upgrade without keeping setting? Thanks!

Try setting network to WPA2

2 Likes

this is my result

Sat May 28 13:18:35 2022 daemon.info hostapd: wlan0: STA MACADRESS IEEE 802.11: disassociated due to inactivity
Sat May 28 13:18:36 2022 daemon.info hostapd: wlan0: STA MACADRESS IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat May 28 13:44:52 2022 daemon.info hostapd: wlan0: STA MACADRESS IEEE 802.11: authenticated
Sat May 28 13:44:52 2022 daemon.info hostapd: wlan0: STA MACADRESS IEEE 802.11: associated (aid 1)
Sat May 28 13:44:52 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED MACADRESS
Sat May 28 13:44:52 2022 daemon.info hostapd: wlan0: STA MACADRESS WPA: pairwise key handshake completed (RSN)
Sat May 28 14:14:36 2022 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED MACADRESS
Sat May 28 14:14:36 2022 daemon.info hostapd: wlan0: STA MACADRESS IEEE 802.11: disassociated due to inactivity
Sat May 28 14:14:37 2022 daemon.info hostapd: wlan0: STA MACADRESS IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat May 28 14:15:29 2022 daemon.info hostapd: wlan0: STA MACADRESS IEEE 802.11: authenticated
Sat May 28 14:15:29 2022 daemon.info hostapd: wlan0: STA MACADRESS IEEE 802.11: associated (aid 1)
Sat May 28 14:15:29 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED MACADRESS
Sat May 28 14:15:29 2022 daemon.info hostapd: wlan0: STA MACADRESS WPA: pairwise key handshake completed (RSN)type or paste code here

Have you used english letters and only something really easy for test, like qwerty1234

I never keep settings anyway.

In tp-link archer c7 v2, after going from 22-03-0-rc1 to 22-03-0-rc3, internet stopped working.
I had to disable the firewall Hardware flow offloading in luci gui, for it to work again.

Can't say if HW offload was working or not before, but the firewall always worked well with that option enabled.

Same devices running fine with openwrt 22.03.0-rc3!

Is that a thing? I see the folder in the downloads tree... but is it good to go, or still being cooked?
What happened to rc2? DOA?

Looks like a small mistake in the rc2 release commit. (package/base-files/image-config.in was left unchanged)
Quite likely DOA.

Ps.
There seems to be no real functional difference between rc3 and rc2. See commit log from rc3 showing just the addition of one new device between rc2 and rc3. Also LuCI has no changes
https://git.openwrt.ifw.cn/?p=openwrt/openwrt.git;a=shortlog;h=refs/tags/v22.03.0-rc3

2 Likes