Od1n

I remember when ping-stabilizer got teased by the Netduma Dev-Lead Ian in 2017 or 2018 by showing lab results he got with it. Back then it was said to be an R1 feature called "anti-jitter". 7 years later and it's still not out yet, or let's say fully functional... 😅

Given how much help the NetDuma Support provided me i want to provide the solution to this problem. It took some time to figure this out but my ISP switched my connection from IPv4 to Dual-Stack-Lite without me being aware of that. DS-Lite does not offer port forwarding and other stuff, which resulted in my R1 not being able to open these ports. Long story short, i must now pay a few more bucks per months to have an IPv4 again and now the R1 can successfully open ports again!

Thanks a lot that worked! Speeds arent amazing (5 down 2,4 up) but that is perfectly fine for gaming! Works really well and i can VPN into a different region now!

Thanks a lot Liam! I run into two issues though, maybe you can help me out (see screenshot below). 1) The R1 doesnt allow me to assign the VPN to the Playstation. The option to activate the VPN for this service is greyed out. 2) The VPN says connected on the left side but when i do an IP/location check with my PC i am still on my normal IP and home country. For reference this is what i did: I clicked on Setup VPN, then picked Advanced. Unter username and password i typed in my NordVPN login credentials. Then under Configuration i pasted the whole text content of the OpenVPN file that i downloaded from the NordVPN website. Is that correct? Or must it only the be certificate part of the .ovpn file?

Hey Netduma Support, I wanted to setup a VPN on my R1 that is only assigned to my PS5 (as an option to play in a different region). Has the VPN setup changed since its first implementation into the DumaOS? All guides that i found are several years old, and the instruction video from the Netduma YT channel is set to private now too. If i recall correctly i must just paste the OpenVPN file into the DumaOS interface and then select the device in my network it should apply to. Is that still correct? Also last time i tried the VPN Router solution the download speeds dropped to like 3-4mbits due to the VPN computation being so demanding for the R1 CPU. I assume this will still be the case, right? If yes i would make sure to not download larger files through this setup but turn off the VPN then. As long as the stability of the VPN connection doesnt suffer from this i could deal with the reduced bandwidth.

Hey Fraser, how would i do port sharing with the R1? This is the first time i hear about that terminology :). Right now the R1 uses DHCP with the Fritzbox, PPPoE doesnt work anymore since quite a while (around the time i updated from DumaOS 2.0 to DumaOS 3.0). By the way the port forwarding is just one issue that doesnt work since then anymore. WiFi Call from the phone or not being able to open the NAT are other problems that came along with this change. The NAT is for example always moderate/symmetric. Just mentioning this in case its helpful to isolate the issue.

I thought more about it and i remembered how this whole situation started. During the DumaOS 2.0 and prior firmware versions i was using PPPoE from the R1 to the Fritzbox. I think the Fritzbox removed this feature around the launch of the DumaOS 3.0 via a firmware update though. At least since then i cannot find this feature in the Fritzbox interface anymore. From this time onwards i had to switch from PPPoE to DHCP. Since then all my ports are closed. I dont think this is the case, here is how it looks like. Default IP of the Fritzbox is 192.168.178.1

Wow Fraser i really appreciate that! 😮 The specific model is "FRITZ!Box 7530".

Yes with the DMZ too, port is closed. The Fritzbox is set as a DHCP Server, i dont know if it has a bridge mode though. Very Very old Fritzbox models had a modem mode (it turns into a modem then) and a PPPoE mode for other devices to establish an Internet connection though the Fritzbox.

All right i did both of that, the miner interface still says relayed though (aka the port is closed). I can restart the R1 once more to see if it makes a difference, but i doubt it. What else could i try? It starts to sound like i may have to remove the R1, no?

All right thanks Fraser i will activate IPv6 again! How do i do the following two in the R1 interface?

1) The R1 is using an IPv4 address to the Fritzbox (192.168.178.22). I activated both DHCP IPv4 and DHCP IPv6 on the Fritzbox but to me it looks like the Netduma uses the IPv4 DHCP. Worth to mention: In my NetDuma WAN settings i have turned off IPv6 so this would only make sense. This was a recommendation by you around 2 months ago where my R1 Internet would randomly die. Details here though not that relevant for this problem i think: 2) The miner uses an IPv4 address in the R1 network (192.168.88.201) and has no IPv6 assigned to it And yes this port forwarding issue think it has been with every DumaOS 3.0 version i think, but i upgraded from 2.0 to 3.0 very very late as i wasnt a beta tester for it. I probably updated to 3.0 around a year after it was out. So i cannot say how i would have worked with early DumaOS 3.0 firmware versions. The miner is currently doing some syncing to the blockchain so i cannot check its port situation. Though since i havent done anything else its port will still be closed. The problem with a closed 44158 port is that all traffic will be relayed to a different miner nearby and you lose a significant amount of mining income (which the nearby miner then gets). So you want to avoid being relayed = port closed at all costs .

All right thanks for the update, great to hear that there is progress!

Thanks for replying on a Sunday Fraser, much appreciated! Yes with previous firmware version (DumaOS 2.0 and below) i never had issues doing port forwarding, even UPnP worked then. This goes all the way back to the original launch R1 firmware and my network setup hasnt changed since then. The device i need to port forward is a so called Helium crypto miner named Sensecap M1. It communicates with the blockchain on TCP port 44158. I will get you this information as soon as im back home, stupid traffic jams

I must open TCP port 44158 for a device XYZ in my network. This is a make or break situation, if i cannot get this port to open i will have to remove the R1 As you can guess im not able to open this port so far. Here is what i have done but the port is still closed. 1) R1 is connected to a Fritzbox via DHCP. The Fritzbox has the option ticked to allow the R1 to open its own ports! R1 is also set to exposed IPv4 and IPv6 host in the Fritzbox which fully deactivates the Fritzbox firewall for the R1. The R1 has a fixed address within the Firtzbox DHCP too. 2) Assign device XYZ a reserved DCHP IP in the range of 2-49 in the R1 settings. I went with 192.168.88.40. 3) Create a corresponding port forwarding rule in the R1 settings with inbound/outbound port 44158 TCP assigned to device XYZ on 192.168.88.40. 4) Restart R1 to verify all settings have been saved and device XYZ runs only on IP 192.168.88.40! When testing the port it is still closed though! So i also did: 5) Turn off UPnP and restart router, once again it doesnt work. So i checked my Fritzbox and it has an option to show which ports the R1 currently requests to be open. It shows 0, the R1 seems to fail to tell the Fritzbox that it wants this port to be opened. I would like to mention that since the release of DumaOS 3.0 i have never been able to open ports. On DumaOS 2.0 and below it worked. My network setup hasnt changed since i bought the R1 as an early bird. I do not see what i am doing wrong with my 5 steps so NetDuma Support please tell me what settings i oversaw. Otherwise i must remove the R1. Firmware is 207.