Netduma Jack B

@Achilles@SlamchezDo you both use network switches connected to the R3? If so what switches are they ?

@Slamchez Ok cool thanks, that likely rules out DHCP as the problem then. Have you got remote access enabled? I'd like to connect when the issue next occurs to try and debug

@Slamchez Ok that's super interesting, so if you manually set an IP, gateway on the device e.g through windows adapter options, you're still not able to get access to the internet? If you're statically set, are you able to ping the router at all from a command line? Ok that's also interesting. We've got a Series S here that might also cause an issue, I'll plug it into the one i've got running tests at the moment and see if this causes any issues. Maybe its some Power on lan issue that could be messing with the switch on the R3 (might also explain why we dont see anything in logs, and that wifi works fine)

Hi @Achilles Thanks for this, its very helpful. - get remote logging enabled for your router and check each day if you're experiencing kernel panics Could you enable remote access for Tech support through the settings and i can enable remote logging on your R3, There's no kernel panics happening, as they would already report to us, and your R3 would be rebooting. - have someone (potentially core developers) Monitoring your memory usage. In aggregate and also for overwatch daemon. Do this twice a day please - finally be have a fix for this already Binx to get Achilles an overwatch with tcp seq analysis disabled please" I dont think your issue is memory related as we would be seeing OOM's in the logs, which are not present. IMO it appears to be something with DHCP not renewing leases. If you could set a static IP one of your devices, and see if that disconnects, we can isolate the issue to DHCP. Another theory is that it could be DPI, so maybe try disabling that in your settings and see if the issue re-occurs

Hi @MuRF FuRY Thanks for the report we've recreated the issue. We'll get a fix for it in the next firmware.

How are you resetting the unit? You need to hold the pin down for ~10 seconds on the back and then leave the unit for 5 mins or so (Dont unplug). As @DARKNESShas mentioned above, there also could be a browser cache issue not allowing you to get access again, so either try clearing the cache through the F12 menu on your browser Or try a different device like your phone. Just a suggestion for the meantime. You could either connect your ISP's modem back in for a while and then connect the R3 underneath once getting through the setup.

Have you managed to get through the setup since factory resetting?

@the kappa convict Ah i think i see the issue. Are you using VLAN 101? And are you using PPPoE or DHCP/ static WAN? You should be able to get to the frontend by clicking on 'continue anyway'. Unfortunatley There's a bug in thee newest firmware that we missed in testing / beta with applying vlans on WAN. We'll be getting a new firmware out with the fix next week.

Hi, sorry to hear about the issue. Is the unit electrically rebooting e.g are the lights going on and off constantly? Or are you just unable to load the frontend? Whilst connected, could you go to http://192.168.77.1/cgi-bin/logs.txt and send over the logs from there. Thanks!

Hi @Authentik06What DumaOS version are you running? It should be in the top right corner when you open up the UI.

Hi Mate, I've spoken to a developer about this and hes said that this should only appear if you've got WebGL disabled in chrome, or perhaps you've disabled hardware acceleration in chrome?

Hi Murf, We're having trouble with recreating this issue ourselves, would it be possible for us to arrange a remote session (using teamviewer or anydesk) at somepoint next week to try debugging this issue with you? We've got a few ideas about how we can possibly cause it to happen. All we should need is a computer with the wireshark program installed to record the network traffic. Let me know what time/ timezone works for you. Thanks.

Hi All! We're looking for some DumaOS users in Germany to help out with QoS testing over the next couple of weeks. If you're interested please fill out the form below and I'll send you an email over the coming days detailing the testing. https://forms.gle/FkFMyZQGhuCCEgTr8 The tests shouldn't take much more than 30 minutes of your time! Any help would be much appreciated, Thanks!

Aditionally, I have a couple more questions after looking at your logs. Do you use the traffic controller application, if so do you have any rules set? Which firmware version and DumaOS version are you running? If you can make it to the DumaOS front end, its listed in the system information section Thanks

Hi Arthur, Which Telstra unit are you using? The model number will be listed on the bottom of the unit, Is it an LH1000, DJA0231, DJA0320 or a CobraXH?