Jump to content


  • Content count

  • Joined

  • Last visited

  1. Still waiting for an update from the netduma team
  2. Given the really bad support given here, I am sure there are a lot of people who don't even bother raising their issues. For instance I have raised another DumaOS defect that I am facing when trying to use third party VPN clients (R1 is blocking the connections) 1,5 month ago and even though I have given all the required info to the netduma team they still haven't managed to replicate the issue. I have been requested multiple times to do their debugging for them, even if that involves downgrading/upgrading my router's firmware etc. For a "premium" gaming router this kind of support is unacceptable if you ask me... I wouldn't be surprised if the majority of the people who face issues don't even bother reporting them here...
  3. Hi guys, Did goldenfrog contact you? Any progress on replicating the issue? Regards, Georgios
  4. It could very well be that this issue happens to other people as well but me and Azlios had the technical understanding to figure out that this is not normal, the capability to articulate it and time to raise it with you guys. Of course as you say it could very well be an issue that only occurs to me and Azlios. And that most probably means that it is a hardware issue, wouldn't you agree? In my case, the original R1 that I received from you was defective (reset button problem) so I was sent a replacement R1. Could it be that the replacement R1 is a defective unit as well? Are you usually giving refurbished units for replacement or brand new ones in a situation like mine?
  5. From what I see Azlios has raised the very same issue since November(!) and it seems you still haven’t acknowledged or even managed to replicate the issue. I get your devs are busy and have a queue of backlog items, however this is unacceptable support for a £200 router. I was forced to buy a new wireless router to connect to my R1 in order to have proper WiFi!
  6. Thanks for linking your thread here. To be really honest I am really disappointed as I have raised this issue for quite some time now and it hasn’t even been acknowledged by the netduma team. It seems you are on the same boat. I ended buying an additional router to handle my WiFi devices and connected it to my R1 via LAN. I was seriously considering upgrading to one of the latest netgear DumaOS routers but after seeing how bad the support is at even replicating and acknowledging issues (you raised the very same issue back in November and you still get these generic responses!) I think I ll just go for a different router that has some decent QoS settings.
  7. Any news on the matter Jack? I was wondering: could it be that I am dealing with all these issues because I upgraded directly from the old firmware 1.03.6 to (I did not install the first version of the dumaOS 2.x)?
  8. Thanks Jack, really appreciated I ve sent a couple of log files one of which is taken right at the time when the issue occurs (its been labeled as such).
  9. Hi Jack, I have been facing some issues on pasting/attaching the whole file here as I am on the go and tried to do it from my mobile. Can you please give me the Netduma support email address to send them over as attachments via email?
  10. Quite odd thing to hear as my log file is full of DHCP daemon related messages... You see I there is no easy way to tell. This issue is not related to the DHCP lease time (it occurs regardless of what I set there) meaning there is no easy way to test this. My original thinking was to set the DHCP lease time to 10mins and the proceed with my tests. However the issue does not occur when he lease time expires but instead at a 6-7 days of time after the latest router reboot. So doing this kind of test as you suggest would definitely take more than 3-4 weeks given the fact that I am doing quite a lot of travelling for work and since the last thing I want is to experience home WiFi breaking while away and effectively disabling all my smarthome appliances (thermostat, security camera etc) I reboot the router quite often... So there is that. Is there some other way to proceed?
  11. Yes exactly. That means that once this happens nothing connected to wifi works. Security web cams, thermostat, hue lights are all useless. That is a huge problem for me as I am often away on a business trip and can't do anything about it. Yeah this is not a realistic option. Sure thing. Just to make sure that we do this right, could you please post detailed instructions, firmware file locations etc? No the LAN IP is the default ( Also I wanted to ask: Do you care reviewing my log files? Can I send over something via mail?
  12. Hi again Fraser, I am getting the exact same behaviour its just that now it seems to happen every week instead of every 2-3 days. Is there some way to fix the root cause of this issue instead of delaying its occurrence? Log files are full of DHCP related messages when this issue occurs. Would you like to take a look?
  13. No technical restriction of any sort, it’s just that I don’t have the capacity at the moment to get into a downgrading/re-upgrading loop. Of of course I will forward all relevant info. Thanks a lot for the help!
  14. Thanks Fraser I ll give it a shot
  15. Hi Fraser, since I have been in touch with my VPN provider’s support team about the very same issue, I inquired if they can supply you with a temp testing VPN account to perform the test from your side, as I am unable to downgrade my router and to the required testing.