Jump to content

Netduma Fraser

Administrators
  • Posts

    87496
  • Joined

  • Days Won

    1946

Everything posted by Netduma Fraser

  1. Added https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/
  2. https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/
  3. Re-upload the firmware from that page and then see if its more stable after that please
  4. We don't give out any details about future updates or products and I suspect Telstra would be the same regarding any products until they were ready to announce them but of course we are continuing our partnership and continue to work on updates for the supported products.
  5. Good to hear! As above you can upgrade and you shouldn't get the issue as long as you don't factory reset but if you just want to be safe then probably best to stay on the firmware you're on.
  6. I don't know what the blue/yellow ports correspond to on the ATT router so I can't answer that. You don't need to change those advanced settings options. You can leave the lease time at the default for now. Are ALL devices connected to the R3? Have you entered your speeds into the router? How have you setup Congestion Control? How have you setup SmartBOOST? What game are you playing? What platform are you playing on and how is it connected, via ethernet or WiFi? How have you setup the Geo-Filter?
  7. Good advice above - what do you actually see when trying to access the interface from a web browser?
  8. Good to hear you've tried the workaround, that does seem to fix it for those that have tried. In regards to how you were setting it up above then if the HG is handling PPPoE then the static details on the R3 would be local, not using your public IP details. You can check on the HG for the IP that it's giving the R3. Likely though for DHCP to work set it all up then reboot the HG, wait 2 minutes then reboot the R3, wait 4 minutes and I suspect that'll sort it.
  9. You should connect the R3 WAN/blue port to one of the ATT LAN ports for it all to work correctly
  10. Due to your location the biggest factor for you is going to be the routing your ISP is using, if you've got all your local congestion sorted and you've double checked that in game you're getting similar pings while directly connected to your ISP modem/router then that will be the issue. In that case if it is, I don't normally recommend it but something like Exitlag for example may help you get better routing to the game servers and allow for a better ping.
  11. We don't have any specific recommendations for a router to use in this setup but any should work just fine in that scenario!
  12. You need filtering enabled otherwise it's not doing any filtering to your desired area. Then it's likely Geo-Latency is enabled so disable that then once you've made those changes you should be able to filter.
  13. The logs don't seem to indicate why it's happening just that it is losing the connection. Is the Draytek a pure modem or can you have it handle PPPoE instead of the R3 to see if you then lose connection in that configuration?
  14. Disabling the firewall completely would be the disable entire firewall option but you don't need to do this, putting the router in the DMZ bypasses the hub firewall for that device
  15. There isn't much else I can suggest, you have another topic on the matter where we're waiting to remotely upgrade you to see if that will help, another topic doesn't mean I have any more solutions for you. I'll check in with the team on Monday
  16. No ETA but I've given you Early Access to try it, the latest version is quite stable https://forum.netduma.com/forum/151-netduma-r3-early-access/
  17. Buying second hand is always a risk, it's likely they were having issues which is why they sold it in the first place, I'd suggest you return it to them utilizing the return policy on the applicable marketplace. It's almost impossible for me to give you a reason for an issue occurring when I have no idea what kind of state it was in initially even if it seemed to be working fine. As per your other topic there isn't any specific recovery procedures and we're waiting on a developer to remotely upgrade you. It's not bricked as you are able to access the interface to get logs but it does appear you have an unfixable kernel error that even if you get better access to the router features will still likely cause you issues so I would highly suggest you return it.
  18. Added https://forum.netduma.com/forum/144-netduma-r2-early-access/
  19. The R2 was our first foray into our own hardware and we've learnt a lot since then hence the R3 is a lot more robust. You are also on an Early Access version so there can be issues as you've seen. I will come back to you once I know more.
  20. If you haven't already do a factory reset on that version, it's quite a big jump. We're aware Ping Optimizer isn't 100% reliable currently. It can work you just may need to try again later. In the meantime you can adjust Congestion Control manually to achieve the same effect which can be found in Ping Optimizer > Advanced.
  21. Yes you'd put 0. The ISP timeout must be set to 5 then, if they're otherwise unhelpful perhaps they could change the timeout for you just to see if the issue improves
  22. On your ISP router set a static/reserved IP for the R3 then on the R3 in Settings > DHCP > Add Rules > Select Device > Save. Do that each device you're noticing the disconnects/issues with. Then in DHCP > Advanced change the lease time to 10000, save, reboot the router from the interface and see if it happens again please.
×
×
  • Create New...