Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Mon Jun 13, 2022 7:38 Post subject:
no information provided about, router, settings or current firmware will drop the level of help down to zero...
-router can freeze due to many things:
-bad PSU
- "connect into them remotely and the connections are down"
inappropriate remote access could block/freeze the router if too many attempts are done...
-end of its capacitors life
-bad settings
-out of nvram
-bad firmware flash or buggy _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 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 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 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
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon Jun 13, 2022 11:32 Post subject:
You have in Administration tab -> Keep Alive tab option to reboot at a fixed interval default 3600 seconds = 1 hour or at your choice any other interval or At a set Time.
However this is limited to those options and does no check any connectivity.
To do a reboot based on something else, you would need to make a script and call that script via Cron. It's possible but you would need to get creative with this script.
See topic on wiki https://wiki.dd-wrt.com/wiki/index.php/Scheduled_reboot and something you should research, for my part I apologize for not giving you a script solution, I dont teach bash scripting either as there are plenty well documented resources on the web which many moons ago I read and still use for reference when writing bash script for all sorts.
That said you may get lucky and someone will do your homework for you, but dont count on it
Or get creative and install Teamviewer for remote access to this machine connected to the router and use that to reboot the router, assuming of course the WAN connection hasn't dropped and Teamviwer works.
Or some other kind of VNC, I used and contributed to the ultraVNC project many moons ago and dd-WRT has a nifty VNC repeater which helps with regular VNC connections which works with ultraVNC or use to anyway.
And thinking about it, it maybe possible depending on router (flash space allowing) to install via Entware or compile some VNC server and run that in DD-WRT and then you just use a client to connect to the VNC server running on the router. Me I would prefer to compile it myself since Entware packages are often outdated and maintain by 3rd unknown parties who I dont know who they are therefore dont trust.
If you compile it would be better cross compiling on a Linux VM since compiling on the router directly will take forever and consume all CPU/RAM resources.
That said, by now and like Alozaros stated, you should know that we need router and current firmware information when this type thread is opened (We always dont let other community members forget either and you have been around for a bit ).
Latest DD-WRT builds are always getting updated with various bug fixes and running older build could have some unresolved issue as well as unresolved know security issues. So you need to tells us, if it fixes or not your issue on these latest builds.
Ill assume you know where to find latest dd-wrt by now.
The only other two options for keepalive is the proxy/connection watchdog (WAN) and the WDS watchdog, which do check connectivity. What solution are you looking for, exactly?
_________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
thanks for the reply,
KEEP alive would have been a good idea, but i think the issue is caused incoming WIFI only. cable LAN works but the wifi devices cannot connect.
i dont think the constant reboots will be a solution, knocking the network offline
the-joker wrote:
You have in Administration tab -> Keep Alive tab option to reboot at a fixed interval default 3600 seconds = 1 hour or at your choice any other interval or At a set Time.
However this is limited to those options and does no check any connectivity.
To do a reboot based on something else, you would need to make a script and call that script via Cron. It's possible but you would need to get creative with this script.
See topic on wiki https://wiki.dd-wrt.com/wiki/index.php/Scheduled_reboot and something you should research, for my part I apologize for not giving you a script solution, I dont teach bash scripting either as there are plenty well documented resources on the web which many moons ago I read and still use for reference when writing bash script for all sorts.
That said you may get lucky and someone will do your homework for you, but dont count on it
Or get creative and install Teamviewer for remote access to this machine connected to the router and use that to reboot the router, assuming of course the WAN connection hasn't dropped and Teamviwer works.
Or some other kind of VNC, I used and contributed to the ultraVNC project many moons ago and dd-WRT has a nifty VNC repeater which helps with regular VNC connections which works with ultraVNC or use to anyway.
And thinking about it, it maybe possible depending on router (flash space allowing) to install via Entware or compile some VNC server and run that in DD-WRT and then you just use a client to connect to the VNC server running on the router. Me I would prefer to compile it myself since Entware packages are often outdated and maintain by 3rd unknown parties who I dont know who they are therefore dont trust.
If you compile it would be better cross compiling on a Linux VM since compiling on the router directly will take forever and consume all CPU/RAM resources.
That said, by now and like Alozaros stated, you should know that we need router and current firmware information when this type thread is opened (We always dont let other community members forget either and you have been around for a bit ).
Latest DD-WRT builds are always getting updated with various bug fixes and running older build could have some unresolved issue as well as unresolved know security issues. So you need to tells us, if it fixes or not your issue on these latest builds.
Ill assume you know where to find latest dd-wrt by now.
im trying to find solution for a problem of the WIFI will stop responding to connections. sometimes its all devices sometimes its random device. its a random issue, the lan still works.
and before people ask the firmware and router type. it don't matter. as this happens on different versions and makes and models. im looking at a way to trouble shoot not a guide to fix XYZ
something causes the wifi interface to glitch, until a reboot gets it back online
dale_gribble39 wrote:
The only other two options for keepalive is the proxy/connection watchdog (WAN) and the WDS watchdog, which do check connectivity. What solution are you looking for, exactly?
and before people ask the firmware and router type. it don't matter. as this happens on different versions and makes and models. im looking at a way to trouble shoot not a guide to fix XYZ
something causes the wifi interface to glitch, until a reboot gets it back online
Too late. Someone already went there.
Alozaros wrote:
no information provided about, router, settings or current firmware will drop the level of help down to zero...
Given the amount of variables involved, it would be helpful to know further details. Other than what has already been given as possible factors, since this is strictly a wifi issue, there's really only one place to look and that is how your AP interface(s) is(are) configured. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
so for example. when the problem occurs
what can i look at in the router? Syslogd ?
logs? status? to narrow down what has stopped working?
for example. DHCP problem, or AUTH, or something crashed?
under status> "Active Clients"
"Connections" tab. what does this represent exactly?
i notice some devices can be hundred or thousands
99% of the time everything works good
i trying to find what is triggering the issue
_________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio