Leaderboard

To be honest, the NetDuma community isn’t really a typical customer base. We’re more like passionate enthusiasts with a mild addiction. We complain, we debate, we push for more… and yet we’re still here. That says something. We appreciate that updates for the R3 are in progress, and it’s good to hear they’re substantial. But there’s another thought that many people here share — some openly, others quietly refreshing the forum every day. We’re not just waiting for firmware. We’re waiting for the next level of hardware. If a more powerful next-gen router — call it an R4 or whatever it ends up being — were announced tomorrow, I genuinely believe a huge portion of this community would upgrade instantly. Not because of marketing pressure. Not because we’re being manipulated. But because we believe in the idea behind NetDuma, and we want to see it running on hardware that truly matches its ambition. Sometimes the frustration you see here isn’t negativity — it’s anticipation. People don’t get loud about products they don’t care about. The reason discussions get heated is because expectations are high. Give us DumaOS running on seriously powerful hardware, with proper headroom for the future, and that wouldn’t just be another release. It would be a statement. We’re not angry customers. We’re impatient supporters. And that’s a good problem to have.

i got it working not sure what i did but it works now

It took a lot of time and effort to finally achieve this result. Trying things out, shifting the mesh system, and adjusting the netduma. I'm very happy with the result.

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

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

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.

Muito obrigado por responder, tenha um ótimo dia.

No it's not necessary for you

I'm thinking about that. I hadn't too much problems with v4.0.258, really. I only use that for Warzone.

Good to hear! If you download the last DumaOS 3 update, then just upgrade to it from the interface. Hard to say, I don't think 4 on the R2 is too unstable really. Whatever works best for you!

When it gets to the internet part of the setup selected the advanced options and then you can skip that part of the setup, complete the wizard and then you can get through to the interface. Then, reboot the Movistar, wait 2 minutes, reboot the R2 from the interface, wait 4 minutes and see if you get a connection then.

ok I will move the geo filter around this week and report back this weekend

Your ping sounds fine and it's unlikely you're experiencing any congestion so I think forcing some different servers might give you a better experience

Honestly, just having a 2.5 Gb Wan port would be a good enough upgrade for me as my 1 Gb AT&T fiber actually comes in at 1.25 Gbps. Would allow to use all available bandwidth. No actual devices other than my desktop pc have a 2,5 Gb port so the extra bandwidth is negligible. I guess I can say I have been lucky with the R3. I have not had any hardware issues with it like I had with the R2. My R2 eventually went into a power up boot loop and basically became a paperweight at 3 years old. I also had Wi-fi issues with the R2 but nothing like that with the R3. Fortunately for me though, my entire home is hardwired into every room. And anyone who buys a Netduma router is buying it for DumaOS. There is no other reason other than that to buy a Netduma router. So let them focus on getting the software right. That is what we paid them for.

No one usually posts a bad gameplay video to YT!

Yes correct. It's available to some users but not you. Just wait for it to be released.

Hi @Netduma Fraser, this is great news, since I will be moving from a very poor FTTC network to a 5G one, I'm very happy to know it. If you need a tester user, I can share and test the firmware if it is released in beta. In the form where you report your line, I had put my FTTC, but for a while longer I will have both, both FTTC and 5G, so if you need a tester when you release the beta firmware, I'm happy to provide feedback.

MERCI

We've been hearing about this for half a year, it's like waiting for Santa Claus on his reindeer who won't show up. Or is just prolonging time to the next release of new router to be honest 😂

Problem solved. It turned out to be my controller disconnecting from the console. That was causing the PSN and Call of Duty logouts. This was not related to the NetDuma R3 in any way. Thanks for the assistance — case can be closed.

You can't setup to apply different locations/radius sizes etc for different games, this was something we were considering/looking into the feasibility of adding, it may come in the future.

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.

Yes you will, we've spent a lot of time and resources on these new features so yes they will be coming

Buongiorno, volevo delle informazioni precise riguardo il settaggio del qos, cercando su internet ho visto che è consigliato per le ftth stare tra l 80% e il 90% e non necessariamente stare in bufferbloat a+ questo perché se per raggiungere a+ dovessimo scendere sotto la soglia del 80% in giochi come warzone verrebbe aggiunto un jitter artificiale, che ne compromettere la fluidita e l hit reg del gioco. È reale tutto ciò sapete dirmi qualcosa di concreto

I'm not sure where you've got that information but: We don't have any specific recommendations based on connection type We don't suggest to stay within a certain percentage range Are you referring to lag compensation - the theory that if your connection is too good that the game essentially makes your connection worse/helps worse connection players have a fairer experience? The first two are not correct, there are no one size fits all settings, every connection is different so its best to experiment to find what works best for you. As for lag compensation, I don't know how much I believe the aspect where they make your connection worse but I'm sure they do have measures in place so that people with worse connections can have a better experience than they would otherwise have.

Hi, Normally on a City Fibre connection you would need the username and password plus the VLANID. (At least that’s been the case on the last three City Fibre connections I’ve had.) VLANID could be 911. Your ISP should be able to give you the details for all of the above credentials. As @Krush shows above, if you’re already in the main Duma OS console. Then go to Settings > WAN, then select PPPoE, then pop in your details. *The VLANID is under the advance section of the WAN settings (on some firmware). Please note, it may take a few minutes for the City Fibre connection to establish once you fill in the details and save. You may need to reboot the router if you see no connection after say 10 minutes. Hope that helps.

PPPoE from my internet service?

United Kingdom the service is called uswitch city fibre

If it's working without the Geo-Filter enabled then it'll 100% be those servers that need to be added, they can appear and disappear very quickly. Either way the team will investigate and resolve it via a cloud update as soon as they can.

Obg

Yes that's normal

No, we keep the current game and last game on there so when 7 came out we would have removed MW3. The servers are essentially all the same anyway.

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.

You can keep it enabled that's fine

Hi! I've been working hard lately to get my Netduma, including Deco's Wi-Fi mesh, working. I've searched extensively for the correct settings and have found them. I'd like to share them with you. Here are both my Wi-Fi and wired results. First my WIFI results My wired results

Putting yourself in 100ms ping lobbies is setting yourself up for a major disadvantage either way you look at it 😂😂

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.

Thank you, I'll pass it on!

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

im almost on your route..