cedric108

Thanks for the explanation about Hybrid VPN.
Yeah, I remember seeing the patch notes mention that they were starting to crack down on VPN usage. It just wasn’t as strict back then as it seems to be now. Hopefully, they’re still testing different values and this isn’t the final setup.
In the meantime, I can still play with my friend in Japan by connecting through the New York server. I also noticed that using a wired connection helps lower the ping a bit, sometimes enough also to get the DC server under the threshold too. I’m keeping an eye on the situation to see how it develops.
And by the way, thanks for developing the geo-filter! Without it, I wouldn’t even be able to play with my friend, and we both get a solid experience because of it.

Hi everyone,
The wait is over, we're happy to deliver the latest R3 firmware. It contains months of work from our development team, with a big focus on improving the stability and reliability of our features.
Main Changes:
Hybrid VPN is here: this is long standing Netduma feature which allows you to run your VPN through your router and then choose which devices or applications the VPN should be applied to. This means you can run your VPN on things that usually hard run a VPN on, such as Smart TVs and consoles. Hybrid VPN is compatible with OpenVPN and WireGuard, so make sure your VPN provider supports one of these protocols. Added UPnP Relay. Previously, if your R3 was connected underneath an ISP router, you'd likely see a Double NAT reported on your games console unless you did some manual port forwarding. UPnP Relay pushes port opening requests from your devices up the chain to your ISP router, meaning you should get an open NAT with no additional configuration needed Some users reported issues with Chromecast or Airplay, or transferring files locally. These are fully fixed now. Many quality of life / annoying bugs fixed, including improved IPv6 and PPPoE support, increasing the reliability of the Geo-Filter ping graph and increasing the reliability of the Ping Optimiser test (with further improvements to come) A longer changelog is below.
We want the Netduma R3 to be the best router in the world, and we're taking another step towards that goal with this firmware. We'll continue working on and releasing updates, so please give us any feedback you have.
 
INSTALL GUIDE
You can install the firmware using one-click update. Simply open up DumaOS and look for the green "Update Available" icon.
Alternatively, you can download the file below, then go to Settings > Troubleshooting > Upload Firmware, then upload the file.
DumaOS-R3-4.0.219.sig
NOTE: You need to login to the forum before you can download this file. If you don't want to make an account, use one-click update as described above.
 
Changelog:
Hybrid-VPN added Improved performance of SmartBOOST Improved performance of Steady Ping Improved performance of Geo-Filter Ping graph appears more frequently Ping Optimiser reliability improvements Chromecast/AirPlay compatibility fixed UPnP relay added (no more double NAT) Increased maximum speeds Improved compatibility with IPv6 and PPPoE Optimisations to improve memory usage Many other smaller bug fixes

Probably 2025. Netduma still hasn’t released a firmware. It’s almost been 3 months and nothing. It appears that they only have 1 developer on the team lol

Are we getting a new firmware this month?

Thank you for the tip. I tried this and it did not work and as with my previous Duma router I did not have to split up my bands and all my devices where able to find each other. It’s seems to be a R3 software issue 

Hello Team
APPLE AirPlay and IPhone remote app still not finding Apple TVs on the same network. I did not have any of these issues with my previous Nighthawk Netduna OS router. I have updated to the latest firmware in hopes that this would be fixed. My home is deep in the Apple ecosystem and my Apple devices not being able to talk to each is a problem. Side note adding an extender antenna does not work well on this router as it treats the extender as an individual device and not and extension of the network. Thank you for all your hard work on this product 

@Netduma Fraser Can you give a detailed explanation on what the 'Geo-Latency' feature actually does? This is not quite clear to me. Cheers!

After a few games of COD MW3, I'm glad to report Steady Ping working well but with Geolatency turned OFF When Geolatency is ON the Geofilter allows connection to servers outside the Geofence even with Ping Assist off (0), this feature  needs more work still.
 

Thank you very much. I like being able to receive new firmwares regularly.
The update process this time is much more smoother than previous firmwares. I am going to do some in-game tests.
By the way, the issue where local wireless devices connected to the same Wi-Fi frequency (5GHz / 2.4GHz) can't communicate with each other has still not been fixed. Is this bug going to be fixed soon? Thanks.

Overall R3 works fine. Geo-Filter works. I am not experiencing those network connectivity and low download speed issues that others are reporting, expect a major issue I already reported.
Wireless devices on the same Wi-Fi frequency cannot see each other, for example devices connected to 5GHz are all isolated, but they can communicate with devices connected 2.4GHz. It causes a lot of problems with smart home devices, printers and local file sharing.

As it stands now, my XR1000 is more stable. All of the issues that I’m having with the R3 went away when I switched back. I like the R3s feature set, just hope it gets patched soon. 

It's likely that in the evenings/during peak times the game is trying to keep everyone more to their region, as more people are online the servers become more under load, adding high ping to that would result in a bad experience. Over the last few days it has occurred to me that it may be using a relay server which could be causing games to appear outside the radius. I'll have to have the team look into it.

This would make sense as around 6/7pm UK time is when I start to experience the issue, before that time I'm able to geofilter to any region such as US or Saudi and get into lobbies with no issues whatsoever, during the evenings however it allows that authentication server to bypass my geofilter selection even when I have tried to block that particular server. So in the evenings I just cannot use the geofilter at all as it starts trying to put me into local servers.

No .23 was from before the holidays on the first week of launch. The issue is actually a regression which is actually a good thing as we identified the internal version it was introduced in and so can work backwards from there to identify what changed.

Thank you very much for the clarification. I am using version 4.0.21.
Actually, everything is working fine today (no setting change, no reboot). It seems that if the authentication server is displayed on the GeoFilter map, the issue may occur, but if it's not explicitly displayed (which is usually the case), everything works as expected. I am going to keep monitoring the situation.

ok, I see. Thank you.
Does having an authentication server outside the circle also disrupts GeoFilter on your side?

Thanks! We've identified the issue so the team will get it resolved after the holiday break

Thank you for this, having a look over some correspondence I believe we have identified the issue (manifested in a different way to you), I'm hoping we can get a fix available tomorrow but it may be in the new year due to the holiday season.

Firstly thank you very much for identifying the issue and providing easy to follow reproduceable steps, this really helps the development team identify the issue quickly and speeds up a potential fix, I will certainly pass this on to them as well as the other topic you mentioned.
Just as a test, could you make traffic rules for the affected devices to allow ALL traffic to them and see if they work the way you want them to then please?

Steps to reproduce:
Connect two devices wirelessly to R3's Wi-Fi, make sure they use the same Wi-Fi frequency, either both 5GHz or both 2.4GHz. Ping each other. Expected result:
Both devices should be able to communicate with each other.
Actual result:
They can't communicate with each other.
Firmware versions tested: v4.0.19 and v4.0.20
Remarks:
2.4GHz <-> 5GHz works. WLAN <-> LAN works. I haven't tested two wired devices. This is a serious issue, it would impact local file sharing, smart home devices, printers, wireless debugging, etc. Please help.

Geo-Latency is essentially a way of filtering servers by ping, everything outside your radius will have a high ping, thereby forcing servers within your radius instead. We have identified some issues with it that will be fixed. With it disabled it will be like the original version of the Geo-Filter that works by allowing everything inside the radius (location based) and exclude everything outside. The Geo-Filter will be active if you have a device added that has filtering enabled.

I tested with an old phone with only 2.4GHz Wi-Fi support. It worked, the phone can see my iPad on 5GHz band, however, if both devices are connected to the same Wi-Fi frequency, they can't see each other. It's reproducible, I can confirm.
I believe AirPlay and HomePods Pairing issues are all caused by this bug.

I tested 3 games in MW3 with geo latency disabled, it’s a small sample size, but yes, it does filter inside the circle. I even made a change to the circle during this game session, it worked.
However, with geo latency enabled, the result became inconsistent, sometimes the router shows I was connecting to a server in Los Angeles, but in reality I was connected to a local server in Europe and servers outside the circle were not denied. I have Ping Assist disabled.

I am having the same issue.
This is my post in R3’s forum. https://forum.netduma.com/topic/52907-unable-to-connect-to-the-local-wi-fi-server/
Please take a look, I am pretty sure it’s the same problem.
Luckily I found another recent post https://forum.netduma.com/topic/52834-wifi-client-isolation-issue/ talking about this. It seems devices on the same Wi-Fi frequency can’t communicate each other, which explains your problem. I have also a HomePod, already configured, it uses 5GHz Wi-Fi frequency just like my phone.
This is a very serious problem, dear Netduma team, please help.

I am having all kinds of trouble reconfiguring WiFi connected devices that require setup through a cell phone.  I believe I have discovered the problem, which is that there seems to be client isolation set within the same frequency's network.  It's possible I'm blind, but I don't see a setting for this anywhere.  I have verified this by segregating the WiFi networks and pinging the devices in question from my phone (IPs pulled from Device Manager).  From 2.4 GHz to 2.4 GHz, no traffic is passed but when I connect the phone to 5 GHz it is suddenly able to ping and device setup completes.  I can't ping in the other direction, as these other devices are smart home devices and have no console.  I have further tested this by running a constant ping from my phone to a laptop and switching between the two networks.  As soon as the laptop connects to the other network, pings start coming back.  Networks in question are the secured networks, not the guest networks.  Where can this be turned off?