Posted: Tue Mar 15, 2022 6:27 Post subject: New Build - 03/15/2022 - r48494
Welcome to MediaTek r48494 beta release thread for reporting, feedback to developers & 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 / Version: Dlink DIR-882 A1
File: dlink-dir882-a1-webflash.bin
Firmware: DD-WRT v3.0-r48494 std (03/15/22)
Previous: DD-WRT v3.0-r48432 std (03/01/22)
Reset: No
Mode: AP
Uptime: few minutes
Status: Not working (personal experience, may vary with other settings)
Services: Openvpn client, DLNA, SAMBA, PPPOE
Issues / Errors:Bricked router. After upload was finished, router was still on r48432. After few minutes, rooter went off and won't boot again. Tried to switch off then on, removed power cable, and nothing, it was bricked. I used recovery mode to upload previous frimware, then factory-to-ddwrt, both didnt work. I used then original firmware 1.01 and it didn't work untill i used DIR882A1_FW104B02_Middleware. I could then restore, then upload factory-to-ddwrt then r48432. Restored settings and voilà !
Posted: Thu Mar 17, 2022 14:27 Post subject: Unstable WiFi on Netgear R6850
Router/Version: Netgear R6850
File: DD-WRT v3.0-r48494 std (03/15/22) factory_to_ddwrt.img
Kernel: Linux 4.14.271 #2190 SMP Tue Mar 15 04:27:45 +07 2022 mips
Previous/Reset: OEM / Yes
Mode/Status: Gateway Wireless Router / PPPOE running; DHCP Server running; WiFi 2.4 Ghz and 5 Ghz active
Issues/Errors: My MacBook (2013) and Intel Win 7 laptop both connect to the WiFi normally and work well, while enjoying a steady connection (N-mode, 2.4 Ghz & 5 Ghz bands), however my mobile phones, smartTV, WiFi smart bulbs are all having a major problem connecting to the WiFi network and connecting to the internet via the DD-WRT router's WiFi.
All these devices were working fine with the OEM firmware and still work fine with other routers at home (OEM). If these mobile devices do connect to the WiFi they regularly lose access to the internet, otherwise they have difficulty even getting connected to the WiFi network in the first place.
I've tried all the recommended settings for the wireless networks, tried playing around with it a bit too, but nothing works.
I'm sharing some of the System Log from when I'm trying to connect with two of my mobile devices (the 2 MAC addresses):
-------------------------------------------------
Mar 17 19:46:29 DD-WRT Netgear_R6850 daemon.info hostapd: wlan0: STA 9e:98:7e:29:d5:6b MLME: auth request, signal -71 (Accepted)
Mar 17 19:46:29 DD-WRT Netgear_R6850 daemon.info hostapd: wlan0: STA 9e:98:7e:29:d5:6b IEEE 802.11: authenticated
Mar 17 19:46:29 DD-WRT Netgear_R6850 daemon.info hostapd: wlan0: STA 9e:98:7e:29:d5:6b MLME: assoc request, signal -71 (Accepted)
Mar 17 19:46:29 DD-WRT Netgear_R6850 daemon.info hostapd: wlan0: STA 9e:98:7e:29:d5:6b IEEE 802.11: associated (aid 1)
Mar 17 19:46:29 DD-WRT Netgear_R6850 daemon.info hostapd: wlan0: STA 9e:98:7e:29:d5:6b RADIUS: starting accounting session 9200DBD6D7E05159
Mar 17 19:46:29 DD-WRT Netgear_R6850 daemon.info hostapd: wlan0: STA 9e:98:7e:29:d5:6b WPA: pairwise key handshake completed (RSN)
Mar 17 19:46:49 DD-WRT Netgear_R6850 daemon.info httpd[9183]: [httpd] : Authentication fail
Mar 17 19:46:49 DD-WRT Netgear_R6850 daemon.err httpd[9183]: [httpd] : Request Error Code 401: Authorization required. Wrong username and/or password!
Mar 17 19:47:20 DD-WRT Netgear_R6850 daemon.info httpd[9183]: [httpd] : Authentication fail
Mar 17 19:47:20 DD-WRT Netgear_R6850 daemon.err httpd[9183]: [httpd] : Request Error Code 401: Authorization required. Wrong username and/or password!
Mar 17 19:47:36 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 1e:da:07:6c:fd:2f MLME: auth request, signal -57 (Accepted)
Mar 17 19:47:36 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 1e:da:07:6c:fd:2f IEEE 802.11: authenticated
Mar 17 19:47:36 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 1e:da:07:6c:fd:2f MLME: assoc request, signal -58 (Accepted)
Mar 17 19:47:36 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 1e:da:07:6c:fd:2f IEEE 802.11: associated (aid 2)
Mar 17 19:47:36 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 1e:da:07:6c:fd:2f RADIUS: starting accounting session C8A76A7729949C96
Mar 17 19:47:36 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 1e:da:07:6c:fd:2f WPA: pairwise key handshake completed (RSN)
Mar 17 19:47:50 DD-WRT Netgear_R6850 daemon.info httpd[9183]: [httpd] : Authentication fail
Mar 17 19:47:50 DD-WRT Netgear_R6850 daemon.err httpd[9183]: [httpd] : Request Error Code 401: Authorization required. Wrong username and/or password!
Mar 17 19:48:18 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b MLME: auth request, signal -64 (Accepted)
Mar 17 19:48:18 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b IEEE 802.11: authenticated
Mar 17 19:48:18 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b MLME: assoc request, signal -64 (Accepted)
Mar 17 19:48:18 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b IEEE 802.11: associated (aid 3)
Mar 17 19:48:18 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b RADIUS: starting accounting session 7D3559AD74CDC0A4
Mar 17 19:48:18 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b WPA: pairwise key handshake completed (RSN)
Mar 17 19:48:20 DD-WRT Netgear_R6850 daemon.info httpd[9183]: [httpd] : Authentication fail
Mar 17 19:48:20 DD-WRT Netgear_R6850 daemon.err httpd[9183]: [httpd] : Request Error Code 401: Authorization required. Wrong username and/or password!
Mar 17 19:48:38 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b MLME: auth request, signal -65 (Accepted)
Mar 17 19:48:38 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b IEEE 802.11: authenticated
Mar 17 19:48:38 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b MLME: assoc request, signal -66 (Accepted)
Mar 17 19:48:38 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b IEEE 802.11: associated (aid 3)
Mar 17 19:48:38 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b RADIUS: starting accounting session B856017DF7F16CD9
Mar 17 19:48:38 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b WPA: pairwise key handshake completed (RSN)
Mar 17 19:48:42 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b MLME: auth request, signal -65 (Accepted)
Mar 17 19:48:42 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b IEEE 802.11: authenticated
Mar 17 19:48:42 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b MLME: assoc request, signal -66 (Accepted)
Mar 17 19:48:42 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b IEEE 802.11: associated (aid 3)
Mar 17 19:48:42 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b RADIUS: starting accounting session 3D937016AE73FFE8
Mar 17 19:48:42 DD-WRT Netgear_R6850 daemon.info hostapd: wlan1: STA 9e:98:7e:29:d5:6b WPA: pairwise key handshake completed (RSN)
Mar 17 19:48:52 DD-WRT Netgear_R6850 daemon.info httpd[9183]: [httpd] : Authentication fail
Mar 17 19:48:52 DD-WRT Netgear_R6850 daemon.err httpd[9183]: [httpd] : Request Error Code 401: Authorization required. Wrong username and/or password!
Mar 17 19:49:23 DD-WRT Netgear_R6850 daemon.info httpd[9183]: [httpd] : Authentication fail
Mar 17 19:49:23 DD-WRT Netgear_R6850 daemon.err httpd[9183]: [httpd] : Request Error Code 401: Authorization required. Wrong username and/or password!
Mar 17 19:49:53 DD-WRT Netgear_R6850 daemon.info httpd[9183]: [httpd] : Authentication fail
Mar 17 19:53:01 DD-WRT Netgear_R6850 daemon.err httpd[9183]: [httpd] : Request Error Code 401: Authorization required. Wrong username and/or password!
Mar 17 19:53:28 DD-WRT Netgear_R6850 daemon.info hostapd: wlan0: STA 9e:98:7e:29:d5:6b IEEE 802.11: disassociated due to inactivity
Mar 17 19:53:30 DD-WRT Netgear_R6850 daemon.info hostapd: wlan0: STA 9e:98:7e:29:d5:6b IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mar 17 19:53:31 DD-WRT Netgear_R6850 daemon.info httpd[9183]: [httpd] : Authentication fail
Mar 17 19:53:31 DD-WRT Netgear_R6850 daemon.err httpd[9183]: [httpd] : Request Error Code 401: Authorization required. Wrong username and/or password!
Posted: Thu Mar 17, 2022 14:47 Post subject: Requesting Advice
I installed the latest beta assuming that would be the best for the router (Netgear R6850) - containing the best bits of old and removing the most bugs found previously, but I guess it's not as simple as that.
Guru, could you please point me towards the most stable release of DD-WRT for the Netgear R6850 router. Thank you.
Posted: Fri Mar 18, 2022 6:16 Post subject: Re: Requesting Advice
crazybawa wrote:
I installed the latest beta assuming that would be the best for the router (Netgear R6850) - containing the best bits of old and removing the most bugs found previously, but I guess it's not as simple as that.
Guru, could you please point me towards the most stable release of DD-WRT for the Netgear R6850 router. Thank you.
I have Netgear R6700v2 and r48141(01/21/22) seems to be the most stable release for me.
Joined: 08 May 2018 Posts: 14242 Location: Texas, USA
Posted: Fri Mar 18, 2022 10:54 Post subject:
It would be more helpful if we knew what settings were on the device in question, and it would also be super helpful if people flashed and reported in the build threads. You are not helping anyone (including the developer(s)) by not reporting. _________________ "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
Posted: Sat Mar 19, 2022 18:33 Post subject: Re: Requesting Advice
Thanks for the info - will give it a try.
1chaoticadult wrote:
crazybawa wrote:
I installed the latest beta assuming that would be the best for the router (Netgear R6850) - containing the best bits of old and removing the most bugs found previously, but I guess it's not as simple as that.
Guru, could you please point me towards the most stable release of DD-WRT for the Netgear R6850 router. Thank you.
I have Netgear R6700v2 and r48141(01/21/22) seems to be the most stable release for me.
Posted: Sat Mar 19, 2022 19:15 Post subject: The settings you asked for..
Hi, thanks for the reply.. I wanted to share the settings but I didn't know where to start or how exactly to do so, as there are so many pages in the Web GUi.
A suggestion/request - it would be great if there could be a 'Debug Report' button in the Web GUI (maybe in Administration) that would output a text file with all the settings that would be relevant to anyone on the DD-WRT Forum, to provide help, while ensuring no private data is shared. Just an idea. Thanks.
kernel-panic69 wrote:
It would be more helpful if we knew what settings were on the device in question,
Hope this is what you asked for:
Ref: Attachments.
FYI: I've tried different settings for DTIM, Beacon Interval, Channel, Channel Width, U-APSD, Disassoc Low Ack, Protection Mode, RTS Threshold, Threshold,... and not found the problem to go away.
kernel-panic69 wrote:
...and it would also be super helpful if people flashed and reported in the build threads. You are not helping anyone (including the developer(s)) by not reporting.
Could you explain what you meant by "flashed and reported in the build thread"? Flashed? I thought this was the build thread.
Last edited by crazybawa on Sat Mar 19, 2022 19:22; edited 1 time in total
Joined: 08 May 2018 Posts: 14242 Location: Texas, USA
Posted: Sat Mar 19, 2022 20:00 Post subject:
It seems people cannot read and comprehend the wikis correctly. 784 is an invalid setting, considering wireless max MTU is not 1500 as with wired ethernet.
Protection mode is either disabled or RTS/CTS for AP modes.
If Protection mode is RTS/CTS, enable threshold and set to 2346.
Enable Short GI.
DTIM should be default of 2.
ACK timing in multiples of 450; 1350 should be plenty.
I wouldn't bother with the TX power settings as they should be whatever the driver and regulatory domain information default to. I presume that the antenna chains selections are the defaults? _________________ "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
Thanks for the inputs. Will give them a try and revert.
I had tried different settings for these parameters and the problem was still there. For instance, by default the first setting for Protection Mode was Disabled/None, I changed it and found pages talking about how 784 was a good setting for the threshold, DTIM was 2 and ACK timing was 500.
kernel-panic69 wrote:
It seems people cannot read and comprehend the wikis correctly. 784 is an invalid setting, considering wireless max MTU is not 1500 as with wired ethernet.
Protection mode is either disabled or RTS/CTS for AP modes.
If Protection mode is RTS/CTS, enable threshold and set to 2346.
Enable Short GI.
DTIM should be default of 2.
ACK timing in multiples of 450; 1350 should be plenty.
I wouldn't bother with the TX power settings as they should be whatever the driver and regulatory domain information default to. I presume that the antenna chains selections are the defaults?
The manual that came with the router, says the max Tx power for 5 Ghz is 22.9 dbm and for 2.4 Ghz it is 19.9 dbm, and the regulatory domain Canada supports Tx powers higher than 17 dbm for 5 Ghz.. but I'm not able to use those, as explained.
Posted: Sun Mar 20, 2022 10:16 Post subject: Findings
Hey, it seems much better after the changes.
Of all the settings you mentioned, the one I hadn't previously tried was Enabling Short GI (thought it was better to keep it disabled in a noisy environment and a large space where some devices can have a low signal. But guess I was wrong.)
The OTHER MAJOR point was that the mobile devices would connect to the WiFi but I would always get a notification saying "No Internet Access" and other such lines about the network not allowing the device to connect to the internet. The devices would then automatically disconnect and connect to other known networks and try. That kept happening and when connected, some webpages would just not load, would take forever, timeout, give me a DNS Not Found error and maybe start working after a few minutes again. This made me look at my DNS settings.
What I did was I removed my Local DNS setting (which I had set to the Gateway Router, this router) and left it as 0.0.0.0. That also seems to have helped. What are your thoughts?
kernel-panic69 wrote:
It seems people cannot read and comprehend the wikis correctly. 784 is an invalid setting, considering wireless max MTU is not 1500 as with wired ethernet.
Protection mode is either disabled or RTS/CTS for AP modes.
If Protection mode is RTS/CTS, enable threshold and set to 2346.
Enable Short GI.
DTIM should be default of 2.
ACK timing in multiples of 450; 1350 should be plenty.
I wouldn't bother with the TX power settings as they should be whatever the driver and regulatory domain information default to. I presume that the antenna chains selections are the defaults?