FYI, I restored my original cal data ART, and after erasing netgear then got my original default SSID, password, MAC and serial back. I was also able to get 5G going on oldest stock the same as with the alternate cal data.
kernel-panic69 wrote:
That URL works whether connected by wire or wireless. Now, if you know the router's IP address, you can use that with the appended 'debug.htm' as well. The only way you won't be able to use that URL is if you improperly set a static IP on your client device AFAIK. I don't recall Voxel killing that URL, but hey... anything is possible.
I got the message requiring wireless on newest stock, but Voxel worked with just 192.168.1.1/debug.htm to enable telnet. Unfortunately, the telnet setting cannot survive a firmware backdate. Oldest stock debug can also be accessed that way even without WAN, and also has the telnet setting. When I finally got into newest stock debug, the telnet setting was missing anyway.
Alas, nothing I do from stock or voxel telnet is allowing 5G. It seems the only way to get 5G stable on this particular unit is to prep on dd-wrt (reset pin, GUI reset, telnet for netgear erase and nvram erase, etc.) and then switch to oldest stock. Any reboots, resets or further firmware updates lose it again, although most settings can be applied without reboot. Following the same sequence but using a slightly newer stock f/w doesn't work either (tried 1.0.1.xx thru 1.0.3.xx with no joy). I've got a backup config but it's slow going taking at least 20 minutes every time I lose 5G to recycle through dd-wrt to old stock. Unfortunately, I simply haven't been able to get 5G up on dd-wrt, although I've only tried the last 3 builds so far. Perhaps if the wifi button were enabled I'd have better luck. My hunch is that this 5G fussiness is all caused by the 2.4G radio having a hardware issue. Too bad they're not easily removable! _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
EDIT #3: I noticed that the default SSID NETGEARxx last two digits changed for all three radios, as did the stock wifi password, so now both are different than printed on the router sticker! I guess my ART-bak partition might have been from or for a different unit, and perhaps I successfully erased the netgear partion the first time so reverting to stock re-poplated it from the different restored ART. I'll have to try restoring the original ART at some point to see what difference it makes.
I could have told you, because I looked at your data in the ART and ART.bak partition.
The difference was e.g. different SSID's and WLAN passwords.
Probably someone had tried to change the calibration data before.
or whatever
well, since you have now exchanged the calibration data back again and have made no progress - we are now back to 0
by the way regarding the bug with the netgear partion...
the r7800 has the same bug with the netgear partition, and if you have the bug then the wifi can not be activated under the stock firmware.
with the dd-wrt firmware the wifi runs without problems
if the router has a hardware defect - then you can certainly delete what you want - defect remains defective
I tried the Voxel firmware which is based on the Netgear FW and still no go. I flashed it with the dd-wrt FW and bang, all the Wifi come back on! All LEDs are on, SSID’s are detected by my devices!
Quote:
I could not get the Netgear FW to work. In the meantime, I have flashed it with the latest DD-WRT build and all the WiFi appear to be working correctly. As I said previously, this proves all the HW is working correctly.
Quote:
My router wifi worked with the dd-wrt FW but not with NG's after firmware upgrade. You may want to try dd-wrt or openwrt FW to verifiy
i also wrote that it is questionable if the netgear partition has any influence on dd-wrt
why should dd-wrt get anything from the netgear partition if everything needed is in the callibration data
but as the saying goes: the prudent thing is to try
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Sat Jul 31, 2021 12:38 Post subject:
My wifi died after flashing (non-<Kong>) DD-WRT. It would be counter-intuitive to flash that image and remain on it to have working wifi. You would basically have to never reset whatsoever and cross your fingers. _________________ "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
Agreed. I don't know why mine only works on oldest stock, sometimes, and only after prep in dd-wrt. Here's a telnet session from old stock yesterday that made no improvement whatsoever (just before going back to dd-wrt, prepping similarly, and back to old stock again fixed 5G until the next reboot - but that's admittedly too much trouble after every single reboot or refresh). Mine might be all hardware issues after all. Anyway, I guess I'm at a dead end on this one re 5 (and without saying 2.4) GHz, but I'll watch the forum in case anyone can make better progress than I.
I'll probably focus on the 60 GHz WiGig for wireless on this unit (since that always works in both stock and Voxel, and hope dd-wrt will support it at some point too). Currently stalled due to antenna connection on qca9005 that looks just like newer connections but simply can't stay on (despite my using the antenna adapter from an otherwise wasted mini pci-e to m.2 adapter board with included jumper). Pic attached - qca9005 connector on the right is the issue. Could it be a third connector standard that only looks like the new ones? I've currently got the 3rd WLAN antenna connected to it, but once the small connection's jumper is resolved I've also got a couple of built-in WWAN antennas to try, one of which is marked "AUX" and may have originally been for 39 GHz - which although still less than 60 is a lot closer than 5!
Code:
=== IMPORTANT ============================
Use 'passwd' to set your login password
this will disable telnet and enable SSH
------------------------------------------
BusyBox v1.4.2 (2016-09-08 23:08:06 CST) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
MM NM MMMMMMM M M
$MMMMM MMMMM MMMMMMMMMMM MMM MMM
MMMMMMMM MM MMMMM. MMMMM:MMMMMM: MMMM MMMMM
MMMM= MMMMMM MMM MMMM MMMMM MMMM MMMMMM MMMM MMMMM'
MMMM= MMMMM MMMM MM MMMMM MMMM MMMM MMMMNMMMMM
MMMM= MMMM MMMMM MMMMM MMMM MMMM MMMMMMMM
MMMM= MMMM MMMMMM MMMMM MMMM MMMM MMMMMMMMM
MMMM= MMMM MMMMM, NMMMMMMMM MMMM MMMM MMMMMMMMMMM
MMMM= MMMM MMMMMM MMMMMMMM MMMM MMMM MMMM MMMMMM
MMMM= MMMM MM MMMM MMMM MMMM MMMM MMMM MMMM
MMMM$ ,MMMMM MMMMM MMMM MMM MMMM MMMMM MMMM MMMM
MMMMMMM: MMMMMMM M MMMMMMMMMMMM MMMMMMM MMMMMMM
MMMMMM MMMMN M MMMMMMMMM MMMM MMMM
MMMM M MMMMMMM M M
M
---------------------------------------------------------------
For those about to rock... (%C, %R)
---------------------------------------------------------------
root@R9000:/# wlan up
phy for wifi device wifi1 not found
wifi1(qcawifi): enable failed
phy for wifi device wifi0 not found
wifi0(qcawifi): enable failed
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
wifi0 no private ioctls.
/sbin/wlan: eval: 1: cannot create /sys/class/net/wifi0/led: Directory nonexistent
qcawifi: on led failed
root@R9000:/#
root@R9000:/# wlan down
phy for wifi device wifi1 not found
wifi1(qcawifi): disable failed
phy for wifi device wifi0 not found
wifi0(qcawifi): disable failed
root@R9000:/#
root@R9000:/# wlan toggle
phy for wifi device wifi1 not found
qcawifi: WIFITOGGLE failed
phy for wifi device wifi0 not found
qcawifi: WIFITOGGLE failed
/sbin/wlan: eval: 1: cannot create /sys/class/net/wifi1/led: Directory nonexistent
wifi1 no private ioctls.
qcawifi: force off led failed
root@R9000:/#
root@R9000:/# wlan up
phy for wifi device wifi1 not found
wifi1(qcawifi): enable failed
phy for wifi device wifi0 not found
wifi0(qcawifi): enable failed
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
root@R9000:/#
root@R9000:/# wlan toggle
phy for wifi device wifi1 not found
qcawifi: WIFITOGGLE failed
phy for wifi device wifi0 not found
qcawifi: WIFITOGGLE failed
wifi0 no private ioctls.
/sbin/wlan: eval: 1: cannot create /sys/class/net/wifi0/led: Directory nonexistent
qcawifi: on led failed
root@R9000:/#
root@R9000:/# wlan down
phy for wifi device wifi1 not found
wifi1(qcawifi): disable failed
phy for wifi device wifi0 not found
wifi0(qcawifi): disable failed
root@R9000:/#
root@R9000:/# wlan up
phy for wifi device wifi1 not found
wifi1(qcawifi): enable failed
phy for wifi device wifi0 not found
wifi0(qcawifi): enable failed
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
Sorry, rule does not exist.
wifi0 no private ioctls.
/sbin/wlan: eval: 1: cannot create /sys/class/net/wifi0/led: Directory nonexistent
qcawifi: on led failed
root@R9000:/#
root@R9000:/# nvram default
root@R9000:/#
root@R9000:/# nvram commit
root@R9000:/#
root@R9000:/# ngmtd="$(awk -F: '/"netgear"$/ {print $1}' /proc/mtd | grep mtd)"
root@R9000:/# [ -n "$ngmtd" ] && flash_erase /dev/"$ngmtd" 0 0
Erasing 128 Kibyte @ 4460000 -- 100 % complete
root@R9000:/#
root@R9000:/# lspci
0000:00:00.0 Ethernet controller: Device 1c36:0002 (rev 01)
0000:00:01.0 Ethernet controller: Device 1c36:0001 (rev 01)
0000:00:03.0 Ethernet controller: Device 1c36:0001 (rev 01)
0000:00:04.0 Network and computing encryption device: Device 1c36:0011 (rev 01)
0000:00:04.1 Network and computing encryption device: Device 1c36:8011 (rev 01)
0000:00:05.0 System peripheral: Device 1c36:0021 (rev 01)
0000:00:05.1 System peripheral: Device 1c36:8021 (rev 01)
0001:00:00.0 PCI bridge: Device 1c36:0031 (rev 01)
0001:01:00.0 PCI bridge: ASMedia Technology Inc. Device 1182 (rev ff)
0001:02:03.0 PCI bridge: ASMedia Technology Inc. Device 1182 (rev ff)
0001:02:07.0 PCI bridge: ASMedia Technology Inc. Device 1182 (rev ff)
0001:03:00.0 Network controller: Qualcomm Atheros Device 0046 (rev ff)
0001:04:00.0 Network controller: Qualcomm Atheros Device 0046 (rev ff)
0002:00:00.0 PCI bridge: Device 1c36:0031 (rev 01)
0002:01:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
0003:00:00.0 PCI bridge: Device 1c36:0031 (rev 01)
0003:01:00.0 Network controller: Wilocity Ltd. Wil6200 802.11ad Wireless Network Adapter (rev 02)
root@R9000:/#
root@R9000:/# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br0 state DOWN mode DEFAULT qlen 1000
link/ether 78:d2:94:b4:d4:2f brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
link/ether 78:d2:94:b4:d4:2b brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
link/ether 78:d2:94:b4:d4:2c brd ff:ff:ff:ff:ff:ff
5: sit0: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT
link/sit 0.0.0.0 brd 0.0.0.0
6: pas0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 42:fe:ef:12:25:de brd ff:ff:ff:ff:ff:ff
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP mode DEFAULT qlen 4000
link/ether 78:d2:94:b4:d4:30 brd ff:ff:ff:ff:ff:ff
8: ifb0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 32
link/ether 92:89:ba:52:54:2e brd ff:ff:ff:ff:ff:ff
9: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 32
link/ether ae:f4:3e:27:c5:3c brd ff:ff:ff:ff:ff:ff
10: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN mode DEFAULT
link/ether f2:7e:6a:22:80:b7 brd ff:ff:ff:ff:ff:ff
11: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
link/ether 78:d2:94:b4:d4:2b brd ff:ff:ff:ff:ff:ff
12: brwan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
link/ether 78:d2:94:b4:d4:2c brd ff:ff:ff:ff:ff:ff
13: ethlan@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT
link/ether 78:d2:94:b4:d4:2b brd ff:ff:ff:ff:ff:ff
14: ethwan@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master brwan state UP mode DEFAULT
link/ether 78:d2:94:b4:d4:2c brd ff:ff:ff:ff:ff:ff
16: p1@eth1: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc noqueue master bond2 state LOWERLAYERDOWN mode DEFAULT
link/ether 78:d2:94:b4:d4:2b brd ff:ff:ff:ff:ff:ff
17: p2@eth1: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc noqueue master bond2 state LOWERLAYERDOWN mode DEFAULT
link/ether 78:d2:94:b4:d4:2b brd ff:ff:ff:ff:ff:ff
18: bond2: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
link/ether 78:d2:94:b4:d4:2b brd ff:ff:ff:ff:ff:ff
root@R9000:/#
root@R9000:/# reboot
_________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
2). Unzip the image files from the downloaded firmware zip files.
3). CHANGE firmware to a not wanted one:
It is NOT enough to flash same firmware again! Not from GUI and not even using tftp.
You must alternate the version, e.g. between Netgear/Voxel:
Router GUI: Administration: Firmware Update: Locate and select the upgrade file on your hard disk: Browse
4). CHANGE firmware to the wanted one:
Router GUI: Administration: Firmware Update: Locate and select the upgrade file on your hard disk: Browse
5). Erase all configuration data:
R8900/R9000: Run these commands from a router shell/prompt:
Q: My WiFi can not be switched on. It's on in ADVANCED: Advanced Setup: Wireless Settings,
but the BASIC page and the Kamoj add-on Router Information shows it as off.
Also there really is no WiFi available to connect. What can I do? (@Giudi001)
A: This is a Netgear bug that can also happen when you update the Firmware or at other times.
One reason is if you have switched off the WiFi with the hard button on the router,
and then made a Firmware update. The radios would then have been left unusable.
A1: The smart way: Install Kamoj add-on 5.4b24 or later, and enable WiFi Supervison in Settings.
Within one minute, the WiFi should be working again.
A2: The manual way: Run this command, from a router terminal shell/prompt:
Code:
wlan down;wlan up;for i in 1 2;do { [ "$(dni_wlan radio 11a -s)" != "ON" ] || [ "$(dni_wlan radio 11g -s)" != "ON" ]; } && wlan toggle; done
6). Save the Router configuration file:
Router GUI: Advanced: Administration: Backup Settings: Save a copy of current settings: Back Up
Make sure the file size is less than 100Kb.
Q: My R7800/R9000 malfunctions and seems to be corrupt. What to do?
A: There is a severe Netgear bug (in both R7800 and R9000) resulting in corrupt configuration backup files.
The bug also exist in Voxel FW.
The bug will also cause many add-on functions to stop working.
The bug has reportedly resulted in random hard to explain errors,
like lost internet and wifi.
Just opening one of these forms - without changing anything - could cause corrupt configuration:
- Opening: "BASIC: NETGEAR Downloader"
- Opening: "ADVANCED: NETGEAR Downloader: NETGEAR Downloader Settings"
- Opening: "ADVANCED: NETGEAR Downloader: NETGEAR Download Manager"
This GUI change is known to have caused corrupt configuration:
Advanced: Setup: LAN Setup: Starting IP Address
Advanced: Setup: LAN Setup: Apply
These GUI changes are known to have caused corrupt configuration:
Advanced: Administration: Logs: "Turn off wireless signal by schedule"
Advanced: Administration: Logs: ReadySHARE
Advanced: Administration: Logs: Apply
Your current configuration may also be corrupt.
Check it by making a backup and then check the file size!
You can check the size of your backup files, they should not be bigger than 100Kb.
If they are bigger they are probably corrupt.
A way to check configuration corruption is to:
From router shell/prompt run:
nvram show
When configuration is corrupt this command does never finish, the command just hangs.
If corruption due to too big configuration/backup files:
From router shell/prompt:
nvram default
nvram commit
VERY IMPORTANT: Do NOT try to restore a corrupt backup.
Final words:
It's recommended to make a configuration backup before and after changing router settings,
and then compare the size of the backup files.
I'll probably focus on the 60 GHz WiGig for wireless on this unit (since that always works in both stock and Voxel, and hope dd-wrt will support it at some point too). Currently stalled due to antenna connection on qca9005 that looks just like newer connections but simply can't stay on (despite my using the antenna adapter from an otherwise wasted mini pci-e to m.2 adapter board with included jumper). Pic attached - qca9005 connector on the right is the issue. Could it be a third connector standard that only looks like the new ones? I've currently got the 3rd WLAN antenna connected to it, but once the small connection's jumper is resolved I've also got a couple of built-in WWAN antennas to try, one of which is marked "AUX" and may have originally been for 39 GHz - which although still less than 60 is a lot closer than 5!
ho1Aetoo wrote:
you could get the 60Ghz radio to work, but you need a 60Ghz antenna for the QCA9005 card and you can usually only get that by cannibalizing any old notebooks or dock with WiGig.
I may have expressed myself a little unclearly.
But you definitely need a compatible 60Ghz antenna for the card.
actually this is not a pure antenna but a 60GHz antenna + upconverter RFIC module
The module itself contains the Wil6110 chip!
without the module you only have a normal WLAN Card - nothing more
in addition, the RF connectors are not standard connectors
Ah, thanks very much! Understood now. I'll have to source a matching Wil6110 RFIC module. I'd mistakenly assumed it was already built into the qca9005 card. I guess that explains why my antenna jumper wouldn't fit.
EDIT: Just checked eBay and nada. I don't suppose the more readily available Intel module would work with the Qualcomm/Atheros card? _________________ My DD-WRT Routers:
Linksys WRT3200ACM - Marvell
Linksys WRT1900ACS - Marvell
Netgear R9000 - Atheros
Netgear R7000 - Broadcom
PC x86-64 VM - Atheros
In the card itself is also a Wilocity chip.
The cards themselves do not generate a 60Ghz signal.
The 60Ghz signal including beamforming is generated directly in the antenna module.
(you could also call it a active antenna design)
There are different WiGig versions (codename Marlon / Falcon / Sparrow).
They also have different antennas
Marlon = 16x beamforming
Falcon = 32x 360°
Sparrow = 24x beamforming
and the Intel modules have 20x arrays
The cards and modules have partly different RF connectors (X.fl or unknown)
The DW1601 was for example in the Dell D5000 or 6430u.
The problem is to get a card with a suitable antenna.
You can get the cards everywhere, but not the antennas.
otherwise you have to read up on how far you can get the cards to run in non-dell devices.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Tue Aug 03, 2021 20:28 Post subject:
The only thing I have not done is mess with the ART partition(s); I have run the gamut of everything from the Voxel FAQ and mine is currently on the latest Voxel firmware and no working wifi. The hardware is not even being detected, but the LEDs are lighting up again and the webUI shows that the radios are working. The wifi button light keeps going off and coming on randomly and not sure I want to risk pushing it . I may try to recover the cal data in the ART partition(s) some other time. _________________ "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
That might be an interesting possibility (buy a defective R9000, remove the antenna and get a QCA9008 card somewhere).
Or in your case maybe buy a working R9000 (you already have a defective one)
too sketchy...i had one R9000 with no WiFi, plugged a DDWRT supported router in WAP mode in one of its LAN ports and happy days...sold it to a friend and he is happy chappy with it.. _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Posted: Sun Dec 04, 2022 6:03 Post subject: Re: Voxel FAQ, which does NOT contain DD-WRT commands
blkt wrote:
Q: My WiFi can not be switched on. It's on in ADVANCED: Advanced Setup: Wireless Settings,
but the BASIC page and the Kamoj add-on Router Information shows it as off.
Also there really is no WiFi available to connect. What can I do? (@Giudi001)
A: This is a Netgear bug that can also happen when you update the Firmware or at other times.
One reason is if you have switched off the WiFi with the hard button on the router,
and then made a Firmware update. The radios would then have been left unusable.
A1: The smart way: Install Kamoj add-on 5.4b24 or later, and enable WiFi Supervison in Settings.
Within one minute, the WiFi should be working again.
A2: The manual way: Run this command, from a router terminal shell/prompt:
Code:
wlan down;wlan up;for i in 1 2;do { [ "$(dni_wlan radio 11a -s)" != "ON" ] || [ "$(dni_wlan radio 11g -s)" != "ON" ]; } && wlan toggle; done
I seem to be hitting this issue on R9000. How can I access the router console? I didn't find any info. There are no telnet / ssh settings in the stock firmware (I reverted to it since dd-wrt didn't find 2 out of 3 radios either).
Can this fix be done through dd-wrt console somehow?
finally R9000 are know for bad heat-sink design and heating issues....burned radios too..
once you flash to DDWRT than access your router via cable on 192.168.1.1 _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
finally R9000 are know for bad heat-sink design and heating issues....burned radios too..
once you flash to DDWRT than access your router via cable on 192.168.1.1
I tried latest DD-WRT (more details in this thread).
I simply didn't see any radios besides 802.11ad listed there.
It boots fine, but the main issue that WiFi can't be even enabled.
I was also able to get 5G going on oldest stock the same as with the alternate cal data.
. I may try to recover the cal data in the ART partition(s) some other time.