Ewerton Posted October 7, 2021 Posted October 7, 2021 After giving this message the app no longer loads! Until restarting the router, it works for a moment then gives the message again!
Administrators Netduma Fraser Posted October 7, 2021 Administrators Posted October 7, 2021 Go to the System Information page and on the Rapp panel option menu change retries to 5 then reboot the router from the interface, wait 2 minutes then access and it should stay working for longer.
Ewerton Posted October 7, 2021 Author Posted October 7, 2021 ok I'll try the strange thing that this has never happened since last year I bought netduma R2 on pre sale!
Ewerton Posted October 7, 2021 Author Posted October 7, 2021 14 minutes ago, Netduma Fraser said: Vá para a página de informações do sistema e no menu de opções do painel Rapp, altere as tentativas para 5 e reinicie o roteador a partir da interface, aguarde 2 minutos e acesse e ele deve permanecer funcionando por mais tempo. It worked @thanks!
Ewerton Posted October 12, 2021 Author Posted October 12, 2021 The problem happened again!!! I've done everything, cleared browser cache, restart, router factory defaults, general reset through the small hole behind, reinstalled firmware, increased it to 5 in app panel, nothing solves! Note: I never had this problem in almost a year using R2!
Ewerton Posted October 12, 2021 Author Posted October 12, 2021 Just now, Ewerton said: O problema voltou a acontecer !!! Eu fiz tudo, limpei o cache do navegador, reiniciei, padrões de fábrica do roteador, reinicialização geral pelo pequeno orifício atrás, reinstalei o firmware, aumentei para 5 no painel do aplicativo, nada resolve! Nota: Nunca tive esse problema em quase um ano usando R2! @Netduma Fraser
Ewerton Posted October 12, 2021 Author Posted October 12, 2021 I believe someone from the Netduma team accessed my router remotely! Tue Oct 12 12:40:00 2021 kern.info kernel: [22785.890518] ash (2364): drop_caches: 3 Tue Oct 12 12:40:00 2021 cron.err crond[1404]: USER root pid 2364 cmd echo 3 > /proc/sys/vm/drop_caches Tue Oct 12 12:39:06 2021 user.warn com.netdumasoftware.devicemanag: aclassman failed to acquire LAN IP Tue Oct 12 12:38:43 2021 daemon.warn dnsmasq[2982]: possible DNS-rebind attack detected: redirect-test.flive.ixigua.com Tue Oct 12 12:37:59 2021 daemon.err cli.lua[2997]: conntrack v1.4.5 (conntrack-tools): 0 flow entries have been deleted. Tue Oct 12 12:37:59 2021 daemon.err cli.lua[2997]: conntrack v1.4.5 (conntrack-tools): 0 flow entries have been deleted. Tue Oct 12 12:37:59 2021 daemon.err cli.lua[2997]: conntrack v1.4.5 (conntrack-tools): 0 flow entries have been deleted. Tue Oct 12 12:37:59 2021 daemon.err cli.lua[2997]: conntrack v1.4.5 (conntrack-tools): 0 flow entries have been deleted. Tue Oct 12 12:36:37 2021 user.warn com.netdumasoftware.devicemanag: aclassman failed to acquire LAN IP Tue Oct 12 12:36:19 2021 user.warn com.netdumasoftware.devicemanag: aclassman failed to acquire LAN IP Tue Oct 12 12:36:18 2021 user.warn com.netdumasoftware.devicemanag: aclassman failed to acquire LAN IP Tue Oct 12 12:35:00 2021 kern.info kernel: [22485.830836] ash (27715): drop_caches: 3 Tue Oct 12 12:35:00 2021 cron.err crond[1404]: USER root pid 27715 cmd echo 3 > /proc/sys/vm/drop_caches Tue Oct 12 12:34:37 2021 daemon.warn dnsmasq[2982]: possible DNS-rebind attack detected: redirect-test.flive.ixigua.com Tue Oct 12 12:33:39 2021 daemon.warn dnsmasq[2982]: possible DNS-rebind attack detected: redirect-test.flive.ixigua.com Tue Oct 12 12:32:12 2021 daemon.warn dnsmasq[2982]: possible DNS-rebind attack detected: redirect-test.flive.ixigua.com Tue Oct 12 12:31:16 2021 user.warn com.netdumasoftware.devicemanag: aclassman failed to acquire LAN IP Tue Oct 12 12:30:00 2021 kern.info kernel: [22185.768186] ash (21461): drop_caches: 3 Tue Oct 12 12:30:00 2021 cron.err crond[1404]: USER root pid 21461 cmd echo 3 > /proc/sys/vm/drop_caches Tue Oct 12 12:27:07 2021 daemon.warn dnsmasq[2982]: possible DNS-rebind attack detected: redirect-test.flive.ixigua.com
Administrators Netduma Fraser Posted October 12, 2021 Administrators Posted October 12, 2021 It is an issue we've fixed in the next version and that isn't far off from being released now. We don't access routers remotely unless we have specifically said that's something we'll do - we also can't because you have IPv6 enabled and remote support is disabled by default unless you enable it. There isn't anything in the logs to indicate you've been accessed.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.