Joined: 21 Aug 2019 Posts: 120 Location: Here, There And Everywhere
Posted: Wed Mar 15, 2023 15:30 Post subject:
Router/Version: Netgear R7800
File/Kernel: DD-WRT v3.0-r52020M std (03/14/23) / Linux 4.9.337 #1648 SMP Tue Mar 14 07:32:01 +07 2023 armv7
Previous/Reset: r51530 / No
Mode/Status: WAP, WDS AP / Works
Issues/Errors: Firmware switching prone to block the router, needs manual power cycle. I ended just saving the settings and then reboot. Vanilla firmware had very low transmit strength, so I gave DD-WRT firmware a chance. What a difference in signal strength! Before I was unable to use the 5GHz radio as WDS backhaul, now it works with signal strength to spare!
Joined: 21 Aug 2019 Posts: 120 Location: Here, There And Everywhere
Posted: Wed Mar 15, 2023 15:37 Post subject:
Router/Version: TP-Link ARCHER-C7 v5
File/Kernel: DD-WRT v3.0-r52020 std (03/14/23) / Linux 3.18.140-d6 #166583 Tue Mar 14 11:03:22 +06 2023 mips
Previous/Reset: r51530 / No
Mode/Status: WDS Station / Works
Issues/Errors: DD-WRT firmware results in stronger signal than ever before! I can finally use 5GHz radio as WDS backhaul (see my previous report).
A question: what exactly does the "Override Chipset Restrictions" option in Wireless->Basic settings (next to "Firmware type") relate to? Does it have to do only with TX Power or something more?
Joined: 18 Mar 2014 Posts: 12882 Location: Netherlands
Posted: Wed Mar 15, 2023 15:39 Post subject:
matjazk wrote:
Router/Version: Netgear R7800
File/Kernel: DD-WRT v3.0-r52020M std (03/14/23) / Linux 4.9.337 #1648 SMP Tue Mar 14 07:32:01 +07 2023 armv7
Previous/Reset: r51530 / No
Mode/Status: WAP, WDS AP / Works
Issues/Errors: Firmware switching prone to block the router, needs manual power cycle. I ended just saving the settings and then reboot. Vanilla firmware had very low transmit strength, so I gave DD-WRT firmware a chance. What a difference in signal strength! Before I was unable to use the 5GHz radio as WDS backhaul, now it works with signal strength to spare!
Joined: 21 Aug 2019 Posts: 120 Location: Here, There And Everywhere
Posted: Wed Mar 15, 2023 16:15 Post subject:
@egc Thanks, I'm aware of that. However the signal strength with DD-WRT radio firmware (on 5GHz) seems better than Vanilla ever was. When I was setting up WDS a few months ago, I was unable to use it on 5GHz (signal was too weak). Now it works great, and I'll stay on DD-WRT for the time being.
you don't have a broken channel list with the vanilla firmware?
(select 149+UU and reboot the router - channel is then set to auto)
you also have no reduced signal level after a reboot with the vanilla firmware?
(select any channel, set the signal strength e.g. to 23-26dB, after a reboot the signal strength is ~16dB / can be fixed by apply clicking in the WLAN tab)
you can set the signal level in the dd-wrt firmware?
(no matter what I set, 3dB-30dB on the clients I see no difference)
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Mar 15, 2023 20:14 Post subject:
channel list broken in both fw, always was as it was never fixed properly, i just use allow overlapping channels enable and manually pick correct channel+ext since i know which is valid. tx power seems to be working, i always use 30dbm with panama domain, i reduced it to 24dbm and scanning showed about a 5dbm difference. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Geez, when all is said and done we might need a new wireless set-up guide.
Protection Mode None RTS Threshold Disabled Beacon 100 DTIM 2 Sensitivity Range 900 or 1350, the rest is good.
Edit: Never mind. Disable TurboQAM, disable power save and you are right these screenshots are way too old now.
Router/Version: TP-Link TL-WR841ND v11
Update method: WebUpgrade
File/Kernel: tl-wr841nd-webflash.bin / Linux 3.18.140-d6 #166559 Tue Mar 14 10:25:03 +06 2023 mips
Previous/Reset: r52004 / no
Mode/Status: AP wired and wireless / Up and running for 2 days, 5:15 hours
Issues/Errors: Nothing significant
The fact is that the router connected to the Internet (to the Internet provider). And it reports an error, the orange WAN indicator flashes (the icon in the form of a planet). Internet is working, I just think it's a glitch
Thank you BS and gurus! _________________ Atheros
Netgear XR500 Nighthawk - DD-WRT 54545
Tp-Link TL-WDR4900 v1.3 - DD-WRT 53133
TP-Link WR1043ND v4 - DD-WRT 51838
TP-Link WR1043ND v2 - Gargoyle OS 1.13.0
TP-Link WR841ND v11 - DD-WRT 55779
Broadcom
Asus RT-AC87U R - DD-WRT 55819
Asus RT-N66U - DD-WRT 55779
Linksys WRT54GL v1.1 - DD-WRT 54517M
Linksys WRT54GL v1.1 - FreshTomato 2023.4_MIPS_K26
Linksys WRT54GL v1.1 - Gargoyle OS 1.6.2
Joined: 03 Nov 2015 Posts: 317 Location: Florida, USA
Posted: Fri Mar 17, 2023 3:27 Post subject:
[quote="strange"]Geez, when all is said and done we might need a new wireless set-up guide. /quote]
Or put up some simple, step by step and in numerical order, some text guides that can be put on the screen side by side. I use these when the only alternative is RESET and ENTER your settings from scratch. _________________ ......All GOOD here... Just Handshakes and Time Stamps !......
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Fri Mar 17, 2023 18:18 Post subject:
Code:
Mar 17 12:19:34 Haswell httpd [httpd] : Authentication fail
Mar 17 12:19:35 Haswell httpd [httpd] : Authentication fail
Mar 17 12:19:39 Haswell httpd [httpd] : Authentication fail
Mar 17 12:19:40 Haswell httpd [httpd] : Authentication fail
Mar 17 12:19:41 Haswell httpd [httpd] : Authentication fail
Mar 17 12:19:46 Haswell httpd [httpd] : Authentication fail
Mar 17 12:22:45 Haswell httpd [httpd] : Authentication fail
Mar 17 12:59:49 Haswell httpd [httpd] : Authentication fail
Mar 17 12:59:54 Haswell httpd [httpd] : Authentication fail
Mar 17 13:00:00 Haswell httpd [httpd] : Authentication fail
Mar 17 13:00:03 Haswell httpd [httpd] : Authentication fail
Mar 17 13:00:08 Haswell httpd [httpd] : Authentication fail
Mar 17 13:00:23 Haswell httpd [httpd] : Authentication fail
Mar 17 13:00:28 Haswell httpd [httpd] : Authentication fail
Mar 17 13:00:32 Haswell httpd [httpd] : Authentication fail
Mar 17 13:00:40 Haswell httpd [httpd] : Authentication fail
Mar 17 13:00:55 Haswell httpd [httpd] : Authentication fail
Mar 17 13:02:19 Haswell httpd [httpd] : Authentication fail
Mar 17 13:02:27 Haswell httpd [httpd] : Authentication fail
Mar 17 13:02:31 Haswell httpd [httpd] : Authentication fail
Mar 17 13:02:40 Haswell httpd [httpd] : Authentication fail
Mar 17 13:02:43 Haswell httpd [httpd] : Authentication fail
Mar 17 13:02:45 Haswell httpd [httpd] : Authentication fail
Mar 17 13:02:46 Haswell httpd [httpd] : Authentication fail
Mar 17 13:02:48 Haswell httpd [httpd] : Authentication fail
Mar 17 13:02:50 Haswell httpd [httpd] : Authentication fail
Mar 17 13:03:08 Haswell httpd [httpd] : Authentication fail
Mar 17 13:03:10 Haswell httpd [httpd] : Authentication fail
Mar 17 13:03:16 Haswell httpd [httpd] : Authentication fail
Mar 17 13:03:20 Haswell httpd [httpd] : Authentication fail
Mar 17 13:03:34 Haswell httpd [httpd] : Authentication fail
Mar 17 13:04:38 Haswell httpd [httpd] : Authentication fail
Mar 17 13:04:42 Haswell httpd [httpd] : Authentication fail
Mar 17 13:05:21 Haswell httpd [httpd] : Authentication fail
Mar 17 13:05:42 Haswell httpd [httpd] : Authentication fail
Mar 17 13:07:09 Haswell httpd [httpd] : Authentication fail
Mar 17 13:09:10 Haswell httpd [httpd] : Authentication fail
Mar 17 13:10:34 Haswell httpd [httpd] : Authentication fail
Mar 17 13:11:36 Haswell httpd [httpd] : Authentication fail
Mar 17 13:13:05 Haswell httpd [httpd] : Authentication fail
Mar 17 13:13:07 Haswell httpd [httpd] : Authentication fail
Mar 17 13:13:59 Haswell httpd [httpd] : Authentication fail
Mar 17 13:14:26 Haswell httpd [httpd] : Authentication fail
Mar 17 13:15:15 Haswell httpd [httpd] : Authentication fail
Mar 17 13:15:31 Haswell httpd [httpd] : Authentication fail
Mar 17 13:15:36 Haswell httpd [httpd] : Authentication fail
Mar 17 13:15:39 Haswell httpd [httpd] : Authentication fail
Mar 17 13:15:43 Haswell httpd [httpd] : Authentication fail
Mar 17 13:16:00 Haswell httpd [httpd] : Authentication fail
Mar 17 13:16:21 Haswell httpd [httpd] : Authentication fail
Mar 17 13:16:36 Haswell httpd [httpd] : Authentication fail
Mar 17 13:17:00 Haswell httpd [httpd] : Authentication fail
[/code]
is there a way to shut this crap up? its been like this for years now, any interaction with gui makes it print this useless spam, yet im clearly authenticated and gui is working fine.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers