Leaderboard

Thanks for the comments, I'll pass them on the team for when this is considered

Added

Thanks again for your help, you were right, the solution does work, but only if the process is followed very strictly. I can see why others may have failed or stopped midway. In my case, if I didn’t do: downgrade to 4.0.41 factory reset at that exact stage only use the correct command to bypass the wizard then upgrade it would break things badly (I had HTTP redirection to /dumaweb, SSL issues, Windows Update failing, etc.). Regarding your question about the 24h disconnect: Before this full process, I had hard disconnections every ~24 hours with no automatic reconnection at all ; I had to manually reboot the router each time. Now, after applying the full method, everything is stable. It has been 48 hours without any disconnection or need to reboot, so for now it looks like the issue may be completely resolved. What I’ve also identified is that the issue seems to be triggered specifically after performing a factory reset on firmware 4.0.540 or 4.0.645. After that, PPPoE auto-reconnection stops working correctly. Using the 4.0.41 reset + upgrade method seems to avoid that state entirely. I’ll continue monitoring to confirm over a longer period, but this is already very promising. Also interesting to hear you're running 4.0.645 successfully, that gives me confidence to maybe test it later, once I’m sure everything is stable on my side.

Thank you; I now know that the solution does, in fact, work for others, albeit with some bypassing involved. I have suggested the solution to others in the past, but I don't think anyone has actually persevered until the end. I have promptly used the latest firmware versions, as they are released, with the solution. I am currently using firmware version 4.0.645. The only slight problem I have encountered, which may be unrelated to the solution, is that the '--' fails to load occasionally. This problem has only started to occur more recently, and it resolves itself after some time without any intervention. One last question: do the 24-hour disconnects still occur but automatically reconnect afterwards, or do they no longer occur altogether?

General errors like that I don't always trust because all it's really telling you is it wasn't able to connect and there could be another reason for it BUT If you're getting a DNS issue then that is a problem, basically DNS is what turns a URL for example netduma.com into the IP address that you use to connect to that website. So if that's not working properly then it means that entering google.com into your web browser for example it wouldn't know what IP to connect to/access to then display the correct information back to you. If that is the case the ISP should be able to sort it quite easily, either from a new modem (if this is the issue then wiring is less likely and now more likely the modem) or something they can sort remotely. I understand your frustration on that, they have their script they have to go through and they will go through it regardless of what you say. Your best bet is to go through the motions, tell them the issue, do/feign doing if you've done their suggestions before (make sure to leave enough time in between so they can be certain you've done it) and let them go through all the steps they're required to ask you. If they can't fix it with those basic suggestions which is likely then they will either want to send a tech out which as you've mentioned isn't viable, hopefully explaining that they will (or ask to be) escalate(d) to a tier 2 or 3 tech. They will have more knowledge and should hopefully provide more targeted support/be able to identify the cause and solution. Also absolutely do not mention another router - it's vital you're clear that this issue is experienced when directly connected via ethernet from your PC to their modem - not saying they will but some may use that as the excuse to get you off the call if they don't know what the problem is. Good luck, I hope you can get it sorted and would be interested to hear an update on how you get on!

That's great to hear, thanks for the update! I would suggest staying on your current version as I cannot guarantee the kind of stability for your issue that you're looking for on that version at the moment.

We don't give out any ETAs but if we were to release .645 publicly it would be using the exact same version of the firmware you're on now. If we made any changes to it we'd release it with a new firmware number.

From my testing, my solution only works if the factory reset is on firmware version 4.0.41. Firmware version 4.0.41 was the last firmware with PPPoE working. Any factory reset after that firmware will break it again. The solution was to automatically reconnect when a disconnect occurs. I'm unsure whether it will prevent your disconnections from happening altogether.

You don't need PPPoE to connect the router to their ONT, you can just connect them and it should work unless they've specifically put measures in place to ensure you use their router connected to the ONT. You can just connect the R3 to their router otherwise.

ok thanks!

The ID is: 1FD984N Las Vegas. Ok i was wrong but its 27ms now. Not sure if still need ID. Its weird, when i connect to atlanta server it saids las vegas for a split second then after game start its Atlanta Server. So not sure if this is an issue or not. If need anything else let me know or more info. Thank you for your time.

@JOSHR3ll try this command as one command please instead: await duma.RPCHandler.PostRPC({rapp:"com.netdumasoftware.config",method:"set_web_setup_done",params:[true]}); await duma.RPCHandler.PostRPC({rapp:"com.netdumasoftware.config",method:"set_setup_done",params:[true]});

I will reply there shortly

