Router: Netgear R7000
Firmware: DD-WRT v3.0-r32780M kongac (07/21/17)
Kernel: Linux 4.4.77 #375 SMP Fri Jul 21 12:02:04 CEST 2017 armv7l
Status: Working
Reset: No
Previous: 32735
Errors: Yes
Upgrade went smooth, but router locked up after 20 minutes. SFE is disabled.
My R7000 up time 13,5 hours without any locked up.
Status: Working
Reset: YES
Previous: 32735
Only locked up ones stright after flash. Clear nvram, power on/of and no issue then.
Settings are by default. SFE is anabled, using USB storage with samba.
Router: Netgear R7000
Firmware: DD-WRT v3.0-r32780M kongac (07/21/17)
Kernel: Linux 4.4.77 #375 SMP Fri Jul 21 12:02:04 CEST 2017 armv7l
Status: Working
Reset: No
Previous: 32735
Errors: Yes
Upgrade went smooth, but router locked up after 20 minutes. SFE is disabled.
After 20min, means you have some other problem, e.g. bad nvrm params from other firmware, custom stuff running or just simply setup something that eats up ram. E.g. attach usb drive enable minidlna, which depending on setting store it's index db in ram. With lots of files, the db gets large and eventually eats up ram. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
FYI, in my build qos is enabled even if sfe is turned on I have 3 x A+ on dsl reports with sfe + qos and I do not need download limit.
@Kong, SFE interferes/breaks vlan setup between Router (R7000) & AP (R6300v2).
Symptoms:
- Device behind VLAN3 through the trunk port on R6300v2 AP to R7000 lost internet connectivity.
- The same VLAN3 device is successfully getting assigned a VLAN3 IP address, so only the WAN (or NAT?) access is affected.
Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Sat Jul 22, 2017 9:44 Post subject:
egc wrote:
Router Model: Netgear R6400
Firmware Version: DD-WRT v3.0-r32780M kongac (07/21/17)
Kernel Version: Linux 4.4.77 #375 SMP Fri Jul 21 12:02:04 CEST 2017 armv7l
Upgraded: from 32735M via ddup --flash-latest (thast version crashed)
Reset: Yes, Erase NVRAM
Status: Up and running for 15 min, basic setup as AP.
Errors: one GUI lockup, had to do stopservice httpd/startservice httpd via telnet.
Now running SFE tests will report back
Big Thanks to Kong and BrainSlayer!!
Did some further testing
No lock up with SFE on so far.
OpenVPN client on PIA working with and without SFE
But:
OpenVPN and PBR does not work with SFE on ???
The clients outside the PBR range do work but webrowsing via the VPN is somehow blocked. tracert does work, e.g. I could run tracert from my client and also resolve DNS so it is not a routing or DNS problem but SFE with PBR seems to block http traffic??
FYI, in my build qos is enabled even if sfe is turned on I have 3 x A+ on dsl reports with sfe + qos and I do not need download limit.
@Kong, SFE interferes/breaks vlan setup between Router (R7000) & AP (R6300v2).
Symptoms:
- Device behind VLAN3 through the trunk port on R6300v2 AP to R7000 lost internet connectivity.
- The same VLAN3 device is successfully getting assigned a VLAN3 IP address, so only the WAN (or NAT?) access is affected.
Please let me know if you'd like me to open a ticket
SFE has nothing to do with vlans and you can just disable SFE and the basic setup page.
Understood. I had it disabled already. There is a strong correlation that I do not understand between enabling SFE and VLAN3 client (a gateway for connected thermostats) losing WAN side connectivity:
It went by this sequence
- SFE disabled: VLAN3 client talking to WAN
- SFE enabled + reboot: no issue in first ~5mins, but VLAN3 client disconnected from WAN after (retaining VLAN3 IP)
- SFE re-disabled + reboot: VLAN3 client connected to WAN again
So somehow enabling SFE affects VLAN3 connectivity in some way. I am disabling SFE for now (I was only testing it anyway; and as you said, I don't need it for VLAN). Is there anything you'd like me to test/investigate?
Router: Netgear R6300V2
Firmware: DD-WRT v3.0-r32780M kongac (07/21/17)
Kernel: Linux 4.4.77 #375 SMP Fri Jul 21 12:02:04 CEST 2017 armv7l
Status: Working
Reset: No
Previous: 32735
Errors: Yes
Running as a client bridge, so SFE is not available.
Up 17 hours without lockup.
Still not NTP date&time after a reboot.
The date stays at 01 Jan 1970.
The date problem has been in every version after 32170M.
I hope it can be fixed soon.
I'm getting a lot of random problems, WAN and LAN. It's hard to pinpoint what's going on but my R7000 is very unstable. The GUI crashes often, but most of the clients are having random WAN access issues. The Windows 10 server that is hard wired is getting round trip ping times to 8.8.8.8 in excess of 200+ ms, then back down to 8ms (which is what is normal for my environment).
What is the latest stable build? I've never had to "roll back", can I just download the firmware from KONG's FTP then flash via the GUI, or should I use telnet?
Posted: Sat Jul 22, 2017 16:03 Post subject: Re: Kong's DD-WRT test build 32780M - 2017/07/21
Router: R8500
Firmware: 32780M -2017/07/21
Kernel: Linux 4.4.77
Status: intermittent drop of Internet connection
Reset: Yes
Errors: Drop Internet, intermittent web interface access
I'm suspecting that dd-wrt is not compatible with my ISP (Charter/Spectrum). My Internet connection finally came to a hold and after booting the Router a few times, it wouldn't acquire an IP address. I even took an step back and installed the dd-wrt Firmware released on 2017/06/11 and I was experiencing intermittent WAN connectivity with it as well.
I was obligated to go back to stock firmware, so further testing is not possible at this moment.
Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Sat Jul 22, 2017 16:14 Post subject:
seanvree wrote:
I'm getting a lot of random problems, WAN and LAN. It's hard to pinpoint what's going on but my R7000 is very unstable. The GUI crashes often, but most of the clients are having random WAN access issues. The Windows 10 server that is hard wired is getting round trip ping times to 8.8.8.8 in excess of 200+ ms, then back down to 8ms (which is what is normal for my environment).
What is the latest stable build? I've never had to "roll back", can I just download the firmware from KONG's FTP then flash via the GUI, or should I use telnet?
Actually this build is rather stable apart form the occasional GUI glitch. You should consider other flaws.
Did you erase nvram and put settings in manually?
Kong's regular ( http://www.desipro.de/ddwrt/K3-AC-Arm/ ) build has been running also stable on my R6400.
Use telnet and ddup, that is the easiest. For options ddup --help. --flash-latest will get you the test build, you have to use --flash-remote URL
@EGC
Oh, wow, I didn't know "DDUP --flash-lastest will give you test builds. So, to get the latest stable build I would input "DDUP --flash-remote http://www.desipro.de/ddwrt/K3-AC-Arm " ? Or what would the be "remote" URL for KONG's R7000 firmware ?
Joined: 18 Mar 2014 Posts: 12884 Location: Netherlands
Posted: Sat Jul 22, 2017 16:59 Post subject:
seanvree wrote:
egc wrote:
Actually this build is rather stable apart form the occasional GUI glitch. You should consider other flaws.
Did you erase nvram and put settings in manually?
Kong's regular ( http://www.desipro.de/ddwrt/K3-AC-Arm/ ) build has been running also stable on my R6400.
Use telnet and ddup, that is the easiest. For options ddup --help. --flash-latest will get you the test build, you have to use --flash-remote URL
@EGC
Oh, wow, I didn't know "DDUP --flash-lastest will give you test builds. So, to get the latest stable build I would input "DDUP --flash-remote http://www.desipro.de/ddwrt/K3-AC-Arm " ? Or what would the be "remote" URL for KONG's R7000 firmware ?
