Jump to content

Od1n

Clubhouse Member
  • Content Count

    655
  • Joined

  • Last visited

  • Days Won

    4

Od1n last won the day on July 2 2018

Od1n had the most liked content!

About Od1n

  • Rank
    Legendary

Basic Info

  • Gender
    Not Telling
  • DumaOS Routers Owned
    Netduma R1

Recent Profile Visitors

5,158 profile views
  1. Imagine fully maxing out your up- and download yet your ping only spikes by 5 milliseconds, thats what Iain pulled off in the lab. It wouldnt matter at all whats happening in your network, your ping would always be spot on. Iain posted the results on his blog a few years ago, its several pages long with lots of test results and graphs (including benchmarks against unnamed industry leading routers). Maybe that blog is still up. Yes pretty much. Iain said the router would analyze how the ping to the server is fluctuating and then add a variable delay on the fly to it to keep the ping stable. Say you set this feature to +8 milliseconds, your router would then just add an artificial 8 milliseconds delay on top of your normal ping/connection and remove a chunk from it each time the actual ping to the server would rise. A stable but slightly higher ping will give a better game experience than a lower but unstable one. And yes it may not work with high jitter connections but low to medium jitter connections could be balanced out perfectly assuming you set the artifical ping increase high enough. using Anti-Jitter and Anti-Spike at the same time could be huge! But who knows if its still a thing, last message was like 2 years ago in which a Netduma employee said its still worked on.
  2. What are the chances Anti-Spike and Anti-Jitter are part of the 4 unveiled features? Iain must have been working on those for like 5 years now, and the lab results he showed lots of years ago where quite promising already.
  3. I typed my effective connection into the bandwidth settings (85/30), should i use my advertised speed there? That wouldnt really make that much sense, right? Either way for those facing the same problem, everything was as Fraser wrote above ecept for the following which solved it: After that it worked again!
  4. Hey guys, basically my QoS doesnt work anymore. Its set to 70% - 70% for both up- and download with "Always" ticked but on speedtests or other bandwidth tests i get 100% of my connection and the ping obviously spikes. I have had this once every now and then with the old R1 firmware and it could be solved by pressing the restart button in the R1 interface. This doesnt seem to be available anymore though, any idea on how to solve it? A quick re-powering of the R1 didnt help. In case its needed: - R1 is in DHCP mode with all network devices connected to the R1 - ISP router is set to modem mode and communicates via DHCP to the R1 - I have a 100/40 connection and effectively get 85/30 out of that. With QoS 70% it should result in 60/21 but i still get 85/30
  5. When will we be able to change the congestion algorithm that the R1 uses? In the last few seconds of this Netduma announcement video you can see the download graph and it looks like Cubic Congestion Control is used. This is sub-optimal for gaming since it doesnt consider roundtrip time or other metrics that are relevant for gaming devices in your network. And using Cubic is probably also the reason for why we are forced to set our connections to 70% to prevent congestion. Ages ago Iain claimed to have created a congestion control algorithm that in his lab allowed him to max out his complete connection while his ping only spiked by 5 milliseconds. Googles BBR Congestion Control is very close to what he promissed, is out for several years now and could probably be implemented very quickly by you guys. For those who dont fully understand what i mean here is a picture from google: In the last few seconds of the Netduma Video above you can see the bandwidth graph which basically looks like left graph below in the picture. This is bad and causes lag. What you want is the right graph it gives more bandwidth AND less lag. It has some downsides but those could be adressed by the R1 only assigning BBR to gaming devices for example.
  6. This was suggested in the first week the geo-filter came out, took a long while but its finally here haha. The feature will highly depend on the accuracy of the server list, will we see more frequent updates then? Also now im curious about Anti Jitter and Anti Spike ;).
  7. But does that vision go hand in hand with what the customer wants? It took 3 years to come up with DumaOS which is bascially just a nicer looking modular OS but with pretty much 0 new features. The post release roadmap was to deliver modular feature add-ons in short succession. But that has long been droped and now (for whatever reason) everything has to be bundled into one new DumaOS 3.0 which totally works against the initial modular approach. So why again have we waited 3 years for DumaOS then?! I start to get the feeling that the main driving factor for DumaOS was Netgear and that there MUST be a reason for why those "over-promissed" features havent been released individually yet. The original R1 OS may have had some expansion bottlenecks, but at least it was WAY more responsive and easier on the CPU. I mean the new DumaOS isnt even mobile compatible, and its 2020! And to come back to my first sentence about what the customer wants, i could care less about another overhaul of the netduma interface or its traffic monitor. The R1 is a gaming router and not a device for network engineers who need to track down traffic sources. So why would a gamer need a traffic history in the first place? People who need that buy different routers with far more monitor capabilities. The idea of the R1 is to activate congestion control and forget about lag and all the complicated stuff. And talking about congestion control, last year some really impressive progress has been made in terms of congestion control. And it will not take that much longer until you can natively use those with Linux. So the R1 will soon get some severe and free competition that doesnt require you to reduce your bandwith to 70%. Im curious to see who is faster with the release, but deep down i already know the answer. Plus im not even sure if the R1 congestion control can beat Googles congestion control from 2016, Iain didnt include it in the benchmarks from 4 years ago. Netgear isnt stupid, when taking the congestion control out of the equation there isnt all that much that separates the R1 from the competition. Geo filtering becomes less and less important as more and more games use dedi servers plus dont enforce world wide lobbies. And the VPN function kills the R1 CPU plus most competitive shooters straight up ban you for VPN-ing anyway. After 4 years you guys better have some REALLY good features in the oven. Luckily it is no longer our job as the community to make pressure but for the first time the competition will now do that. And maybe you will listen more to what they have to say than what we had to say over the last 4 years...
  8. Even if things are still confidential you can give out monthly updates that contain informations like - very persistant bug has been found that gave us troubles for weeks now - new feature we cannot unveil yet is currently being tested, things are looking very good - for next month we want to refine our congestion interface and discuss new features All it requires is a 5-10 minutes meeting once a month with the netduma staff to define the boundaries of what will be shared and what not. It really isnt a huge effort but will greatly please your community. You will get much less ETA questions that way. Overall it might require 1 hour per month to pull this off, and its not really hard to keeping certain things confidential while still sharing the general development progress.
  9. Thats nice but you should still consider to upgrade your communication channels. The biggest backlash that netduma received wasnt about the over-promissing or missed release dates but about giving only 2 statements within 3 years. Everyone was completely left in the dark! I used to regularly read and post in this forum when Iain and Luke used to post here too and shared their thoughts and development progress (regardless of it they made progress or not). Nowadays i read the forum maybe once every 5-6 month as i can be certain not a single announcement on the progess has been shared since my last visit. This could easily be changed by giving out monthly update announcements... Also curious to see if we will ever get those over-promissed features like anti-spike or anti-jitter, last time we heard about those was like 2+ years ago... Iain showed lab results of +5ms spike with 100% maxed out up- and download...
  10. At least in my country most ISPs use IPv6 addresses and give out dual stack routers cause IPv4 addresses are either only for business customers or have to be "rented" for additional money. This might be different in other countries but IPv4 addresses will become more and more expensive so eventually all ISPs will cheap out on regular private customers. So im all up for a better IPv6 R1 support. @SwiftCookie Yes it isnt but netduma also has 0 interest in selling a 2020 model and getting a netgear isnt really a great option either as you then either get features delayed or the netgear staff straight up rejects them. If netduma continues to plan with the R1 then IPv6 is necessary.
  11. Id like to suggest two things 1) Give us a more advanced network monitor for the R1 where we for example can inspect what DHCP packets it receives plus the option to change those. That way we can trick spying devices such as Google Home or Alexa via changed DNS that they should send their accumulated user data to some arbitrary non-existant address rather than to the Google or Amazon server. 2) Same as above but fully automated so the user doesnt have the (obvisouly very powerfull) monitor and manipulation rights. Say you can pick from a list of existing hosts in your network one device and everything is then handled automatically for it. Yes i can use third party software and/or hardware to achieve that, but the R1 is all about having features that no other router has and a feature to block devices like Alexa without rendering them unuseable surely would be something a lot of people might be interested in.
  12. So you play with a 200€ controller that has features such as super precise analog sticks, trigger stop and paddles giving you a HUGE advantage over regular controller players yet you complain about XIM users? Guess you re one of the people who always find something to complain about unless they have ALL the advantages for themselfs. And sure go buy the XIM, youd not be the first to realize that a mouse doesnt turn you into a Shroud. Just like with a controller you have to grind for years to become good.
  13. Notification for those also reading this topic: DCHP reduced my R1 CPU load from PPPoE @ 70-90% on bandwidth load to DHCP @ 30-50% on bandwidth load Connection is currently 50 down 10 up so not even that fast. Overall a huge difference, when i switch to 100 down 40 up in the next month or two im quite confident that the R1 will deliver those speeds without any problems :).
  14. Well i just ticked the DHCP box in the R1 Network Settings and it worked without any additional adjustments required. Only thing, should i set in the fritzbox that the IPs given out by DHCP are static? Does it matter for the R1 if it gets a different IP once every now and then?
  15. The R1 doesnt show me an IP under that setting, it just looks like the following. Any other way to optain the IP or the R1?
×
×
  • Create New...