Haha don't worry, there will be a new firmware in your lifetime! Progress is going well as far as I can see. In the meantime though there is a newer firmware you haven't yet tried which I've just given you access to: https://forum.netduma.com/forum/151-netduma-r3-early-access/

@DanologyUKThat tool isn't generally reliable for identifying the source of an issue, but it's great for 24/7 monitoring but it is free though @mygamertagsucks As he mentioned, the specs fall within 3 dBmV and 40 dB. The only potential concern might be the upstream, but it's still acceptable. It's likely difficult to fine-tune, and the ISP probably won't invest resources for such a minor improvement anyway. So did you get the ISP to check and are you still experiencing connection issues? I would more or less recommend PingPlotter for in-depth diagnostics. The only con is it is not free but there's a trial. The best route is a perpetual license version. I got Pro, but it is because I am pretty deep into analysis.

Those power levels are within tolerance so you are fine. If you are still really worried (don't be), goto https://www.thinkbroadband.com/broadband/monitoring/quality Set up this broadband quality meter (it's free). This will map out your connection by sending a ping to your Comcast Modem and will show you your normal ping levels as well as any packet loss. Here is mine for example. Once you have set it up, leave it for a few hours to allow it to build up an image of your connection. It sounds like you are looking for a problem when there isnt one?

They use new servers every so often, they've done it for every game, sometimes it's obvious there is an update needed, other times not

I will try it, but like I said it won't let me pass in both cases as PC and as Playstation. Why this is even happening? It never was a case back in 2023-2025 years.

It's always a good idea to get clarity! Good advice above but that could be it. Fingers crossed they'll be able to sort it out for you. Do keep us updated!

@DanologyUKThank you. I honestly figured this was the case, but was hoping y'all would tell me otherwise. I like the analogy, btw. And, honestly, when you said I was worrying over nothing; you have absolutely no clue how square you hit the nail on the head with that, lol.

Will check out tomorrow and report back!

As above the DoS attacks are rarely attacks and are usually showing connections you've made, for example some of IPs from your logs are: 3.169.149.83 - Amazon 69.147.65.251 - Yahoo 142.251.41.78 - Google 185.146.173.20 - Shopify/Cloudflare 100.52.165.89 - Amazon The others look to be reputable as far as I can see. There is something that potentially by the looks of the MAC addresses and the fact that they don't show as legitimate device on lookups you can solve which may help, is that you're likely using iPhone(s)/Android(s)/Windows PC(s) via WiFi that are using Private/Randomized MAC addresses which would explain the constant reporting of them in the logs. If you disable this option on each of those devices it should remove the entries from the logs and hopefully if that's the cause stop the issue you're having. If not then I would suggest connecting a PC directly to your modem and see if you get the same issue, if you do then that's something you'll need to contact your ISP about.

Dos Attacks seen in the logs are NOT DDoS Attacks. If you search on the forum, such as this post, you will see they are not DDoS attacks

Yes but won’t be able today. Ill make note for tomorrow

It seems as though technology is advancing very quickly. I am just trying to keep up. lol

I don't know specifically though with the features we're making e.g. ACC we wouldn't need it for that aspect at all. I suspect we would want/need better hardware if we were going to do things like this though as we push it to the hardware limits as is most of the time. Good suggestions though, I will pass it onto the team!

