Firmware: v3.0-r47911 std (12/23/21)
Router/Version: Netgear R7000 Kernel: Linux 4.4.294 #4782 SMP Thu Dec 23 04:11:41 +07 2021 armv7l
Previous: v3.0-r47900 std (12/20/21)
Mode/Status: AP wired and wireless / Up and running for 30 hours
Reset: Soft boot before and after upgrade
Temperatures: CPU 58.0 °C / WL0 45.3 °C / WL1 50.2 °C
Issues/Errors: Nothing significant
Updated via webif. No 'nvram erase' this time, last one was in July 2018 (r36325).
Upload and Download speeds are to ISP spec (500/500 Mbps).
Current basic R7000 setup (subject to change of course):
- Static WAN IP
- Shortcut Forwarding Engine: CTF, Flow Acceleration: Disabled
- STP - Enabled
- IPv4 only, both WAN and LAN
- LAN DHCP Enabled
- Not currently forwarding any ports
- Wireless: AP, Regulatory Domain = CANADA, wl0 Mixed (ch. 6), wl1 AC/N-Mixed (ch. 36, VHT80), AES
- 1 wireless VLAN on wl0
- SNMP disabled, SSH enabled, Telnet disabled
- Firewall enabled, Log Level high
- Syslog: to local server. klogd: disabled.
- USB support - Off
- No custom scripts
- No: ttraf, Tor, VNC, Zabbix, VPN, Radius, OpenVPN
- No: UPnP, DMZ, QoS
- No: Samba, CIFS, JFFS2, miniDLNA, Entware, Optware _________________ Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7
@kooper2013: And everything that relies on check_ps (and process monitor) that goes askew will be because cron is disabled. Is this over wireless or something? It would help to know all the details of the issue and have screenshots of all applicable settings to see where things are going awry.
LOG attached, diverted to USB. ntp disabled, cron enabled.
Screenshots won't help, I'm quite sure. The router is not reachable by WLAN nor LAN, no pings returned.
Last line is always
Jan 1 23:16:01 home user.info : [upnp] : maybe died, we need to re-exec it
Set time to 23:50 manually and waited. So disregard the times in the LOG. The router will stop as soon as 0:00 is shown in GUI (+/- 1s).
If left in this status over night, the router is cold, as if it switched itself off.
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Sun Dec 26, 2021 22:54 Post subject:
Going by your log, wireguard requires ntp to be enabled. It looks as if dnsmasq is in a restart loop - not sure if that's ntp or dns failure / wanup failure / config problem. Also, I don't know why you have upnp enabled, but unless there is a specific reason why it's enabled, I would disable it. Seems like worst case is reset, hard reset, and start from scratch. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Going by your log, wireguard requires ntp to be enabled. It looks as if dnsmasq is in a restart loop - not sure if that's ntp or dns failure / wanup failure / config problem. Also, I don't know why you have upnp enabled, but unless there is a specific reason why it's enabled, I would disable it. Seems like worst case is reset, hard reset, and start from scratch.
WireGuard doesn't seem to require real time (first thing I checked).
I know upnp is unsafe. It is only enabled in my internal network, not available from outside.
I'll try older builds, now that I'm able to reproduce it without waiting for real midnight. But little time these days...
Router/Version: NetGear R7000
File: netgear-r7000-webflash.bin
Firmware: DD-WRT v3.0-r47911 std (12/23/21)
Kernel: Linux version 4.4.274
Mode: Router, wifi/eth, 2 subnets, 2x WG tunnels
Previous: r47074
Reset?: N
Status: Working after reboot
1. I run 2 WG tunnels to different endpoints at the same VPN that also use the same key. In previous version the "WireGuard Status (F5 to refresh)" section just displayed details of the first tunnel, for both first and second tunnels. It was only a cosmetic problem, the connection details were correctly shown in the syslog. BUT - it is nice that it is fixed now !! Thank you Each tunnel now shows its own details in that section.
2. Both my WG tunnels use Policy Based Routing (PBR). That section has now been expanded with more options/granularity. My own PBR details did not carry over to the new version (this is expected, and there is a post about it ). For me, it was just easier to re-enter those details into 47911. And - also to disable "Query DNS in Strict Order" on the Services page...
Over the last few months, I have had some stability problems with my 2nd WG tunnel. It seems to stay up for about 3 weeks and then requires a bit of a reset to keep going. The first WG tunnel does not have those problems. Anyway, I am curious to monitor over the next couple months to see if that changes/improves with this new version. EDIT - I suspect the VPN provider is at fault for that.
MY thanks to all the devs and all those who tested #47911
Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Mon Dec 27, 2021 11:29 Post subject:
kooper2013 wrote:
WireGuard doesn't seem to require real time (first thing I checked).
I know upnp is unsafe. It is only enabled in my internal network, not available from outside.
In your attached log, the following entry did show up multiple times:
Code:
Jan 1 23:01:37 home user.info root: WireGuard stopped waiting after 91 seconds, trying to set routes for oet1 anyway, is there a connection or NTP problem?
Better assume all kinds of encryption protocols need correct time. Unbound DNS definitely needs it.
Did you setup NTP time client by entering a domain name? Try IP addresses, or leave the field blank!
There were multiple mstpd errors as well... I dunno that one. Per kp69 said, maybe you should just disable uPnP to reduce the amount of logging.
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 18 Mar 2014 Posts: 12835 Location: Netherlands
Posted: Mon Dec 27, 2021 12:46 Post subject: Re: R7000
seanPH wrote:
Router/Version: NetGear R7000
Over the last few months, I have had some stability problems with my 2nd WG tunnel. It seems to stay up for about 3 weeks and then requires a bit of a reset to keep going. The first WG tunnel does not have those problems. Anyway, I am curious to monitor over the next couple months to see if that changes/improves with this new version. EDIT - I suspect the VPN provider is at fault for that.
MY thanks to all the devs and all those who tested #47911
Three weeks without a disconnection? Wow that is something which is very rare with my provider (Keepsolid).
I use the fail over setting so that the next tunnel will start when the first goes down.
I will not go into detail but WireGuard when implemented on a device without a RTC needs the correct time.
That is what the log is trying to tell you
Hi @egc, @kp, @mwchang,
this is an older issue. I went back to r47171, which also stops at 0:00. Then I decided to give up.
Now cron is disabled, ntp (and upnp) enabled on r47911 and it doesn't stop at 0:00. Don't know what the problem is.
Remarks:
ntp was just disabled for the tests (I needed to set time to 23:55 to wait just 5min rather than 24h).
wg works at least for a few minutes with the wrong time.
The spam in the log about upnp isn't bothering me. _________________ 3xBuffalo WLI-H4-D1300
1xBuffalo WZR-D1800H
1xBuffalo WHR-HP-G300N
1xBuffalo WHR-1166D (stock f/w)
1xAsus RT-AC87U
1xAsus RT-AC88U
1xTP710
Router/Version: ASUS RT-AC68U rev B1 (AC1900)
File: asus_rt-ac68u-firmware.trx
Kernel: Linux 4.4.294 #4782 SMP Thu Dec 23 04:11:41 +07 2021 armv7l
Previous/Reset: r47900 / No reset, upgraded via GUI (https)
Mode/Status: 1 AP; 3 Client Bridges, all OK, up 7 hours
Issues/Errors: No issues; Working as configured
Thank you BS and all of the other devs who help out to make this firmware great. _________________ ASUS RT-AC3100 AP Merlin 386.12_4
ASUS RT-AC68U Media Bridge/Merlin 386.12_4 (x2)
ASUS RT-AC68U AP r54604
ASUS RT-AC68U Gateway/AP r54604
Edgerouter-4, v2.0.9-hotfix7
Router/Version: Asus RT-N66U ver. B1
File/Kernel: DD-WRT v3.0-r47911 mega (12/23/21) / Linux 4.4.294 #13256 Thu Dec 23 05:33:28 +07 2021 mips
Previous/Reset: r47911
Mode/Status: Router/DHCP, for three wireless (printer, phone, laptop) and two wired clients (nas, desktop). 2.4GHz (NG-Mixed) and 5.0GHz (Mixed), CPU 600 MHz (default), Temperatures WL0 41.7 °C / WL1 42.0 °C
Issues/Errors: Every few days (two in last instance) the router will lock up. No webui, internet, or LAN. Used off/on button to reset. No known cause. Config and logs attached.
Factory reset after upgrade. I paste my router settings into a telnet session then hit save on each of the applicable webgui pages then hit apply settings.