Whenever I try to restore configuration with this build the server terminates the connection and settings are not restored - but do appear in the admin interface until you reboot. If you save settings, they are partially applied but the system get into a very unstable state.
Hopping back to the 33675 and then restoring then upgrading works.
@kong
Do you have any tips / instructions on how to configure ipsec vpn.
Looking through the forum no one was able to configure ipsec vpn server since you released it a while ago.
Also BS and Kong great work, thank you. _________________ Netgear R9000 main router
RAX80 as AP
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Thu Feb 15, 2018 19:26 Post subject:
Router Model Netgear R7000
Firmware Version DD-WRT v3.0-r34900M kongac (02/11/1
Kernel Version Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l
update: via ddup
reset: NO
status: operational
errors: ntp time, authentification fail... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
@kong
Do you have any tips / instructions on how to configure ipsec vpn.
Looking through the forum no one was able to configure ipsec vpn server since you released it a while ago.
Also BS and Kong great work, thank you.
CloneVince wrote:
Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved.
_________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
File: No real Point in linking official Kong PTB repo as next PTB will overwrite this file... (but HERE is link to my personal repo) or not, i'm too lazy to maintain that historial Kong FW repo
File Name: dd-wrt.v24-K3_AC_ARM_STD_128K.bin
MD5: a1fe90a23803133272d582d6678859ee
I'm using R6400 as an AP (Ethernet-->WiFi). Seems with v3.0-r34900M, R6400 is consistently locking up. I've had to power-cycle-reboot about a dozen times now. Since it requires a power-cycle reboot to get back online, there aren't any logs to see what is happening. Don't mind beta-testing at all, but since this issue is a lock-up requiring power-cycle, I need to reload something that won't require physical power-cycling. (i.e., I'm good testing even if a bug requires a remote reconfig/reboot/etc., but can't keep having to physically power-cycle re-boot... The R6400 sits behind my Home-Theater Center Channel Speaker in my Family Room, and it is a pain to have to keep removing the speaker and get inside the cabinet to power-cycle. )
So, I Re-loaded Firmware: DD-WRT v3.0-r33675M kongac (11/03/17) today via GUI, and so far seems stable.
I'll report back after a few days if I don't have any issues with 33675M.
Thanks Kong for all your hard work! I've moved my R8000, R7800, and R6400 to your builds. R7800 and R8000 are both on 34900M, and seem fine. I've just replaced my R7000 with R8000 as my main router (Wi-Fi disabled), and am using R6400 and R7800 as Wi-FI APs. (R7000 remains on NETGEAR stock offline as a spare, in case things go wrong with R8000 DD-WRT.) This is great, and now I can implement all the features NETGEAR Stock FW doesn't support, but always wished for. VERY Happy camper here...
SIggy.
@Siggyceline
I have been up almost 3 days now, no issues... of course YMMV, and I've been "riding dirty" (not a clean flash, no reset). _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Posted: Sat Feb 17, 2018 17:11 Post subject: 34900M
Router Model Netgear R7000
Firmware Version DD-WRT v3.0-r34900M kongac (02/11/1
Kernel Version Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l
Update 33675M
Reset yes (first time)
OpenVPN
Samba
MiniDLNA: Media Center disappears
Not many errors
Frontier FiOS 50-50 service
Slowed down by NordVPN
Screenshot-2018-2-16 Frontier Internet Speed Test Tool.png
1x AP/Router: Netgear R8500 (AP)
Firmware: DD-WRT v3.0-r34900M kongac (02/11/1
Kernel: Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l
Completely fresh install, using .chk file.
2x Routers: Netgear R7000 (Each a Client Bridge for downstream wired devices)
Firmware: DD-WRT v3.0-r34900M kongac (02/11/1
Update with hard reset, but no "erase".
R8500: With Active Cooling (USB Fan Underneath):
CPU 46.9°C, WL0 44.0°C, WL1 40.2°C, WL2 42.5°C
Trivial error counts on wireless (100% good)
2.4G with low-bandwidth PCs.
5.0G to client bridges, they support 4K TVs and video servers boxes, at high bandwidth (5.0G A/C only). I couldn't get wireless Bridge to work.
R7000s have Passive Cooling only: CPU 54.7 °C, WL1 43.0 °C Zero errors Transmit/Receive.
I'm delighted. My thanks to Kong and BS!
Last edited by rickst29 on Sun Mar 11, 2018 4:06; edited 1 time in total
on R6400 (others had issues on this device with this buildabove)
I reset/reconfigured from scratch and was up for a day or two before "ddup -flash--latest" to current. No issues noted, FWIW. _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE