gadgetpig DD-WRT User
Joined: 20 Feb 2014 Posts: 74
|
Posted: Tue Mar 07, 2017 15:32 Post subject: |
|
Router: Dlink DIR-810L A1
Firmware: DD-WRT v3.0-r31571 std (03/04/17)
Kernel: Linux 3.10.105 #2548
Status: Good
Reset: No
Errors: None but may require manual reboot after flashing, or when changing wireless settings. YMMV.
Updated via Telnet method, router used in standard router/wireless mode, no QOS. Upon first reboot, I couldn't connect back to 5ghz. My 5ghz had appeared and then suddenly stopped broadcasting SSID. After a soft reboot via telnet, 5ghz settings disappeared entirely. So I manually powered off/on, and used a PC with wired connection. Thanks to MrJCD's screen shot in the Atheros forum, I reconfigured my wireless channel to use 161/set extension=lower level, and get 5ghz working again. In fact my 5ghz has never worked so well! MrJCD's post with recommended wireless setting is here (not all settings will apply fyi):
http://dd-wrt.com/phpBB2/viewtopic.php?t=307775
My recommendation , use the telnet method to flash, and use a wired PC to reconfigure/save wireless settings. Then manually power off/power on if needed.
So my steps were:
1.) flash via telnet and reboot
2.) login wired directly to router and set 5ghz setting to use wide mode (in my case Wide HT40), save, apply settings, and then set extension channel to lower level, save, apply settings and reboot. What happens during this time is wireless channel stays at "auto" (I couldn't manually choose channels just yet)
3.) After reboot, login wired to router again, and go to wireless channel, you will now see a list of channels to manually select. I selected 161, save, apply settings and rebooted. Should be good after that. If the GUI is inaccessible, or router acting weird at first, manually power off and then power on.
After I did that, system has been rock steady.
Thank You Devs!
Processor:
CPU Model Ralink MT7620A ver:2 eco:3
CPU Cores 1
CPU Clock 580 MHz
Load Average 2%
0.00, 0.01, 0.04
Memory
Total Available
94%
61748 kB / 65536 kB
Free
61%
37780 kB / 61748 kB
Used
39%
23968 kB / 61748 kB
Buffers
9%
2080 kB / 23968 kB
Cached
26%
6340 kB / 23968 kB
Active
28%
6752 kB / 23968 kB
Inactive
14%
3280 kB / 23968 kB
Space Usage NVRAM
24 KB / 64 KB
Update 3/16/2017
================
Alas life at channel 161/HT40 wasn't meant to be. After couple days it dropped 5ghz connection, and I couldn't reconnect to channel 161. Since I have neighbors, there may be 5.8ghz wireless phones using channels 149-161. I changed it back to channel 40/HT40/extension channel="lower", and it bonded channel 40+36,and connected fine again (albeit at lower connection speeds). I tried using auto channel selection for 5ghz, but since there's no regional wireless setting, it kept picking a non-valid USA channel (32). best to manually pick non DFS 5ghz channels valid to your region.
Last edited by gadgetpig on Thu Mar 16, 2017 15:15; edited 1 time in total |
|
h8red DD-WRT Guru
Joined: 28 Jun 2011 Posts: 580 Location: Vilnius, Lithuania
|
Posted: Thu Mar 09, 2017 17:30 Post subject: |
|
Router: Asus-rt-n10plus C1
Kernel: 3.2.86 #26205
Status: OK
Reset: no
Errors: no
Web upgrade from previous beta _________________ [Ramips] Nexx WT3020F Openwrt @kernel #4.14.167 (OpenVPN server, Wireguard server, AD blocking, SQM QOS, USB) |
|
ezdisd DD-WRT Novice
Joined: 03 Oct 2012 Posts: 5
|
Posted: Sun Mar 26, 2017 17:22 Post subject: |
|
Router: Buffalo WHR-1166D
Firmware: DD-WRT v3.0-r31571 std (03/04/17)
Kernel: Linux 3.10.105 #2544
Status: meh
Reset: yes
Errors:
Needed a hard reboot to make WAN port work, but that's probably the old OS's fault.
Bigger issue is the 5GHz radio doesn't work. Someone else had this issue a year ago on a similar model http://www.dd-wrt.com/phpBB2/viewtopic.php?p=1010647 Trying different GUI settings and multiple reboots I did see a single beacon packet from it once. The interface is down and I don't see anything in any log, etc.
That post mentions that the WL1 mac is corrupted in the GUI; I also see it as wrong in the NVRAM. A manually set NVRAM value is reverted to crap on reboots or any changes to WLAN in the GUI (whether or not I committed the NVRAM). However, after the set I can manually ifconfig ra1 up and brctl addif br0 ra1 to make it usable. So this is probably not a driver thing and could be worked around in dd-wrt's scripts. |
|