Jump to content


  • Content Count

  • Joined

  • Last visited

About patnj

  • Rank

Basic Info

  • DumaOS Routers Owned
    Netduma R2


  • Connection Speed
    Don't know/Won't say
  1. Hi Fraser, All sorted...fixed IP has resolved the issue. Thank you for you help and support, especially on a Sunday...greatly appreciated and a real testament to NetDuma’s customer support philosophy and sorry for the late diagnosis from my side (ISP issue)
  2. Hi Fraser, I have just got off a call with my ISP and they have recently moved to CG-NAT (whatever that means) which they feel would not work with the uPNP on the R2. They said they need to give me a static public ip, which they are going to do, which in their opinion will resolve this issues. Not knowing much about this, do you feel this recent ISP change could be the cause ?? Should I wait for this change, before carrying out the test you have suggested? BTW..not sure if the ISP change happened around the same time as the firmware update. Thanks
  3. Im using an Xbox Series X console. It reports NatType: Strict This is shown on the XBox Network Setting page. Same message is shown if I use the "Test NAT" option. The other device is my Synology home server. They have an app which automatically sets up the router uPNP for their Photo/Video apps. It first test that the router is compatible, which it reports as "passed", then tries to setup the ports. This then returns a pop-up message "Port forwarding rules could not be applied. Please restart UPnP/NatPmP protocol on the router or restart the router." Also, as I mentioned earlier, all was ok before updating the firmware. Your earlier question on the fibre modem, does this up stream router, which the R2 connects to, also play a part in whether uPNP works on the R2 ? BTW, nothing is shown on R2 under the uPNP tabs. This normally shows the ports that have been opened
  4. ZTE Fibre ONT connected directly to R2 (using PPPOE for authentication).
  5. Most devices via a Gigabit switch to the router and 2 affected devices directly to the R2. Forgot to mention in the last post, that my setup worked completely fine with .179.
  6. All my devices, are unable set any ports using uPnP. Some report along the lines of; Port forwarding rules could not be applied. Please restart UPnP/NatPmP protocol on the router or restart the router. I have rebooted, turned QoS and Geo Filter off, turned off uPnP and used Port forwarding, have given affected devices fixed IPs, but nothing works. Using .205 firmware, have already factory reset via button at back of router, but still no joy.
  7. Hey @Netduma Fraser, Will is be possible to down-grade the firmware from .205 to .179 after installation of .205 ? Just in case, as my .179 has been pretty stable for the past month
  8. Hi, Does anyone know the best way to block YouTube completely for all or specific computers on the local network using DumaOS on R2 ? I thought I would try a custom list within Adblocker, but this did not work. YouTube apps were still able to connect. Thanks in advance.
  9. After updating to .179 Connection Benchmark does not appear to be working correctly when a "scheduled" test is run. Basically, when ran as part of the schedule, the "Ping under load" reports either D or C, however if I run it manually using the "Run Test" button it reports A+. See below image (time and date in Yellow are manually run tests). So where this leaves me, is whether the connection benchmark results are correct, when manually run or when ran under the scheduler. Either way, feel this a defect that needs to be looked at, as every manual run (where time is not on the hour) reports A+, but all other scheduled runs report lower This is clearly shown between 14.25 and 15.23 on the 3rd Nov, where the 15.00 is a scheduled run.
  10. "Honestly though I think we'll probably go with the downloadable config file option, despite the risk of low level corruption." Could you not implement some kind of "checksum" validation to compare the downloaded config file to the one generated in memory at the point of export ?
  11. Following updating from .138 to .179 and performing a factory reset (as advised on this forum), it took me around an hour to re-configure the router around the following areas; Re-adding fixed IP addresses to DHCP for around 20 devices Re-adding Traffic Rules for kids PC and devices Renaming the devices in Device Manager (43 devices) Re-adding QoS Traffic Prioritisation Re-creating Ad-Blocker List (Domains) Whist I appreciate the need to perform Factory resets, especially after firmware upgrades, I feel it is imperative that a mechanism for backing up and restoring configuration data is needed urgently. I am aware that NetDuma are very open to adding feature requests to the development backlog, but it would be good have some "voting" capability for the NetDuma R2 community to influence the priority of feature request backlog (excluding defects 😊). I am sure I'm not the only one that would like such a feature to be added, but it would be great to see if this is truly the case with the rest of the R2 community. There are many product based companies in the UK that use this to great affect, where features requests are voted on. For example, new request made and the initial status is assigned (Status: Under Consideration), then if NetDuma accept the feature (Status: Accepted to Backlog), then when development starts (Status: Under Development). If not accepted (Status: Rejected). When the feature request status changes to (Under Development) a yearly quarter delivery estimate is given i.e. Q2 2020, or Q4 2020. The previous paragraph is only a suggestion, but the backup/restore feature request is something that I feel is needed to stop one getting pi##ed off every time a factory reset is required 😊 Speaking for myself, I am more than happy to support NetDuma with constructive feedback on defects on early or new firmware releases, but without the suitable tools to help make this process easier, it is a little hard to justify, when in the back of my mind, I am thinking I need to spend an hour to re-configure the router after a new firmware update, which needs a factory reset to resolve a possible issue.
  12. Hi, During the setup wizard (after factory reset), spaces are not allowed in the Wifi SSID name (Network name), however you can workaround this by editing the SSID (Network name) later from the "Network Settings->Wifi" tab, which allows spaces to be entered. @Netduma Fraser can this be addressed in the next firmware release. This caused an issue when upgrading from .138 to .179 following a factory reset.
  13. Same here RApps crashing at random intervals (not necessarily the same ones), reboot is the only way to get back up and running. Everything has been fine for the last couple of weeks, but this week, I have had to reboot at least twice a day. The only fundamental setting change made is issuing/reserving Fixed IPs in the DHCP setting to ensure that device get the same IP address. If I do not do this, old IP leases are still attached to a device (that is not online), even though a different online device has been assign that same IP address. However the name of the device shown, for example in Network Monitor is for the offline device and not the online device that is using that IP. When the Offline device comes online, it is given a new IP address, however when you click on the device in Device Manager is shows both the old IP address (which is assigned to another online device and the new IP address). There is no way of deleting the lease of old IP address without rebooting. A suggested roadmap item is the ability to "delete" IP leases instead of forcing a reboot to do the same job.
  14. After rebooting or when the router reports loss of WAN connection (PPoE), the Connection Benchmark schedule and history are deleted. This does not happen all the time, which makes it difficult to troubleshoot. Has anyone noticed this behaviour before ? The only way to get the schedule back is to re-create it, however the history is lost. Firmware: 3.0.129
  • Create New...