Tripper reacted to SwiftCookie in ANNOUNCEMENT: The Future of DumaOS: Version 3.0
Lol I don't understand why people are getting so angry about the time it's taking to release 3.0. I swear people take for granted just how much the Netduma guys communicate with their consumers about problems and feedback. Looking forward to the possibility of testing it out in beta, should be great!
Tripper reacted to RedBull2k in Caddy 1.2
I thought i would start this off with its own thread.
I have expanded slightly from my first app, screen shots are below.
now you can save and load your allow and deny list. This is very ideal if you have to factory reset. plus sharing of lists is possible.
you can clear your allow/deny list with a single click.
for those of you who are fed up of seeing your offline devices can with 1 click remove all offline devices that no longer hold an ip address
you can also create your own custom black/whitlist just make a text file named with the following
and insert ip addresses, only 1 ip address per line for example
from where ever this file is saved just drag and drop into the white box, this will automatically add
here is the file
Tripper got a reaction from Netduma Admin in Fix for "DumaOS not loaded yet!" (XR500 users only)
Simple reboot fix mine
Tripper reacted to East in Could you include Dedicated Server Port(s) to Auto Ping Stats?
To help us understand what ports that need to be open/forwarded could you please consider adding an option to allow us to see what port that dedicate server is using? And include, if possible, if that port is using TCP or UDP?
I ask because developers are not including all the port ranges to the servers their game uses. Also, UnPn isn't a reliable method either. Once forwarded/prioritized it can help improve hit rego.
Tripper reacted to Netduma Alex in Ddos Detection
We are adding a feature called Data History in DumaOS 3.0 which will allow you see how much data has been used over time, both upload and download. This will help with one half of your request.
The other half (CPU usage history) is not something we've considered, but perhaps could be useful... It would certainly be useful for tech support!
I'll forward your suggestion to the developers.
Tripper got a reaction from Zippy in Halo MCC on Geo filter
Halo MCC when will the geo filter block the servers?
There are over 3 million microsoft azure servers and I have an example list below of what I'm connecting to with the geo filter on filtering mode.
Tripper reacted to Netduma Luke in ANNOUNCEMENT: The Future of DumaOS: Version 3.0
The Future of DumaOS: Version 3.0
Last year we released our first major update for DumaOS, Milestone 1.3. You guys loved it, so we quickly got to work on the next milestone, packing it full of features to make your router even more powerful.
This next milestone will instead be a new version, DumaOS 3.0, and it marks the biggest leap forward in our history. It will contain a huge amount of features never seen before on a router. Instead of just sending out each of the features piece by piece, we needed to wrap them all up into one giant release. We will explain why soon 😉 (but don't worry, we're not doing an EA!).
We know you guys will want to get your hands on 3.0 as soon as possible and we are working very hard to make this happen. But until we are sure, the release date is ‘to be confirmed’. But in the meantime, here is a teaser one of the many features coming to your router in 3.0: Data History.
With Data History you can see how much bandwidth you’ve used over time and drill-down to see which devices and/or applications are eating up all your data or find out how many hours you spent gaming over the weekend. If you are under a data cap, you can also see if you are nearing your monthly limit.
This is just a small glimpse into 3.0. We will be gradually revealing more features over the next few weeks so keep an eye out for more announcements.
One final thing, we launched DumaOS Insiders yesterday. This will be a private subforum where we share first-looks at features we are currently working on and using your feedback to shape them. There are only a few spaces left, so sign up here if you haven’t already: https://forum.netduma.com/topic/29480-sign-up-to-dumaos-insiders/
Big things are coming.
Thank you for your support.
The ND Team
Tripper reacted to Netduma Jack in Sign up to DumaOS Insiders
EDIT: The response to to this has been brilliant. Thank you. We are now locking signups - but we will leave the form up in case anyone wishes to register their interest in becoming an insider in the future.
Hi guys - we have a big announcement coming tomorrow about our next development milestone, which will be the biggest set of new features ever released for DumaOS. Our number one focus is building new features, and we want them to be the best they can be. This is why we're starting up DumaOS Insiders, where we will be sharing exclusive first-looks at some of our new features and using your feedback to shape them.
If you are interested, please sign up to DumaOS Insiders using this form:
When you sign up you will be entrusted with exclusive Insider information. Please do not share this content outside of the DumaOS Insiders subforum.
Tripper got a reaction from Fuzy in OpenVPN vs Softether
What is better?
OpenVPN is much older than SoftEther VPN
The number of supported VPN protocols is much higher with SoftEther VPN
OpenVPN barely reaches 100Mbps, SoftEther can go up to 900Mbps and even higher.
There are more platforms which support OpenVPN than SoftEther VPN and this is one important thing where OpenVPN wins.
Tripper reacted to xr500user in Device Manager Workaround(s)
This is for those of you who like to tinker with the router and the duma devs if they are looking for the fix (or maybe they know already?) and a warning if you don't know what you're doing, a factory reset will be in your future.
So I got to messing with this again today (bored) - router still up 15+ days. no reboot, no factory reset QOS still disabled. That's for another rainy day ...
In a previous post I talked about throwing arping probes at each device on the router network to try and jar them free in device manager. Arping is no good, tested. Whatever you use, it needs to actually open a pipe/socket to the device in the kernel and get a temporary entry in the arp table. An arping probe doesn't seem to do it. I tested with telnet (works, but telnet could actually get a response from a host and open a socket, and if the ip is not in use it just takes too long). Would have liked to use nc (netcat) but unfortunately nc can also get a response from a host and take too long on some types of hosts. The version of nc on the router is super limited also, missing a lot of arguments, no -w timeout option which makes it difficult. So I settled on good old ping, even though ping on the router is super limited too and is missing a lot of useful argument options (like wait time). Had to devise a tiny script that would ping all possible hosts on the LAN subnet and do it quickly with what is available by default.
In order to do this, you need telnet access to the router - need to understand how to create a script / chmod +x it, use vi, etc. basic linux stuff. if you find any improvement or better idea, let me know. so far, it works for me.
FOR DEVICE MANAGER DEVICES THAT ARE IN THE ONLINE BRANCH, BUT ARE ACTUALLY OFFLINE -OR- DEVICES THAT ARE IN THE OFFLINE BRANCH, ARE ACTUALLY OFFLINE, BUT HAVE AN ACTIVE IP SHOWING (You are Unable to Delete Device/Device has Sticky IP):
Create the script in the /tmp directory - chmod +x it and execute it:
[email protected]:/# ./<name you called it> ex ./fixip
This is the script:
### Get current LAN subnet - only first 3 octets
chkip=$(config get lan_ipaddr | sed 's/\.[0-9]*$//')
### Cycle LAN subnet - un-comment echo to see if any error
for i in $(seq 2 254)
#echo Are you really there $chkip.$i?
### Open ICMP socket to each IP on subnet & kill ping process in 1 microsecond
ping -c1 -s1 -q $chkip.$i >/dev/null & usleep 1 && kill %1 2>/dev/null
Script is getting around limited ping version on the router by sending a quick ping to each ip .2-.254 and then turning around and immediately killing the ping process in 1 microsecond-- just enough time to open the socket and get an arp entry. With the sneaky loop the script takes only 1-2 seconds to complete as opposed to 37-45 minutes if you don't kill the ping process each time - learned that lesson, lol -- if you wanted to you could put it on a cron job every 6-10 minutes or so. I did not actually time how long it takes before the arp table resets back to only actual online devices and clears all the dummy 0x0 entries. It was about 5 minutes or so after execution of the script.
if you un-commented the echo line to make sure its got the right subnet:
[email protected]:/# ./fixip
Are you really there 192.168.1.2?
Are you really there 192.168.1.3?
After the script runs (1-2 seconds) devices that were stuck online (but actually offline) will drop to the offline branch. Offline devices (really offline) in the offline branch that had IP addresses still stuck to them will clear out the ip, so you can leave them or delete them now without the "Error: Cannot delete, device is online" message.
Now we still have one scenario that this does NOT fix. Devices that are online, have an actual IP attached to them, but STUCK in the Offline branch of device manager.
Sneaky fix/cheat to that in next post ..