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.org/?p=openwrt/openwrt.git;a=shortlog;h=refs/tags/v22.03.0-rc3
2 Likes
OpenWrt 22.03.0-rc2 and rc3 are causing on a Fritzbox 7412 bootloops due to a misdetected flash chip.
Until OpenWrt 22.03.0-rc1 the boot log states
[ 8.397735] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xf1
[ 8.402654] nand: Toshiba NAND 128MiB 3,3V 8-bit
[ 8.407264] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
but beginning with OpenWrt 22.03.0-rc2 the boot log states
[ 8.420923] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xf1
[ 8.425851] nand: Toshiba TC58NVG0S3HTA00 1G 3.3V 8-bit
[ 8.431069] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
The chip soldered on my device reads as Toshiba TC58BVG0S3HTA00, which has a different page organisation and it complains about fixable bit-flip detection and afterwards about uncorrectable ECC errors when it's handled like the N. Dunno yet how to fix, but haven't investigated further...
But rc2 and rc3 are not released yet, so...
Sounds like caused by this backport by @chunkeey
"kernel: add support for Toshiba TC58NVG0S3HTA00 NAND flash"
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=ec45e1ff68d198aded784ad7712484c1474ede60;hp=144d9c4a43cb871756b8e96f9e8c6a1d3f1d915d
Sounds that there are Fritzboxes out there with different flash chips soldered on, the 7430 should be a sibling to the 7412. How to expand the patch to detect the right flash chip? (Can't speak C...) Completely reverting it is only the second best option I think, there is a reason for it...
letters, numbers and special character combined
I tried it again without keeping settings, WIFI Password still not working.
However, only phones (Oneplus 8 pro and Galaxy S22 Ultra, if it matters) can't connect to wifi, wrong password. My 5 years old laptop has no issue connecting. It is weird.
I had some problems that were solved with 30/30/30, in the case of this problem that you report, I had to change the encryption, but after a while, the problem was a lack of connection with the repeater
so I thought it was better to change wpad wolf basic to wpad mini
Beware of the process of changing packages.
Do you have WPA2 or 3 setup in the router?