Posted: Mon May 23, 2022 7:50 Post subject: New Build - 05/23/2022 - r48954
Welcome to Marvell r48954 beta release thread for reporting, feedback to developers and community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery methods.
Avoid discussions, create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Issues, observations, and/or workarounds reported:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Misc: stracetcpdumpwireshark.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) and applicable configurations to reproduce.
Router Model Linksys WRT1900ACS v2
Firmware Version DD-WRT v3.0-r48954 (05/23/22)
Kernel Version Linux 4.9.314 #3223 SMP Mon May 23 03:28:06 +07 2022 armv7l
Current Time Mon, 23 May 2022 19:15:09
Uptime 28 min
update- browser-waterfox,I switched directly from the first partition from the original software,
connection Type PPPoE-IPv6 Type DHCPv6 with Prefix Delegation-,No release on reconnect-on, Schedule Reboot- All ok
with the last few releases, I'm seeing issues with the 2.4 GHz network.
I was running on r48810 for a few weeks and it worked great, but I had trouble upgrading to anything beyond (tested r48897 and r48954).
I have an old 802.11g device that and did not connect anymore with the newer releases.
This is what I see in the logs:
Quote:
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d MLME: auth request, signal -26 (Accepted)
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d IEEE 802.11: authenticated
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d MLME: assoc request, signal -24 (Accepted)
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d IEEE 802.11: associated (aid 4)
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d RADIUS: starting accounting session 24F6BE2FCFE7F35F
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: pairwise key handshake completed (RSN)
May 23 18:35:28 linksys daemon.info dnsmasq-dhcp[1430]: DHCPDISCOVER(br0) 00:1a:6b:a8:4a:2d
May 23 18:35:28 linksys daemon.info dnsmasq-dhcp[1430]: DHCPOFFER(br0) 192.168.10.25 00:1a:6b:a8:4a:2d
May 23 18:35:28 linksys daemon.info dnsmasq-dhcp[1430]: DHCPREQUEST(br0) 192.168.10.25 00:1a:6b:a8:4a:2d
May 23 18:35:28 linksys daemon.info dnsmasq-dhcp[1430]: DHCPACK(br0) 192.168.10.25 00:1a:6b:a8:4a:2d pronto2
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key Error Request (STA detected Michael MIC failure (group=1))
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: ignore Michael MIC failure report since group cipher is not TKIP
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d RADIUS: starting accounting session 24F6BE2FCFE7F35F
May 23 18:35:28 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: pairwise key handshake completed (RSN)
May 23 18:35:29 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key Error Request (STA detected Michael MIC failure (group=1))
May 23 18:35:29 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: ignore Michael MIC failure report since group cipher is not TKIP
May 23 18:35:29 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:29 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:30 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:31 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:32 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:32 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:32 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:32 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:32 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:32 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d WPA: received EAPOL-Key request with invalid MIC
May 23 18:35:38 linksys daemon.info hostapd: wlan1: STA 00:1a:6b:a8:4a:2d IEEE 802.11: deauthenticated due to local deauth request
When preparing some logs for this post and going back/forth between these releases I noticed that this also does happen with the r48810 release.
But I seem to be able to fix the issue by going to the wireless security settings page and hitting "Apply", which apparently reloads some of the wifi stuff.
I was checking if the "Disable EAPOL Key Retries" option would make any difference but it doesn't matter if it's enabled or disabled.
It looks to me as if there's some difference in the way the (2.4G) wifi is setup between the initial state after rebooting and after hitting the Apply button in the security settings.
Joined: 08 May 2018 Posts: 14247 Location: Texas, USA
Posted: Mon May 23, 2022 17:12 Post subject:
You can't mix and match WPA2 and WPA3 on Marvell (this has been discussed in the forum already), especially with BG-Mixed (why you're using that setting, no idea... should be NG-Mixed or Mixed). Pick the security algorithm/method that works across the board. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
But I'm using these settings for ages without any problems until now.
It also seems to work fine now after reapplying the security settings, even with the r48954 release.
Are you sure that this is the issue?
Sebastian
EDIT: no, it's not the issue. I disabled WPA3 and rebooted the router.
Same errors as before - the device does not connect.
I enabled WPA3 additionally as before and only hit apply - works.
(Of course the client device does not know anything about WPA3, I'm glad it even can do WPA2)
EDIT2: I was using BG-Mixed because I had issues running NG-mixed in the past.
I changed it to "G only" now, which seems to work fine at the moment.
It also looks like this solved the initial issue - I have power-cycled the router and also rebooted it from the command line and each time my problematic device was able to connect just fine afterwards.
Joined: 08 May 2018 Posts: 14247 Location: Texas, USA
Posted: Mon May 23, 2022 18:48 Post subject:
@seb666:
Keep in mind, the following links may contain misinformation - if WPA2/3 conjoined was *not* tested strictly on Marvell, any 'success' shown is likely moot. This area of the forum has a long history of *misinformation* and I gave up trying to correct any of it because people love their freedom of speech and to have many threads about similar topics because they're too lazy to search the forum or internet. That being said, happy reading.
Thanks for the reading material!
I don't want to hijack this thread, so I'll only say that I have had enabled WPA2+3 personal for ages and never ran into any issues related to this.
Not all my devices support WPA3, so I cannot turn off WPA2.
I did have "the" issue with Apple devices losing connectivity in post-r44048 releases that was fixed last(?) year, but I don't think that was related to the security settings (I also don't remember if WPA3 was available in that release).
From the links you provided, I gather that simultaneously activating WPA2+3 can cause issues though, so I'll keep that in mind.
Quick question on the side: is there a way to see which connected clients use WPA2 and which are using WPA3?
- update works good without any problems
- VPN WireGuard
- USB
- DDNS
- CRON "delete directories older > x Days, created by 3xWebCams (stored on128GB SSD)"
- Port Forwarding
- FTP
- Samba
- WLAN offline, I use UniFi AP AC LITE as access Point!
- Lan
all OK without error, Thank You for the good work !!!!
I replaced the script and tried Telnet into the router and check if /tmp/custom.sh and not exists after reboot! _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt