ChrisG82

I have assumed that the 8 bytes are included in the 1492 as he sends ICMP packets. But yes I think you are right.

I don't quite understand what you are trying to say. 1492 - 20 (Ethernet header) are the 1472 mentioned, which is why a ping with packet size 1472 goes through and 1473 does not. If, as you say, the MTU restriction did not apply, packets up to 1480 would theoretically still go through. EDIT: sorry, I forgot the 8 bit for the ICMP header like @DanologyUK has mentioned below.. So yes it’s looks strange. What type of connection you use? PPPoE or DHCP / Static IP?

I would prefer that the R3 will use ist as a permanent storage so that there is no data loss (like Logs, data usage, ping heatmap and so on) after a powercycle…

@TG3NOC1D3 You are totally right! The way Netduma has currently implemented UPNP is really no help but a pure security risk! I don't understand why they haven't implemented the whole thing on a device-by-device basis. So that you can allow certain devices to use UPNP and not others. Then it would be no problem to allow the PS5 to use UPNP. @Netduma Fraser Please pass this on as feedback to the development team. It would be nice if UPNP could be activated for specific devices as soon as possible and not system-wide.

It is best to enter the DNS in R3. Deactivate upstream DNS. All devices should use the R3 as DNS server so that all R3 features can be used

No, it is not technically possible as long as the R3 is not the device that establishes the VPN connection. You set up a tunnel from your PC to another server and only send this data through it. Nobody can look into this tunnel (sense and purpose!) The R3 cannot look into it either. How is the R3 supposed to filter accordingly?

Although I didn't have any problems with the Wi-Fi (at least none that the devices couldn't connect), I had to restart the router every three days at the latest as I couldn't access the UI either via the app or the browser. I deactivated Smart Boost and the router has now been running for five days and I can access the UI without any problems.

Port Scan Protection prevents anyone from the Internet from scanning the router for open ports to see if any services are vulnerable from outside. The Spanning Tree Protocol prevents parallel connections in networks with several switches and thus prevents the formation of loops

Have you already tried to disable Smart Boost? Had the same problem after the R3 was up 2 to 3 Days. After I disabled Smart Boost the Router is now up for 5 Days and I have no problem to connect with App or Browser…

With the best will in the world, I can't imagine that it has ever worked like this. You set up a VPN tunnel from the PC to a VPN server via NordVPN. The Netduma R3 may still be able to see the VPN connection to the VPN server. I cannot judge whether this is displayed in the geofilter (as the VPN server is not a game server). BUT as soon as the VPN connection itself is established and all data is routed through this connection, the R3 can no longer actually see which connections and data are flowing through this tunnel. That is exactly the purpose of a VPN tunnel: Nobody should be able to look in! For this to work, the R3 itself must initiate the tunnel, but this is not yet possible.

Here the Changelog from iPad OS / iOS: Version 1.2.12 Further fixes for XR1000 connection issues Hybrid VPN support (R3 firmware coming soon) Added easy firmware upgrade feature Streamlined adding a device to Geo-Filter Geo-Filter icons are now more crisp Geo-Filter Auto-Host display is now more reliable Geo-Filter now shows a warning if your device type is wrong Added Steady Ping to many areas in Geo-Filter Added a new stats section to Steady Ping Added the ability to change sliders by entering numbers Added a "Speedtest Bypass" feature Improvements to Ping Heatmap Improvements to Netduma R3 RGB Colour Selection page Improvements to Port Forwarding page Improvements to UPnP page Improvements to Dashboard colour and layout Improved integration with mobile light and dark themes Fixed PPPoE login during initial setup Improved wording and translations EDIT: Maybe @Netduma Fraser want to „Pin“ this Thread?

Do a reboot of the R3 first. When the R3 is online again try to repeat ping optimizer….

And sorry, what you describe doesn't sound like a bug in the firmware, but rather like a user who doesn't know what he's doing

@euphidra Why don't you try it the other way round? Your subnet probably looks like this. The IP address of the router is the following address, i.e. 192.168.77.1. The subnet mask is 255.255.255.0 by default. The default DHCP range is, I believe, from 77.100-77.250 If you are working with DHCP reservations, why don't you just use the IPs 77.10-77.21 for your 11 devices? DHCP reservations do not have to be in the DHCP range for them to work!

@Netduma Fraser Please integrate it like in DumaOS3 that the IP of the Server with the game is connected to will shown! That will be very helpful for troubleshooting!

Could you provide your settings for Geo-Filter please? Maybe as screenshots?

No, not possible at the moment. I will hope that we get this feature wit a new firmware release in future. I don’t understand how they could release such a device without the possibility to backup and restore the settings…

Go to the geofilter settings and deactivate the upper point (geo-latency). Then restart the PlayStation. I also had the problem that I often ended up in Amsterdam, France and the like. Since I deactivated Geo-Latency, I only end up in Mainz (the servers closest to me)

However, this should not scare you too much. This is pretty normal when devices are made accessible from the Internet. These are regular attacks on the IP address ranges, with the hope that the attacker will get lucky with an IP at some point. Your router itself is constantly exposed to such attacks, but apparently does not indicate this to itself. If you have a Microsoft account, for example, and authenticate yourself with a password, you should take a look at the login activities in the security dashboard. There you can see how often attempts are made to illegally access your Microsoft account.

This is a known problem actually. We all hope that’s the new firmware release will fix it.

So you maybe you can look what could caused the possible loop issue. It may be a fault in the cabling or in the configuration of the switch, provided it can be managed.

Und? Konntest du es testen?

According to the ping heatmap, there are also Warzone servers in Mainz. @Oskar Markus also says that he is sometimes connected via servers in Mainz.

Geh mal in die Einstellung vom Geofilter und deaktiviere dort den oberen Punkt (Geo-Latency). Danach die PlayStation neu starten. Hatte auch das Problem, dass ich öfter in Amsterdam, Frankreich und Co. gelandet bin. Seitdem ich Geo-Latency deaktiviert habe, lande ich nur noch in Mainz. Muss aber dazu sagen, dass ich ausschließlich Multiplayer spiele und nicht Warzone. Wenn du aber sagst, dass du ja trotzdem oft über Mainz verbunden wirst, gehe ich davon aus, dass auch dort Server für Warzone stehen.

That's definitely not how I know it. If the PlayStation is connected to an active switch, the network connection itself is definitely maintained. Then the PlayStation only says no Internet but not LAN cable not connected. Edit: It might still be worth a try to take the switch out of operation and run everything via the R3 only, even if some devices are then possibly not connected.