Joined: 23 Jan 2008 Posts: 50 Location: Ulm, Germany
Posted: Mon May 07, 2018 15:24 Post subject: Re: New Kong's test build: DD-WRT 35550M - 2018/03/28
Router: Netgear Nighthawk R7000P
Firmware: DD-WRT 35550M - 2018/03/28 (Kong build)
Kernel: 4.4.124
Reset: Rebooting with factory defaults didn't help.
Errors: When being in "Client Bridge" mode on 5 GHz Wi-Fi , broadcast messages seem to be ignored most of the time. This causes ARP and DHCP to fail most of the time, unless the ARP record is configured statically at the other hosts in the broadcast domain.
Router: Asus RT-AC3100
Firmware: DD-WRT v3.0-r35550M kongac
Status: Working
Reset: No
Previous: kong asus 5300 2018-02-19
Errors: nothing can connect to 2.4Ghz wifi.
I've been having problems with 2.4Ghz since I set this up. I tried using backupessential to copy my settings from an asus ac1900 to this 3100 (same as 5300 just 2 radios not 3) and the 2.4ghz band was completely missing. no eth1+eth2 in the terminal or gui. doing a hard nvram reset brought it back and I configured everything by hand. Worked fine for 2 days now I can't get 2.4Ghz to work again. This time it shows up, but nothing can connect. I checked the output of ps and it shows the nas command 2x, same everything except for the 2 different SSIDs. I did notice that the 2.4ghz strangely has the same mac address as the LAN interface. Changing it in nvram and rebooting made no difference. doing nvram erase didn't fix it even after manually setting it up. I'm on an older CFE but backed it up, and will try to upgrade to the new OEM firmware and see how it goes.
This is so strange, I used to tell everyone to get asus routers, now I got one of the best they make and I want to throw it away. the old ac1900 still works perfect with the same Feb. kong build.
@<kong> any ideas before I stomp this router into the ground? Thanks.
Router: Asus RT-AC3100
Firmware: DD-WRT v3.0-r35550M kongac
Status: Working
Reset: No
Previous: kong asus 5300 2018-02-19
Errors: nothing can connect to 2.4Ghz wifi.
I've been having problems with 2.4Ghz since I set this up. I tried using backupessential to copy my settings from an asus ac1900 to this 3100 (same as 5300 just 2 radios not 3) and the 2.4ghz band was completely missing. no eth1+eth2 in the terminal or gui. doing a hard nvram reset brought it back and I configured everything by hand. Worked fine for 2 days now I can't get 2.4Ghz to work again. This time it shows up, but nothing can connect. I checked the output of ps and it shows the nas command 2x, same everything except for the 2 different SSIDs. I did notice that the 2.4ghz strangely has the same mac address as the LAN interface. Changing it in nvram and rebooting made no difference. doing nvram erase didn't fix it even after manually setting it up. I'm on an older CFE but backed it up, and will try to upgrade to the new OEM firmware and see how it goes.
This is so strange, I used to tell everyone to get asus routers, now I got one of the best they make and I want to throw it away. the old ac1900 still works perfect with the same Feb. kong build.
@<kong> any ideas before I stomp this router into the ground? Thanks.
No problem here _________________ My Routers - NETGEAR R7000
Firmware: DD-WRT v3.0-r40270M kongac (07/11/19)
Kernel: Linux 4.4.185 #670 SMP Thu Jul 11 02:19:39 CEST 2019 armv7l
http://www.desipro.de/ddwrt/K3-AC-Arm/ ---------------------------------------------------------------- - TP-LINK TL-WR1043ND V2
Firmware version: LEDE Reboot 17.01.4 (18/10/17)
Kernel: Linux version 4.13.3
https://downloads.lede-project.org/releases/ ---------------------------------------------------------------- http://www.ncsacademy.com/default.cfm?ref=28555
Ran into a new problem with the Gateway R7000 with over 15 days uptime. The GUI would not load up correctly with a lot of missing data, menu tabs where not labeled. I was able to get into other menus but all had a lot of missing information. I tried a couple of methods to reset httpd service with the same problem, only fix was reboot. I will see if the problem comes back. I still get daemon.err httpd[1323]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases every time I login. Even with the GUI issue all other services where working fine: DNSCrypt, OpenVPN, IPv6, YAMon3, etc...
My uptime with Build 35550M is over 25 days now, still see daemon.err httpd[1323]: Request Error Code 401: when I log into the router but doesn't effect the operation.
With the extra code in DNSMasq I would notice over time once Free RAM was below 50MB I would run into problems. Removing the extra code made made the R7000 stable.
Removed DNSMasq Extra Code to monitor DNS requests....
can someone post a mirror link to 35550m for r7000?
http://ddwrt-kong.clonevince.fr/ _________________ Netgear R7000 on Build 55109
Asus AC-AC68U rev. C1 (AP) on Build 55109
Asus AC-68U rev. A1 on Build 54604
Asus AC-68U rev. A1 on Build 53339
I've been on this since it came out and I've been noticing that my wifi drops and comes back regularly. For example, my phone will show an exclamation mark on the wifi symbol, then go to 4G, then quickly back to wifi every hour or so. Any ideas? This wasn't an issue before.
Also, is this bad?
Router Name R8000
Router Model Netgear R8000
Firmware Version DD-WRT v3.0-r35550M kongac (03/28/1
Kernel Version Linux 4.4.124 #548 SMP Wed Mar 28 09:52:34 CEST 2018 armv7l
Hostname R8000
Current Time Thu, 03 May 2018 11:51:45
You might want to scan your site for the least congested wifi channels then specify them in Wireless > Basic Settings
Luckily I fixed my above issue with Kong's package repository I installed ip-full and edited YAMon3's config file edited _path2ip='/opt/usr/sbin/ip' and have working IPv6 with YAMon3
NOTE: Also need _includeIPv6='1'
Thanks, @mac913! I noticed that YAMon was showing me the `ip` usage message whenever it started, and your fix worked for me. I appreciate you posting it.
Router Model: Netgear R7000
Firmware Version: DD-WRT v3.0-r35550M kongac (03/28/1
Kernel Version: Linux 4.4.124 #548 SMP Wed Mar 28 09:52:34 CEST 2018 armv7l
Reset: No
Previous: Kong r33675M
Errors: No functional problems noticed, but Syslog has some errors and warnings from the booting process; none so far after successfully booting.
.
Thanks for your magic internet cure.