All Activity

I have to wait until I get another netduma. I mostly play the finals thats the only reason i was wondering

Não é a primeira vez q isso acontece e nunca ninguém resolve, acho que eles fabricaram com algum bug e não conseguem resolver.

We need wifi calling turned on for our android phones to work in our area. When I switched from our ISP's router to the R1for better gaming, the cell phones would not make phone calls with wifi calling turned on. I assume it's a setting in the R1, or the phones are communicating wrong with the router. With my limited knowledge of both I will need all the advice you can give. Thanks

Troquei o cabo é cat6 original do Mercado livre

Ola Rodolfo sou do RJ TB vi q vc é do RJ TB. Tente trocar o cabo e deixa seu qos em 100% só pra ver se melhora algo na velocidade.

20260128_123244.mp4 20260128_123154.mp4

Toda semana eu passo por esse tipo de problema e ninguém até hoje conseguiu me ajudar, eu tenho perda de velocidades toda semana e não é um problema da provedora e sim do R3, r3cebo 500 m3gas de download e 250 de upload e essas são as velocidades que o R3 me entrega, já reiniciei várias vezes padrão de fábrica, resetei várias vezes e nada, por favor se alguém tiver uma solução agradeço, recebo uma conexão com ipv4 fixo e tenho uma ONU em modo bridge. 20260128_121205.mp4

Anyway just this error in its log: `cli.lua: goto outils hook failed` PS: I didn't read it properly, and yes, I use AI to help me with my tasks to save time, both professionally and personally, like many admins and sysadmins. But as you know better than anyone, if you don't understand it, unfortunately, AI isn't very useful, especially in the world of IT. If you still have doubts, I can send you a screenshot of my qualifications.

Okay, so for you, "problem" rhymes with "breakdowns" in the IT world, which you clearly don't know much about, especially here, since it's supposed to be a gaming router, so latency and other factors should be optimized as much as possible. Well, in these logs, that's not the case. The router, especially the processor, is working unnecessarily and haphazardly, which affects the stability of the system and therefore the router... Basically, just because your car starts and runs doesn't mean it doesn't have a problem... But since it's you, I can understand.

@18RayFYour case is uncommon but not unheard of. What stands out is that you're using DHCP, which typically operates with an MTU of 1500. However, your ISP is clearly providing an MTU of 1492, commonly seen with PPPoE, and when the MTU exceeds the limit set by the router, fragmentation occurs, which can lead to issues like the one you experienced. In other cases, this might manifest more noticeably, such as through packet loss. It is not an issue on the router side as the router uses the most common configuration. @KinGzzyMost of what you said isn’t even an issue; the time going backwards is literally just the DPI reading the packets, and as you are using the AI, which you are, it doesn’t tell you the most obvious thing, which is that IPv6 is disabled.

No, you can't do anything; you have to wait for him to pass the information on to a Firmware (Embedded) Developer.

Hi Thanks for that Is there anything I can do to fix this ? Adjust DHCP lease time etc or just wait till new update ?

Hi According to the logs, your router is suffering from major software instability. 1. IPv6 configuration problem (odhcp6c) 2. Script and TLS errors (cli.lua) 3. Time instability (Time went backwards) 4. Very frequent DHCP renewal (udhcpc: lease obtained, lease time 600) 5. Memory cleanup (drop_caches) USER root cmd echo 3 > /proc/sys/vm/drop_caches 6. Processor instability (Time went backwards) 7. The conflict with "DPI" (Deep Packet Inspection) In your logs, I also see: user.info dpiclass-daemon: Daemon shutdown user.warn overwatch: Changing category of appid=161... to VPN Your router is suffering from major software instability. This isn't just a minor connection error; it's the DumaOS system crashing because it's trying to handle too many things at once.

Could you uninstall the app, restart the phone, install the app - but don't open it, restart the phone then try again please?

IOS 26.2.1 App Version is 1.3.26 Its appears to be the same thing as the video i provided earlier, but ill attach a fresh video to this post- just an instant crash after opening. ScreenRecording_01-27-2026 15-49-08_1.MP4

What iOS version are you currently on? Could you provide a video of what you're seeing? Also verify in settings it's on the correct app version

Yes a MTU mismatch could cause it, glad to hear you found the cause

Hey Luke, thank you for reaching out. Unfortunately it did not fix it, I just reinstalled the app.

Cant connect direct to ONT as PC is in different room and no cable long enough unfortunately , i realised there was a MTU mismatch from PC and Router could it cause this as i changed router to 1492 as PC already had that and its working fine now ? These logs were yesterday after it happened and today after I changed the MTU on Router while attempting to load up also . R3_2026-01-27T18_49_20.363Z_logs.txt R3_2026-01-26T22_39_49.174Z_logs.txt

If they're directly after the issue happens and before a reboot then yes. Do you get the same issue with the PC connected directly to the ONT?

I’ve got logs already if you would like me to attach

Hi, please try the latest app version (1.3.26) released today. We were able to fix some big incompatibility issues with iOS 26, so hopefully your problem is resolved, if you were still encountering it.

Hi all! App version 1.3.26 is now available on the App Store & Play Store for iOS and Android. Not many changes since 1.3.20, but here they are: Fixed iOS 26 can't interact with views Fixed Ping Heatmap doesn't display servers with longitude of 0 Updated to use new Netduma Logo The biggest issue was an incompatibility with iOS 26, which was causing a lot of issues. This release should resolve those issues.

Make the issue happen and then grab the logs please. Also if you connect via ethernet to the ONT do you get the same issue?

Nope