The best version for my R6400 is 30534 BS. Everything newer gives my trouble after a few days on the LAN side or with Dnsmasq.
I know KONG has R6400 but I wonder how long he let it run before rebooting again as it is his development device.
The best version for my R6400 is 30534 BS. Everything newer gives my trouble after a few days on the LAN side or with Dnsmasq.
I know KONG has R6400 but I wonder how long he let it run before rebooting again as it is his development device.
Cheers
Thank you for the advise. Will try and are up and running on BS 30534 now.
The best version for my R6400 is 30534 BS. Everything newer gives my trouble after a few days on the LAN side or with Dnsmasq.
I know KONG has R6400 but I wonder how long he let it run before rebooting again as it is his development device.
Cheers
It was my development device for about 30min, this is how long it took to port it. Since then it is my main router, thus only gets a reboot when I upgrade the fw and most of the time I skip one or two version on this unit unless there was a major change.
Longest uptime so far 16 days. In the past few months I had one issue where pppd had some hang and I had to kill it in console.
But I have never seen any LAN/Wireless issue on this unit, and I have 2 guest networks and usually 10 wireless devices connected at the same time. And the R6400 does not have anything special, that would make it different from R7000/R6300v2/AC1450 etc. and I don't see a lot of people complain. So far the std arm build 30645 has ~5000 downloads in 5 days.
The best version for my R6400 is 30534 BS. Everything newer gives my trouble after a few days on the LAN side or with Dnsmasq.
I know KONG has R6400 but I wonder how long he let it run before rebooting again as it is his development device.
Cheers
It was my development device for about 30min, this is how long it took to port it. Since then it is my main router, thus only gets a reboot when I upgrade the fw and most of the time I skip one or two version on this unit unless there was a major change.
Longest uptime so far 16 days. In the past few months I had one issue where pppd had some hang and I had to kill it in console.
But I have never seen any LAN/Wireless issue on this unit, and I have 2 guest networks and usually 10 wireless devices connected at the same time. And the R6400 does not have anything special, that would make it different from R7000/R6300v2/AC1450 etc. and I don't see a lot of people complain. So far the std arm build 30645 has ~5000 downloads in 5 days.
I also have units with much older builds. 2 R7000 have 5 month of uptime with 29300.
Since there is no 29300 build for R6400 wich do you is closest one to it (stable wise) that is available for R6400?
The best version for my R6400 is 30534 BS. Everything newer gives my trouble after a few days on the LAN side or with Dnsmasq.
I know KONG has R6400 but I wonder how long he let it run before rebooting again as it is his development device.
Cheers
It was my development device for about 30min, this is how long it took to port it. Since then it is my main router, thus only gets a reboot when I upgrade the fw and most of the time I skip one or two version on this unit unless there was a major change.
Longest uptime so far 16 days. In the past few months I had one issue where pppd had some hang and I had to kill it in console.
But I have never seen any LAN/Wireless issue on this unit, and I have 2 guest networks and usually 10 wireless devices connected at the same time. And the R6400 does not have anything special, that would make it different from R7000/R6300v2/AC1450 etc. and I don't see a lot of people complain. So far the std arm build 30645 has ~5000 downloads in 5 days.
I also have units with much older builds. 2 R7000 have 5 month of uptime with 29300.
Since there is no 29300 build for R6400 wich do you is closest one to it (stable wise) that is available for R6400?
FYI, I had a crash today, after 5 days of uptime. The bad thing is it crashed exactly at the time I turned on my development machine, thus I have no dump. But I know that turning on the wired pc triggered the crash.
At last this gives me a clue how where to look, since the dev machine is hooked up via wire, I know there was no mem issue, as I checked yesterday.
Thus this crash is either in the ethernet driver, or still a problem with k4.4 and the broadcom platform code. Thus time to hook up a little debug box to the serial connector. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
@<Kong>
I'm afraid I'm totally at a loss now. Tried your latest build but WLAN stopped working. I am able to attach all devices but no internet and router's WebGUI not reachable from any device. Ethernet works fine.
FYI, I had a crash today, after 5 days of uptime. The bad thing is it crashed exactly at the time I turned on my development machine, thus I have no dump. But I know that turning on the wired pc triggered the crash.
At last this gives me a clue how where to look, since the dev machine is hooked up via wire, I know there was no mem issue, as I checked yesterday.
Thus this crash is either in the ethernet driver, or still a problem with k4.4 and the broadcom platform code. Thus time to hook up a little debug box to the serial connector.
I upgraded last night to 30645. I wired my pc to router and turned on, nothing happened. I'am still getting TX errors and drops on 2.4G but might be just my laptop drivers or something.
mgw2011 wrote:
@<Kong>
I'm afraid I'm totally at a loss now. Tried your latest build but WLAN stopped working. I am able to attach all devices but no internet and router's WebGUI not reachable from any device. Ethernet works fine.
FYI, I had a crash today, after 5 days of uptime. The bad thing is it crashed exactly at the time I turned on my development machine, thus I have no dump. But I know that turning on the wired pc triggered the crash.
At last this gives me a clue how where to look, since the dev machine is hooked up via wire, I know there was no mem issue, as I checked yesterday.
Thus this crash is either in the ethernet driver, or still a problem with k4.4 and the broadcom platform code. Thus time to hook up a little debug box to the serial connector.
I upgraded last night to 30645. I wired my pc to router and turned on, nothing happened. I'am still getting TX errors and drops on 2.4G but might be just my laptop drivers or something.
You might have a defective unit or power adapter. I Bought my R6400 last November and I'd no issues whatsoever using the following firmwares: Tathagata 27261, Kong 29875M, Kong 30370M & Kong 30465M. Options I always change: CTS Protection Mode (off), Preamble (auto), Wireless GUI Access (off), 3 Static DNS, MAC Address Clone (on), 6 static DHCP, All services off except DNSMasq with default settings, Impede WAN DoS/Bruteforce all on, 1 device have Access Restrictions to WAN always denied, 1 rule Port Forwarding & 14 on Port Range Forwarding, QoS WAN using HTB with FQ_CODEL (on), Enable Info Site (off), Remote Access all disabled & Allowed Remote IP Range set to two local devices.
Notes: On DD-WRT I always reset to defaults using web-gui prior upgrading, after upgrade I reset holding the reset button & never use other fw version configs. Since I switched to Kong I'd Implicit Beamforming on until last firmware switched on Explicit Beamforming instead & started using QoS since 29875M on 08-03-16. The room temperature always below 80F, ceiling fan on & the router is pretty much standing in the air ventilation wise. 2 WiFi devices & 3 wired devices are usually on daily, 2 wired are always on. We sometimes do: local streaming, netflix, gaming, torrenting & VoIP.
For the time being I give up here... just digged up my old Linksys device a WRT610N I used to use as a bridge.
Any advice welcome. Logfiles etc on request.
Alright... The old WRT610N router with a dd-wrt version from 2011 stopped working after 4 days with exactly the same symptoms. Very strange. Ping to router's address 10 sec and more. Error rate on 2.4 GHz rising steeply. Ethernet cable working (incl. Internet).
I've now flashed the original Netgear firmware and upgraded once to the latest version. So far no issues with the HW.
After paralysis by analysis and several desperate actions on the router side my take is that the problems were caused by the client's Ubuntu NetworkManager. I've replaced NM with WICD https://launchpad.net/wicd and have a stable 2.4 GHz WLAN since.
Despite the fact that the Netgear software run a little more stable, I was fighting with exactly the same issue (as described earlier) all the time. This means the 5 GHz connection worked fine and the 2.4 GHz connection was down 1-2 times per week and required a restart of the 2.4 GHz side of the router.
