Jump to content


  • Content Count

  • Joined

  • Days Won


Raikun last won the day on March 29 2020

Raikun had the most liked content!

1 Follower

About Raikun

  • Rank
  • Birthday June 17

Basic Info

  • Gender
  • DumaOS Routers Owned
    Netduma R1
    Netduma R2


  • Gamer Type
    PC Gamer
    Console Gamer
  • Favourite Genres
  • Connection Speed

Recent Profile Visitors

1,591 profile views
  1. UPDATE: So I have my router's IP attached to a public subdomain that I own ( I access it thru encrypted web sessions), and I discovered that Connection Benchmark works perfectly if I use the internal IP rather than the subdomain. So I guess that puts the issue to rest. Thanks for the help @Netduma Fraser
  2. I haven't tried it but it did last time I checked. I'll get on it as soon as I finish work and report back.
  3. New twist. Traffic Controller also does not allow me to Add Rule. Same behavior as Connection Benchmark. And Rapp Store looks like this:
  4. Don't think that's it. The modem is an ARRIS and I personally configured it on Bridge mode, so I could point my own subdomain to the router's interface. Plus, before upgrading to the last firmware version, it used to work.
  5. Sure, uncropped screenshot attached. Also, Adblocker is disabled.
  6. Here it is: I also disabled IPv6 but to no avail. In the above screenshot, I hit Run test and nothing happens.
  7. Chrome latest version on Macbook Catalina
  8. I'm having trouble starting the Connection Benchmark on my R2, firmware version 3.0.205, where if I click the Run Test button nothing happens, and after checking the logs, I see the following message: rm: can't remove '/tmp/benchmark/history/*': No such file or directory Any assistance would be greatly appreciated. PS: I have already reinstalled firmware with Factory Defaults, just as a necessary precaution.
  9. So it's been a bit over a week since I got the current firmware and same as when I criticize something, I should give props as well, so here goes: Firmware is quite solid, and my biggest pet peeve, which was having to reboot every few days or so, seems to be a thing of the past. I initially upgraded over current settings (I know the risks, just wanted to test that functionality), and the only thing that seemed broken was the Connection Benchmark, which worked again once I performed a full factory reset. I can finally disable Adblocker for specific devices, and the selection actually sticks, which is amazing. I feel the lists are a bit aggressive at times, but as long as I can add my own from PiHole (which I can), I'm good. I never really had any issues with WiFi, but it does feel a bit faster, although that might be the placebo effect that comes from factory resetting. Time will tell, but no complaints there. Small issue I had, but now we can add special characters to passwords, which to me, represents a whole lot of peace of mind. I always knew it was a minor bug, but one that had me changing the password on all my devices. Not critical, but weird and quite a hassle. QoS auto setup is more conservative and accurate now. I always go with 70/70 myself manually, but the auto setup goes a long way for new adopters. Kudos on that! Rapps feel more responsive, and less prone to loading issues. I assume this will only get better as more development resources as well as time get poured over the product. As I said, if you take the time to be critical, you should also make an effort to to praise as well. I still believe communication and actual delivery of the firmware are the dark spots on an otherwise great device, but no product is perfect. Keep it up folks, and special shoutout to @Netduma Fraser for putting up with my complaining ass. You are the real MVP.
  10. That's my issue. I don't think anyone here blames Fraser for any delays, but sadly he's the only face we come in contact to, so we resort to pinging him for updates. I'd love to get a Dev in here and at least acknowledge the need for information, I mean, If you take your car to the shop, you might be greeted by a salesperson, but you need answers from the mechanic.
  11. Title says it all. @Netduma Fraser A bit more transparency and less closing threads that aren't even close to being uncivil or insulting. We bought a new version of a product, knowing full well of the sketchy update history of previous iterations (still stuck in Beta for R1 I believe?), and yet again, we find ourselves waiting for new firmware on a device which is less than 6 months old. Not demanding for anything, just clarity for your customers. That's all.
  12. The more things change the more they stay the same. Sad thing is, it's not even @Netduma Fraser fault, he's just the one who deals with us. But yeah, great hardware, solid software, super crappy update process.
  • Create New...