I've been using the netduma r1 since it's inception and grudgingly bought the r2 and r3. I actually got word of the r1 back on the old xim 3 forums as the two companies attempted to collaborate for a brief moment. I'd like to see more involvement to the general community from actual devs like there used to be. The developer(s) themselves used to actually interact with the community and provide feedback on what was going on behind the scenes and even helped support individual users directly. (Mostly during the r1 era) Fraser does an excellent job as community support, but it's not enough in my opinion. The community needs to hear from the people actively developing as well like it used to be. I understand the company has grown, and yet it is still small, but it's missing that element of community that thrived in the past. I think it's been completely detrimental to the company by not addressing well known bugs and seemingly stringing a carrot along that all will be fixed with an upcoming update (with new features( I'd love to see a a change in this direction with some resources being directed towards taking out known bugs and making the router function soundly while waiting for additional features. This has always been my main gripe with netduma. There has never been a 100 percent solid build. There's always a few things that are broken. I heard of you guys originally from the Xim forums. They also have a small team (5-7 people) and have also grown well beyond their roots. The difference with the xim team is they would never let well known bugs fester between releases. Anything that came up was addressed immediately while other major features were being developed. On top of that, the main developer himself still responds to threads on a weekly basis. I want this same dedication from netduma, like there used to be. Allocate some resources to squash out problems with current builds, and please let us hear from more than just fraser. Bring back trust and community.

I'll give it a few days as it is a brand new line

Yeah will look at that tomorrow Cheers Fraser

Hi, i haven’t tried yet. Will today and update you !

Thank you

I'm only seeing three not pinging at the moment so it's possible it's been updated already - click the 3 dots top right of the page and resync the cloud. Then try it again and see if they show. However, servers not appearing on Ping Heatmap would not have any impact on your ability to filter them, they're two completely different features. To force servers you need to do the following: It's essential the Geo-Filter is enabled before the game client (e.g. Steam etc) if on PC or platform (e.g. Xbox, PlayStation) or the game have been launched. If you change Geo-Filter settings when you're on the game then you will need to restart the game for those changes to take effect, otherwise it will use the previous Geo-Filter settings and appear not to be working. For settings ensure Ping Assist and Geo-Latency are disabled in the Geo-Filter menu that can be found by clicking ⋮ in the top right hand corner of the page and go to Settings. Strict Mode should also be enabled, it is enabled by default so if you haven't disabled it you can ignore it. If you have disabled it or want to check it can be found in the same Settings menu as above or in Settings > Troubleshooting > Advanced > Developer Options depending on your firmware version. Fast Search should also be disabled which it is by default so can be ignored if you haven't changed it, otherwise this can be found in the same place.

Those two things are really at odds with each other. If you want to use the DMZ then just keep UPnP enabled and that will work for the PC

can you reply when you've heard back and they can try force an update because im going to leave it till then as ive tried multiple times and im going to use my regular router till then. thanks

Exactly as above!

Your order has been cancelled, we've emailed you

Putting a device's IP into the DMZ is the same as port forwarding ALL ports for that device. It essentially lets through all traffic but opens you to some risk as all ports are open, should a would-be hacker wish to try and connect. I would recommend putting consoles into the DMZ but not a PC for example.

Always/Auto just control when you want it to apply so it's purely a personal decision. 70% is our recommended starting point but there is no one percentage that works best for every connection. You'll need to do some fine tuning/trial & error to find what works best for you. You are on an old version so the cloud will work better with the latest version. Ping Assist won't be present on that version I'm not aware of a visual bug on the ping panel so this is likely reporting the connection as it is Yes I'd suggest factory resetting after upgrading, especially as you're doing a big jump in versions.

The game is very strict with the server selection during matchmaking . Just two or three in the EU and that’s it. It won’t let you connect anywhere else. If the player pool is low, it populates with bots. Unfortunately Geofilter can’t help as much as in COD.

No worries! Congestion Control should definitely be used to eliminate any existing or potential future issues caused by other devices on your network - all it takes is one singular download on your network to use all your available bandwidth and start causing issues. We usually suggest starting at 70% and fine tuning from there - you could have it set to Always or Auto Enable if you just want it to apply when gaming and then you get full speeds at all other times - this does require Traffic Prioritization which I'll come to. Bandwidth Allocation you can leave at the defaults, you won't really see any benefits from adjusting it with your speeds. For Traffic Prioritization you don't need to prioritize all gaming consoles - if you disable DumaOS Classified Games it will only then apply to the specific devices you add. You may be referring to adding these devices with the Games Console service/rule - this does not mean it applies to all gaming devices in your home, it just means it covers the necessary ports that gaming uses per the device you add it for. This is particularly helpful for a PC for example if say Valorant when specifically added isn't prioritizing (it uses a different method to prioritize which is susceptible to becoming out of date). By selecting your PC with the Games Console service it will prioritize the game and won't ever become out of date like the specific Valorant service will. By selecting this it won't prioritize downloads or streaming, regular web browsing etc so you won't see any issues from a stray download getting prioritized for example. If you so choose you could just add your PC to Traffic Prioritization, you don't need to add all consoles. This should then in theory give you the edge if all gaming devices are being used at the same time. That's fair enough, doesn't sound like you need the Geo-Filter at this stage.

I'll let others comment of course but one of the reasons you don't see too many setup posts etc is because there are so many variables when it comes to networking that a configuration that works well for one person may work terribly for another. I'd always suggest experimenting yourself to see what works best, as long as you don't expect 100% of your games to be perfect then you'll find settings that work well for you.

It just affects how you connect to people but as most games use servers now, even for chatting this is less of an issue. If you do play with people frequently and you do notice issues connecting to not having an Open NAT may be the issue. For example if you both have a moderate NAT.

Port forwarding/triggering is really only required for NAT purposes, it won't specifically improve your connection to the game.

Exactly as above! 540 is the public firmware and 645 is the Early Access firmware