Jump to content

Welcome to Netduma Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!



Member Since 14 Jan 2017
Offline Last Active Jan 13 2018 09:10 PM

In Topic: Major Announcement: Netduma partner with NETGEAR to launch the Nighthawk XR50...

10 January 2018 - 05:52 PM


Hi all, 


I can't respond to you all personally so I will answer the general themes I have seen in the comments. Thank you for all the kinds words and the feedback. 



Does the XR500 have the Anti-Jitter/Anti-Spike feature?
- No, that is on our R1 roadmap.


Does this mean that it will be released in april with the duma OS or in a mystical time on the R1 Roadmap? Also as for the features does the anti spike still buffer incoming ping spikes and increases ping to compensate? or have you guys just renamed the congestion control algorithms? 

In Topic: DumaOS Update - Recent Progress

30 June 2017 - 09:52 PM

ethtool is an great program for tuning parameters for devices.

In Topic: DumaOS Update - Recent Progress

10 June 2017 - 09:18 AM

Volunteering for beta testing as im in UK have lots of technical skills to test for bugs and can offer comprehensive feedback. Also i am an early adopter.

In Topic: New Duma update

27 May 2017 - 04:03 PM

Because they clearly think that we dont deserve one! Pure and simple!

In Topic: Adel75 up down wan lan thread

20 April 2017 - 03:11 PM

Ah right i see, the only way to process incoming jitter would be with an Adaptive jitter buffer similar to what Astriek VOIP Application uses but implementing it into the tcp/ip stack through the source code could be problematic. i would be interested in seeing what scripts you run and doing some experiments between us see if we can improve on the current solution.


Modifying fq_codel parameters is a thought or implementing a AdaptiveJitterBuffer could be another.