Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 06/27/25 in all areas

  1. Hi @Netduma Fraser & @Krush, thanks a lot for the quick feedback! Good to hear that this is a known topic and that improvements are being worked on regarding PPPoE performance on the R3. I’m definitely looking forward to future firmware updates in this regard. I’ll test this setup and monitor both speed and latency. If there are any beta updates or settings that could improve PPPoE handling on the R3 directly, I’d be happy to try them and provide feedback! Thanks again – I appreciate the support!
    2 points
  2. We are aware speeds are slightly slower using PPPoE and we'll improve that if we can. Otherwise you can put the R3 in the exposed host on the Fritz instead and have the fritz handle PPPoE as mentioned above and then you should get better speeds through the R3.
    2 points
  3. talbyfish

    VDSL modem

    thanks al give it a go
    1 point
  4. Okay interesting, thanks for letting us know, I've only heard of a couple instances since the R3 launch so perhaps a bad batch from the manufacturer
    1 point
  5. He'll be looking into it more tomorrow I believe
    1 point
  6. So does that mean that by swapping it out for a different cable you've had a better experience?
    1 point
  7. We've got the IPv4 address so we'll try it, it's the same IP we tried last time that we were unable to access but maybe now you've run through the process again it will work.
    1 point
  8. Make a new topic with the answers to these questions and we can go from there
    1 point
  9. I posted in the topic just over a week ago about it: We just need to do a little more testing on this (last thing we want is for this situation to happen again), tie up a few loose ends and then it should be good to release to the beta crowd here.
    1 point
  10. where can i get a copy of that firmware?
    1 point
  11. What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g R3 in its DMZ, modem/bridge mode Are ALL devices connected to the R3? What are the speeds you pay for/receive? Have you entered those speeds into the router? How have you setup Congestion Control? How have you setup SmartBOOST? What games are you playing? What platform are you playing on? How have you setup the Geo-Filter?
    1 point
  12. I actually disabled BI classification (based on your suggestion from a similar post) and it hasn't happened yet since. But it has been happening with multiple devices and I have been using Geo-Filter most of the time, though not all the time. I'll keep you posted.
    1 point
  13. Just a quick update, seems I was right in the beginning, there was stability issues at streamlabs. Dual output seemed fine tonight but I'll get back to you maybe Friday to check.
    1 point
  14. There really isn't much there indicating an issue, just the DHCP lease which should be taken care of with the changes you made but ensure all devices do have a reserved IP and then disable DHCP on the router, reboot from the interface and monitor from there
    1 point
  15. I'll let the team know it needs an update, it might be an issue with different cloud systems though
    1 point
  16. Netduma Fraser

    Rematch

    I'll pass it on to the team to see if they can get it added
    1 point
  17. Excellent detective skills! Hopefully you'll see a real improvement with the change, do let us know. Thanks and you, sweating too much right now 😂
    1 point
  18. We were told not to worry that the team would have released the v4 also for R2 How is possible that after 2 full year (March 2023), the V4 stable is still non available for R2. How long are you guys beta testing this thing? for 1-2 years If it's not ready so be it, but I haven't seen very much commitment to bring the V4 stable on R2 which wasn't cheap. Forcing people to buy R3 because software features that improves game experience. Maybe it just an hardware limitation, i'm ok with it, just full transparency... I wouldn't be upset if you would just say "Hey 3.3 would be the last stable update for R2, if you wish more the R3 is the next step. thank you", rather than "oh we are working on it" beta testing for how many years now?? EDIT: Forgot to mention that I applied for beta testing and the last bets version worked without much troubles delivering a better gaming experience but I can also see people struggling with the firmware and I really feel bad for them because that could have been me.
    1 point
  19. Hello Fraser, I hope you are doing well. A little update. I found out that we have a fibre hybrid connection Coax/HFC and no FTTH. So know we know where all of this instability is coming from. This connections are even used by more then one user. Leading often to internet outages for a longer period of time as well. lol. End of the story, after a lot of back and forward we were able to cancel our contract and will be able to change our provider, who can provide real FTTH. Let’s see what is happening then with the ping 😍 have a great day and stay cool, it’s hot out there 😅
    1 point
  20. No it won't be that, the error on the web browser is a standard no internet message. DNS maps domain names e.g. Google.com to IP addresses e.g. 8.8.8.8 so that when you go to Google.com you get connected to the 8.8.8.8 IP address and the content is displayed. With no internet that DNS process can't happen which is all it's really saying, I've tried to determine the IP address of this website you want to connect to but I'm unable to.
    1 point
  21. I'll pass on the details to the team and let you know when they attempt it
    1 point
  22. I run 236 as well, it's been the most stable for me.
    1 point
  23. I know, you'd think it'd be smart enough to choose one over the other and let's not celebrate yet, I need to test this theory.
    1 point
  24. Do you really see a difference by locking the speeds so low? For me, it's counterproductive because with SmartBoost, your in-game latency won't increase despite this test!
    1 point
  25. That's awesome, hope you love it! I've added you: https://forum.netduma.com/forum/151-netduma-r3-early-access/
    1 point
  26. Don't have an ETA for you, it's only been 1 workday so far so unlikely they've been able to look into it yet
    1 point
  27. I'll chase Alex about it on Monday
    1 point
  28. Added https://forum.netduma.com/forum/144-netduma-r2-early-access/
    1 point
  29. yes only 1 disconnect since then. Much better 👍
    1 point
  30. Thank you Fraser 👍
    1 point
  31. No it doesn't, just those in the Nighthawk Pro Gaming Range i.e. XR300, XR450, XR500, XR700 & XR1000
    1 point
  32. Yeah my PC has a reserved IP as do all the devices and yeah I put that to open and I'll give that a try.
    1 point
  33. Firstly, I know the purpose of the router isn't to mess with any matchmaking algorithm so if this discussion isn't allowed then apologies Fraser! Obviously we know duma has the ability to block individual servers, which I'm having to do due to the plethora of mislocated ones. But it has got me thinking, does the game have servers allocated to specific skill buckets? Like will certains servers always contain a ≥X MMR and others for the opposite. Has anyone experimented with blocking certain servers on duma and what have you found? I consistently see the same players over and over again in my lobbies, especially the crimson and iridescent players and would be curious if this done anything.
    1 point
  34. No specific recommendations other than to fine tune Congestion Control for your network, utilize Traffic Prioritization and use the Geo-Filter to force the closest servers to you. If the servers play badly then force servers slightly further away even if the ping is a little higher as the server may be under less load and actually play better.
    1 point
  35. I can't recall, is there an option to disable DPI where you disable QoS also? (Might be in a later version of 3.0) If it is a cloud problem then it would require a firmware update to get it working on the newer cloud system
    1 point
  36. I followed the steps listed by jodafi when I had restarted and had hte error "Dumaos is not loaded yet...", but I wanted to clarify a few things for others that wasn't as immediately obvious to me. Completely stock XR700 running 1.0.1.50. Monthly restart revealed the error and it immediately cost me 4 hours with my family on a Friday night. Whoever 'effed this up needs a firm nudge in the nads. Handy pre-start tip - If you have a lot of address reservations, port forwards etc. screen grab each page and paste it into Word so you can quickly re-enter later. 1. I downloaded http://www.downloads.netgear.com/files/GDC/XR700/XR700-V1.0.1.20.zip, extracted it 2. Then I logged in through this address http://routeripaddress/adv_index.htm to access the Netgear end of the Firmware 3. I accessed this address http://routeripaddress/debug.htm and clicked "enable telnet" 4. Clicked /Administration/Firmware Update/Browse , selected the unzipped file "XR700-V1.0.1.20.img" and then clicked 'upload'. 5. Once it was installed and rebooted, I factory reset it by holding in the reset button for more than 10 seconds. I used a toothpick. 6. Once it had rebooted, I then set up the router as usual with admin and password, however, once setup, it would still return back to the error. 7. I used CMD in windows, run as administrator and then typed "telnet routeripaddress (type your router ip address here) 8. It will ask you for your router password that you just set up. 9. Then i followed this part of jodafi's earlier post but importantly, you need to copy paste the whole lot. I got stuck here because I couldn't paste into CMD. You have to right click the Window title bar (the bit you grab when you drag a window around the screen) then click 'edit' and paste the whole lot into CMD. Then press enter. Once this is done, you should be good to set it up again with your login details etc. I also upgraded to the latest Netduma OS for this router and it feels snappy and happy. Not touching it until it dies again!
    1 point
  37. My ISP sends 1500 MTU. When I checked the transmission 1500 Packet needs to be Fragmented. 1472 is the biggest MTU where it doesn't ask for Fragmatization. So I don't see the logic of adding 28 to make it 1500 again when 1500 requires Fragmatization. I left 1472.
    1 point
  38. Pretty much what's been provided in the guide. Now, what also helps, is using the geo-filter. Everyone will be a little different. Some will have better games playing on local, or close servers. While others may have a better chance in playing on servers a little further away. Our ISP's routing to the servers all differ. So, using the geo-filter and isolating servers that give a better experience per user.
    1 point
  39. how did u know what the right Mac address is ?
    1 point
  40. DARKNESS

    XR 1000 CADA VEZ PIOR

    @BrunoYou can ignore ping optimizer as it not 100% accurate if you want to configure it professionally I'd use ping plotter but alternatively you can use https://www.waveform.com/tools/bufferbloat or lastly use your own system to configure the best setting by using command prompts and constantly ping a site will saturating the network.
    1 point
  41. I'm in the same boat, changed my ISP, now I have fiber, changed my PC, changed monitor, mouse, keyboard, headphones, power sockets for PC and monitor, windows re-install. Nothing worked, my ping is as low as 3 sometimes, mostly under 10 but I have this weird delay in everything that's on the screen and the sound, and it looks somewhat blurry when moving the camera around fast. On my screen it looks like I shoot the enemy, on the kill cams it shows that I missed. Sometimes the game feels great, mostly late night, and when that happens I am frying, but I can't stay up till 3:00 AM to start playing too often. I have just ordered my R3 to see if it helps, I don't have much hope.
    1 point
×
×
  • Create New...