Incant imagine any of those settings would cause 5GHz to flat out not work. What kind of clients do you have? Load up a WiFi scanner app and see what the client detects (on iOS, can use Apple’s Airport app, e.g.). _________________ Netgear R7500v2, DD-WRT v3.0-r37845M kongat
Netgear R7000, DD-WRT v3.0-r37715M kongac
I had this router sine July of last year, been on the Kong bandwagon since about build v3.0-3200, and currently on latest 37945M build. I upgrade firmware with the .bin file. Most of the time I do a reboot and reset to initial settings, to then restore settings from backup. Yet if the build proves to cause issues, I then do a 30/30/30 reset to see if that'll do it (didn't make difference in this case for current 5ghz issue). Currently the only setting i have toggled is WAN Traffic Counter ttraff Daemon: Disable, and...
Backup your config then reflash with ddup via telnet with ‘erase nvram && nvram erase && reboot’ and see if it works (change nothing). Then put back just these config (manually), them only, nothing else. Report back
Joined: 17 Jan 2018 Posts: 64 Location: Georgia, USA
Posted: Sun Dec 16, 2018 20:55 Post subject:
sweatbee wrote:
router r7800
My only issue with this build (and all previous builds) is the NTP Client
I have the NTP server set to us.pool.ntp.org
On firmware upgrades and power cycles of the router the NTP Client picks up the time properly.
However, if I do a soft reboot from the Administration/Management tab or if I use Administration/Keep Alive to do a scheduled reboot then the NTP Client never finds the NTP server to reset the time.
Dec 31 19:00:46 DD-WRT daemon.err ntpclient[1510]: Failed resolving address to hostname us.pool.ntp.org: Try again
Dec 31 19:00:46 DD-WRT daemon.err ntpclient[1510]: Failed resolving server us.pool.ntp.org: Network is down
Dec 31 19:00:46 DD-WRT daemon.err process_monitor[1505]: cyclic NTP Update failed (servers us.pool.ntp.org)
Dec 31 19:00:46 DD-WRT daemon.err process_monitor[1505]: Last update failed, we need to re-update after 30 seconds
I have to use Setup/Basic Setup apply settings for the NTP Client to properly pick up the time (or power cycle the router).
The only thing I can think of is that the boot sequence must be different depending on how you activate it, and somehow this affects the NTP Client.
Discovered and fixed my problem. It was not a NTP problem. It was a user ID Ten T problem.
Using my backup/test r7800 I cleared NVRAM and manually entered settings one at a time and rebooted after each change until I discovered the setting causing the problem.
On the Services/Services tab I had set under "DHCP Server" the "Used Domain" to "LAN & WLAN" in lieu of the default "WAN". Why I did this sometime in the past I have no recollection, but I kept making this change through many firmware updates. Leaving this setting at the default of "WAN" solved my NTP rebooting issues.
Change the default settings only if you know what you are doing, not just because you can. _________________ R7800 r53339 std (08/01/23)
Private network on bridge br0 = eth1 (vlan 1) + wlan0 + wlan1.
Guest network on bridge br1 = eth1.4 (vlan 4) + VAPs (wlan0.1 + wlan1.1) for IOT devices
(Roku's, Amazon Echos, smart switches, etc.) and guest.
Noob still finding my way.
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 1 set ports "1 2 6"
swconfig dev switch0 vlan 4 set ports "3 4 6t"
swconfig dev switch0 set apply
vconfig add eth1 4
brctl addif br1 eth1.4
ifconfig eth1.4 up
Joined: 17 Jan 2018 Posts: 64 Location: Georgia, USA
Posted: Sun Dec 16, 2018 21:14 Post subject:
mrjcd wrote:
sweatbee wrote:
"Used Domain" to "LAN & WLAN"
mines been like that forever... and actually 'LAN Domain' is also set to my local DNS LAN name :P
LOL, what can I say? I only know this made the problem go away for me on my r7800. I'm a noob! What do I know? _________________ R7800 r53339 std (08/01/23)
Private network on bridge br0 = eth1 (vlan 1) + wlan0 + wlan1.
Guest network on bridge br1 = eth1.4 (vlan 4) + VAPs (wlan0.1 + wlan1.1) for IOT devices
(Roku's, Amazon Echos, smart switches, etc.) and guest.
Noob still finding my way.
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 1 set ports "1 2 6"
swconfig dev switch0 vlan 4 set ports "3 4 6t"
swconfig dev switch0 set apply
vconfig add eth1 4
brctl addif br1 eth1.4
ifconfig eth1.4 up
Joined: 17 Jan 2018 Posts: 64 Location: Georgia, USA
Posted: Sun Dec 16, 2018 21:26 Post subject:
bushant wrote:
sweatbee wrote:
I only know this made the problem go away for me on my r7800.
Glad that fixed your problem but my 7800 also using "LAN & WLAN" without NTP problems. Seems odd.
I love DD-WRT, but I have decided it is definitely odd! _________________ R7800 r53339 std (08/01/23)
Private network on bridge br0 = eth1 (vlan 1) + wlan0 + wlan1.
Guest network on bridge br1 = eth1.4 (vlan 4) + VAPs (wlan0.1 + wlan1.1) for IOT devices
(Roku's, Amazon Echos, smart switches, etc.) and guest.
Noob still finding my way.
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 1 set ports "1 2 6"
swconfig dev switch0 vlan 4 set ports "3 4 6t"
swconfig dev switch0 set apply
vconfig add eth1 4
brctl addif br1 eth1.4
ifconfig eth1.4 up
Spoke too soon about all clients connecting on the new k4.9M builds. While on 5GHz it looks no user complained anymore that it cannot connect, this past weekend one b/g/n user could not authenticate on any Wireless Network Mode, whatever was tried on it. And tried them all. Was so confident that it's a client problem, that I went thermonuclear on it: wiped OS, reinstall, searched for new drivers, bought a big hammer, etc. It just could not authenticate:
Code:
daemon.info hostapd: ath1.1: STA ab:cd:ef:12:34:56 MLME: auth request, signal -49 (Accepted)
daemon.notice hostapd: ath1.1: STA ab:cd:ef:12:34:56 IEEE 802.11: did not acknowledge authentication response
daemon.info hostapd: ath1.1: STA ab:cd:ef:12:34:56 MLME: assoc request, signal -49 (Accepted)
daemon.info hostapd: ath1.1: STA ab:cd:ef:12:34:56 IEEE 802.11: disassociated
daemon.info hostapd: ath1.1: STA ab:cd:ef:12:34:56 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Remembered the same issue but on 5GHz week or so before. And that the client not being being connected all the time, the only changes in the networking environment were on the AP. And as a last resort went back to the router. Surprise again, no problems connecting with the k3.18 build. From reset and manual config.
Gosh, this new wireless security setup wreak havoc on so many builds...
