Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 04/02/2019 in all areas

  1. 26 points
    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
  2. 21 points
    Hi Everyone, We hope you and your families are keeping safe. The virus is going to be a challenge for everybody, but at Netduma we are doing everything we can to power through it. Some of us are now working from home, but we will not let it slow us down in delivering DumaOS 3.0 to you. After all, the quality of your online gaming & home network is an even higher priority than before! We will also be keeping all our support channels open as usual in case you're having any problems. The whole team is safe and we hope you are as well. The Netduma Team
  3. 19 points
    Netduma Jack

    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: https://forms.gle/4TptvkBkqBfVeW669 When you sign up you will be entrusted with exclusive Insider information. Please do not share this content outside of the DumaOS Insiders subforum.
  4. 14 points
    RedBull2k

    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 Server_Blacklist.txt Server_Whitelist.txt Peer_Blacklist.txt Peer_Whitelist.txt 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 caddy 1.0 caddy 1.1 caddy 1.2 @Mobel @GHOST-1-EC @TrayDay @MikeyPython @Sable @WalkedDave @Bert @Locosano @Sherman85 @DanyKTM @Zippy @Grafti @Fuzy @[email protected] @HaBlo0
  5. 9 points
    I've now owned the XR500 for 1.5 years and to this day: No IPv6 without killing off the QOS. No USB printer support. Incorrect network activity stats. No control over VPN settings. Bugs and glitches in the management GUI. Very questionable QOS performance is some games. Very poor update support. At this point this product should be considered as abandonware. Netduma's/Netgear's lack for transparency with such a vocal community is truly disturbing. There are other manufacturers with devices out there that have a much more active support than Netgear/Netduma and according to my preliminary research, as good, if not better implementations of QOS and AQM. I am no longer actively using this router and will soon be totally replacing it. Hats off to those of you who will be sticking around for the long haul, still beta testing a 2 year old AC router.
  6. 7 points
    IPV6 is coming! We’ve got it working on our development units
  7. 7 points
    Killhippie

    Xr500 firmware updates

    While I do see your point, Jack. Something feels like it has changed behind the scenes. NTGR always give out quarterly updates for bug fixes and updates like the R7800's update to dnsmasq 2.78 and login password enhancement in 1.0.2.62 for routers that are current and worth their time and effort as they are still bring in cash, the R7000 is a good eaxple of a router that was kept going well past its sell by date because it worked so well, and people kept buying them. Anyway back to the router in hand, you could add the promised new icons for different devices, you could work out why UPnP does not show on Macs running Safari and Firefox. There are the leaks in the VPN app that need fixing, the messed up port table view and inconsistent actions of the old view (still showing devices online that are not) General bug fixes are needed on the way to milestone 1.4, tbh I have no need to know what's ahead but I am more interested in the here and now and the bugs that exist now. Also updates to present issues which were kind of promised, like simply providing more icons for devices was talked about early last year in march I think although I may be mistaken, anyway well before talk of milestones, but when milestone 1.3 hit we never got them. Software development is very complicated more so than maybe I can imagine, but you cant leave everything and just concentrate on the latest and greatest milestones and new routers for NTGR which I'm sure you have been asked to furnish with DumaOS and at the same time just not fix current issues, its like the XR450/500/700 have to be shelved because you don't have the manpower to look after them and develop new firmware for new upcoming hardware and Milestone1.4 at the same time. This is why I feel unsettled I have to say. Voxel and kamaj keep posting new updates for the R7800 NTGR fork as well as NTGR themselves and that router even though the hardware is almost identical was released in January 2016, Its a very popular model, and there's the rub. NTGR don't just stop pushing updates to their kit, there are always bugs to fix, and I am sure you have versions of DumaOS that would cure some of the GUI issues, and patch other issues in milestone 1.3 I would hope. So keeping a small team working on the bugs of the XR range would be surely prudent? Right now having a router sit idle with no updates, and not a whiff of when the router will get one leaves me to think that Netduma and NTGR have other plans with the new AX devices and these current routers will be at some point hit with EOL because of a lack of interest and ultimately financial gain by NTGR. Of course I could be very wrong, and I hope I am but in all my years of using NTGR hardware the silence has never been so deafening. NTGR are here to make a profit and that's what they should be doing, you guys are too, your company has to grow as well. You want DumaOS to evolve, but when I realised the last update to the XR450/500 was December 2018 it felt quiet perturbing. I do not believe there are no security fixes that need patching, and that Netduma have nothing in milestone 1.3 that needs tweaking, we know there are issues, but If its going to be that we now wait for new milestones before we get updates from Netduma/NTGR the gaps in between updates will be to long and current bugs will just remain unfixed and people will just move on as the router is not behaving in a stable enough fashion. Being both reactive and proactive and keep people updated with fixes so they know their hardware is as up to date as possible while squashing as many current bugs as you can is just as important as working on new versions of DumaOS. Imagine if say Apple only released iOS 12 and never patched it to sort out GUI bugs and security issues until iOS 13 a year later, that would be the death of them. The same with Android being patched monthly on some devices too, I guess my point is there are always things to fix. As it stands right now it feels like present hardware is kind of less important due to things happening behind the scenes we are not privy to which is fair enough, but when there are patches to put out so why are you not pushing them to NTGR and more worryingly why are NTGR not just updating their firmware if nothing else. The current hardware and and how it works will determine the future of new hardware by proxy if you see my point. If people just see inactivity for months on end why would they buy into new versions of NTGR gaming hardware and DumaOS if the same thing will happen again. I know you guys are busy, and I appreciate the hard work you put in, but it does feel like the old hardware is just gaining dust while Netduma works on new versions of DumaOS, as well as new hardware from NTGR that you need to furnish with DumaOS as well. That's just how I feel, I may be well off the mark and I really hope I am, but equally I hope you can understand my fears, during this period of dormancy
  8. 6 points
    Killhippie

    XR500 DDwrt Firmware

    Shame Voxel does not have a XR500 and the ability to update the really old code in the XR router line up. Who pays Hundreds for a XR300 (no Hybrid VPN) XR450, XR500 or XR700 to have modules from 13 years ago or even old versions of OpenSSL which is needed for OpenVPN (and I guess DumaOS's Hybrid VPN too, as it uses hardware acceleration on the XR500, but obviously I cannot be sure) for its 256-bit OpenSSL encryption. Anyway the XR500's OpenSSL version 1.02n is from December 2017, not exactly current or really that secure. I know I go on about this stuff, but it should be current, as Voxels and Merlins firmware versions are. If people with full time jobs like Voxel can compile the firmware with new packages, why cant a huge company like Netgear do it, or their partners 😒
  9. 5 points
    I HAVE UPDATED IT FOR COD MW READ JUST BELOW HOPE ITS NOT TO CONFUSING BUT THIS TOPIC WAS STARTED A LONG TIME AGO It also now shows you how to traffic protize cod mw ports 2019 below I WILL POST COD MW PORTS jUST BELOW HERE these are the ones i found so far i will keep updating it with new ones here I recently upgraded to new dumar os fw and think its great but its missing one thing important i think In network monitor it now does not show you what ports the game you play is connected to uses In cod bo4 now cod mw 20019 i used this feature all the time In cod bo4 same for cod mw19 everytime you would join a new lobby it would show us new ports it was connected to. You would always be connected to two ports in every game this first port is always port 3074 udp the second was always diffrent ever new lobby you join uses diffrent ports If you stayed in the same lobby for an hour the two ports would be the same for an hour or how long you stayed in that lobby . Once you change lobbys the game changes ports it uses so you need to put new ports in traffic priortaztion I think this is why the connection keeps varying For cod mw 2019 its now three ports instead of two HERES WHY ITS IMPORTANT when i put in the ports it uses for that game in traffic priortization my hit registration would get a lot lot better i did this before on cod ww2 now i do it for cod mw2019 and it helped my hit registration .And on cod bo4 Somtimes i would do this during a game. i would be playing a game and struggling to get a kill then in same lobby same people playing i would enter those port number in and the hit registration was great easier kills same for cod mw2019 EVEN IF YOUR NOT PLAYING COD you still might need it for other games. i used it for all my other games to help get a better connection and i would like to use it in the future for new games I really dont wanna downgrade to an older fw just to use this feature as it was so GREAT SO ANY GAME YOU WANNA SEE WHAT PORTS IT USES YOU NEED THIS As some games it dosent tell you all the ports it uses I would love to use this for red dead redemption 2 online when its released soon Fraser told me if enough peole want this feture back in the firmware they would put it back in SO I JUST PUT A POLL UP SO PLEASE VOTE THANKY YOU So i am asking any who might use it before or might wanna use it in the future please vote on the poll here if you would like to see it in i future update I hope i made sence sorry for any typos And please post to say you would like it the more people who say they want it they saidthey would reinstall it if the demands there Thanks i have now edited to update for cod mw READ FROM HERE for cod mw 2019 and how to set up ports correctly From members who know how to set it up correctly below RL317 shows how to in this post below He knows more about it than i do ahe advised me how to set it up correctly Just letting you guys know i think now playing cod mw that the next update that the dumar has has to reinstall the older network monitor My hit detection \hit registration is now brilliant since i done these steps Heres why If you want your hit registration or hit detection to be great read this When playing cod mw the game uses 3 ports to play thats if you want godd hit detection \hit registration The first is port 3074 this is on ps4 i think its 3075 on xbox but i am not sure i dont know about pc The second port stays the same untill you restart the game i think this is the data centre or either matchmaking The 3rd port is changes every new game this is the dedi or peer your playing on Thats why you see new people every game and thats why you do good one game but not the next Thats because you changed dedis and the ports have changed So thats why you need 3 ports every game the first is 3074 the send is the matchmaking or data centre the 3rd is for the game mode you play Atm i am making a list for the ports it uses Just letting you know you can do this yourself to see what ports is needed but you have to downgrade to the older firmware well thats on netdumar1 I dont know about other routers Also this cane be done if you have a router with openwrt on it You would have to ask admins as i dont know anything about the other routers Heres a way to put the ports in traffic priortization Source 3074-3075 destination 30000-45000 udp rule 1 Source 30000-45000 destination 3074-3075 udp rule 2 Source 3074-3075 destination 3100-3500 udp rule 3 not nessasery optional Source 3100-3500 destination 3074-3075 udp rule 4 not nessssery optional HERES A LOAD OF PORTS TH GAMES COD MW USES Heres is a copy of my upnp settings screen after playing a losd of cod mw 2019 192.168.88.119 9308 9308 192.168.88.119 UDP DemonwarePortMapping 3074 3074 192.168.88.119 UDP DemonwarePortMapping 3163 3074 192.168.88.55 UDP DemonwarePortMapping 3153 3074 192.168.88.55 UDP DemonwarePortMapping 3172 3074 192.168.88.55 UDP DemonwarePortMapping 3184 3074 192.168.88.55 UDP DemonwarePortMapping 3155 3074 192.168.88.55 UDP DemonwarePortMapping 3123 3074 192.168.88.55 UDP DemonwarePortMapping 3102 3074 192.168.88.55 UDP DemonwarePortMapping 3148 3074 192.168.88.55 UDP DemonwarePortMapping 3111 3074 192.168.88.55 UDP DemonwarePortMapping 3124 3074 192.168.88.55 UDP DemonwarePortMapping 3131 3074 192.168.88.55 UDP DemonwarePortMapping 3150 3074 192.168.88.55 UDP DemonwarePortMapping 3192 3074 192.168.88.55 UDP DemonwarePortMapping 3176 3074 192.168.88.55 UDP DemonwarePortMapping 3125 3074 192.168.88.55 UDP DemonwarePortMapping 3129 3074 192.168.88.55 UDP DemonwarePortMapping 3177 3074 192.168.88.55 UDP DemonwarePortMapping 3115 3074 192.168.88.55 UDP DemonwarePortMapping 3162 3074 192.168.88.55 UDP DemonwarePortMapping 3116 3074 192.168.88.55 UDP DemonwarePortMapping 3147 3074 192.168.88.55 UDP DemonwarePortMapping 3134 3074 192.168.88.55 UDP DemonwarePortMapping 3133 3074 192.168.88.55 UDP DemonwarePortMapping 3100 3074 192.168.88.55 UDP DemonwarePortMapping 3109 3074 192.168.88.55 UDP DemonwarePortMapping 3095 3074 192.168.88.55 UDP DemonwarePortMapping 3127 3074 192.168.88.55 UDP DemonwarePortMapping 3190 3074 192.168.88.55 UDP DemonwarePortMapping 3117 3074 192.168.88.55 UDP DemonwarePortMapping 3126 3074 192.168.88.55 UDP DemonwarePortMapping 3084 3074 192.168.88.55 UDP DemonwarePortMapping 3182 3074 192.168.88.55 UDP DemonwarePortMapping 3138 3074 192.168.88.55 UDP DemonwarePortMapping 3175 3074 192.168.88.55 UDP DemonwarePortMapping 3171 3074 192.168.88.55 UDP DemonwarePortMapping 3165 3074 192.168.88.55 UDP DemonwarePortMapping 3180 3074 192.168.88.55 UDP DemonwarePortMapping 3169 3074 192.168.88.55 UDP DemonwarePortMapping 3085 3074 192.168.88.55 UDP DemonwarePortMapping 3105 3074 192.168.88.55 UDPDemonwarePortMapping 3194 3074 192.168.88.55 UDP DemonwarePortMapping 3074 3074 192.168.88.55 UDP 192.168.88.55 9308 9308 192.168.88.55 UDP Btw i noticed everytime i reset cod mw 2019 these more was added they were added one at a time So i thought these ports are needed as well but now i think there optsinal Here are the ports network monitor shows are in use for cod mw 2019 i will add more when i find them 30410 35710 30350 31300 35300 37160 31350 36360 32700 32710 39860 38280 39500 42420 43300 30040 30080 32560 31080 32540 30110 30020 30030 30070 30230 30500 30600 31030 32930 33640 34260 36050 36290 36930 39550 43610 43840 44790 30020 :30010 :32680 32310 :32350 :30190 :34790 :34790 :30070 30100 32560 :32580 30060 33420 33420 40820 36800 32310 30550 30520 30130 30060 35310 32550 30040 30310 30160 32590 39300 32460 32490 32550 35800 3258032570 These ports made into a range by east so thank you to them They have a brilliant guide on these forums i recken you guys read it I think its the best one Please if you found this helpful please vote this thread was started over a year ago and we are still have no clue if there gonna bring it back SORRY IF I DOUBLE POSTED A FEW PORTS TWICE BUT I HAVENT HAD TIME TO EDIT THIE LIST YET BTW ANY PORTS LISTED BELOW HERE ARE FOR OLDER COD But you can still see how the people use traffick prortization correctly you just input your ports instead of the outdated ones
  10. 5 points
    PUBzZz

    how to get better hit detection

    Yeah I been using different variations of prioritizing over the past week or so to see what gives me the best results game after game day after day. I have MW on both PS4 and Xbox and test all setups on both. I just like to ask questions when people throw info out so that I'm clear on what they are saying so I can test it. My opinion on this is first and foremost this all starts by not using the Anti Bufferbloat sliders. If you use those that's where the problems start. Prioritizing the ports is the gravy in all this. However too much gravy and you mess the meal up. I just kind of feel the Duma Team could have gave us all this data. I mean they can pull that raw data real quick and break it down step by step for a universal way for everyone to setup.
  11. 5 points
    Be respectful to one another, mobel is Just trying to help, he is giving you decent advice, although it isn’t helping your situation.
  12. 5 points
    bagsta69

    MW4 open nat PS4

    Hi all, I played the Alpha and had moderate nat type, Just played a few games on the beta with moderate nat and did a few changes to get open nat. Playstation static Ip adress Turn off upnp TCP and UDP external and internal port range 3074 =NAT TYPE OPEN
  13. 5 points
    Fuzy

    Xr500 firmware updates

  14. 4 points
  15. 4 points
    Killhippie

    Devices not showing online

    Isn't it a known bug, Alex? There have been a lot of people with this issue including myself. Hopefully one that 3.0 will fix, even though Netduma haven't actually patched it, just re wrote it so it now works (isn't that technically patching?) from what Fraser said and of course if I got the gist of what he was saying correct. Looking forward to seeing these bugs vanish with DumaOS 3.0.
  16. 4 points
    I'm sorry, but I've never seen such a lack of competence with firmware updates. Other companies release firmware updates on frequent bases, but the response that we hear over and over and over at Netduma is "Were have a lot of features in the pipeline, but we don't know when Netgear will release them". Literally half a year will go by with the same nonsense. You guys really need to revise your business model. Releasing firmware updates every 2 years? Seriously?
  17. 4 points
    Im certain i got it now. this is the boy that is right.
  18. 4 points
    Netduma Alex

    Were these routers given up on?

    I don't know how much i'm allowed to say regarding which hardware we'll put DumaOS 3.0 on due to legal mumbo jumbo that i'm restrained by... What I will say is that we're not dropping support for any existing hardware, and we're planning to release DumaOS 3.0 for every current DumaOS device. I can't promise it yet, but that's what we're planning on.
  19. 4 points
    Netduma Alex

    New profile fields

    I just made a few small changes to profiles. It is now mandatory to specify which DumaOS routers you own. You will be asked this question when you next sign in. This will help us loads with tech support! There are now optional profile fields for Discord, Steam, PlayStation Network, Xbox Live, Nintendo Switch and Battle.net - please suggest any more you would like added Some old/outdated protocols were removed, such as MSN, ICQ, AIM and Jabber. Thanks for being a part of the community! EDIT: I'll add Twitter as well EDIT2: You can now use Facebook to login to the forums if you feel like it
  20. 4 points
    If we do that we'll let you know. For the moment keep an eye out for more feature teases over the next few weeks.
  21. 4 points
    Netduma Alex

    Sign up to DumaOS Insiders

    You can thank Jack for that He's also just spruced up the icons on the forums
  22. 4 points
    People need to realize that the ultimate owner of the XR series IS NetGear. If you want to keep complaining and nagging, then you should be discussing this over on the NetGear forums and or filing support tickets. NetDuma is only the 3rd Party or Co-Developer for a portion of the FW that is developed and marketed BY NetGear. NetGear holds all the plans, policy's and release dates of when actual FW updates that go to public. It's up to NetGear and NetDuma to work together in getting code fixed based on which side of the code needs fixing. If there is problems with the NetDuma portion, then NetDuma needs to get this corrected then handed back to NetGear. If there are problems on the NetGear side of the fence, then NetDuma has nothing to do with it and NetGear needs to make the corrections. However NetGear needs to know what all the problems are first and foremost. There's a long processing and development and in house testing that needs to be done. So this can take a long time, several months. So FW just cant' be released willy nilly based on users complaints and nagging. If there are legitimate complaints, users need to post about these in the NetGear forums as well as NetDuma and troubleshooting should be performed to narrow down where the real problem is and also might find out which side of the fence it resides. I most cases, this will be NetGear and they need to see and review ALL information to determine who needs to take corrective actions. IMO, most of you people are barking up the wrong tree. If you want to voice your opinions and complaints, you need to field them with NetGear first. They hold the entire responsibility of the XR series. It's there product. If this was a NetDuma R series router, then you would be in the right right tree. Please give NetDuma a break on this. They can only do so much and say so much. There are reasons why the public gets limited information about FW updates and product releases. This is business and how router business is ran. Be patient and show some understanding.
  23. 4 points
    CrossFitKila717

    Need Help With XR500

    I gotcha man.......go to “firewall” tab, then you’ll see “IP Passthrough”. Click that & choose device (xr500 should show up). Select that and select “fixed” on the other drop down. It’s pretty much that simple. There’s only IP Passthrough not Bridge mode. Restart your device under “device” tab, then your console. Should see “open” NAT as well. Make sure to turn your WiFi off on the gateway as well, assuming you’re using the WiFi from xr500. All port forwarding done through the xr500 as well.....don’t do any funky things to the Gateway, just leave that as is......remember, it’s just passing your IP through it. All control is at xr500.
  24. 4 points
    BIG__DOG

    Upcoming xr500 firmware upnp fix

    All Firmware releases are down to Netgear and when they roll them out. Using port forwarding is 100% reliable which is more than can be said for upnp on any router as upnp is not 100% guaranteed to open all ports that are needed. If you want to try port forwarding then follow this simple guide but remember to disable upnp as it hinders port forwarding and causes conflicts. https://portforward.com/netgear/nighthawk-xr500/
  25. 3 points
    Pingplotter is ICMP ping and games like battlefield measure their loss on UDP packets. When there is traffic congestion across your ISP etc, UDP packets are the first ones to get dropped. Because UDP packets do not get resend while TCP/IP does. So that could explain why pingplotter is fine and your UDP traffic isn't.
  26. 3 points
    We've made notes of everyone who has expressed an interest in the beta. We may make an official list closer to the time for people to sign up to.
  27. 3 points
    Netduma Alex

    Net duma keep restarting

    Could you please email [email protected] with a copy of your invoice/order number?
  28. 3 points
    Netduma Alex

    Servers Set To Peer

    We've been whitelisting and moving lots of servers around, but we haven't updated the server definitions in a little while. I'll be sending out another cloud update this week.
  29. 3 points
    TeCNeEk

    New XR500 owner needs big time HELP!

    Thanks for that! A technician is coming tomorrow so I will find out how everything goes.
  30. 3 points
    Grafti

    Holy Crap

    Let me ask you the fire question: Does this configuration works in 5 games in a row, and at the next day is still working? (we could make the "5 games in a row challenge" in this forum just to guess what settings are good 😂😂)
  31. 3 points
    My setup: Isp Modem/Router > XR500 > PS4 (via ethernet) + 4 other devices connected via wifi. My PS4 has a reserved static ip address, i use UPNP only, no DMZ, Port Forwarding or Port Triggering as this will cause the range overlaps that you are experiencing. I have increased my Qos advanced / manual rules to 10 by 10 - 20 in total (Source > Destination Ports and Destination > Source Ports - I only use the UDP protocol) All rules created are taken from several wireshark captures i did for BO4, Modern Warfare and even tested Apex for a forum member who asked me for help. Unfortunately i dont have the R1 or a PC or Xbox to test which ports are priority on them. ABB were set to 98%/98% and then set to 'Never' which illiminates the sliders settings. Qos bandwith flower has the PS4 receiving 40% on both the upload and download with 'Share Excess' disabled. With all of these settings i still most importantly have to have the correct loadout on my weapons and play the correct lines on the map - spawn prediction where possible and playing behind the UAV and Dead Silence and other perks or streaks. Hope this info helps you or anyone else having issues.
  32. 3 points
    Bat 'n' Ball

    XR500 freeze? Logs?

    Hi Netduma Fraser, Thanks for your reply. If I have issues again, I'll follow your suggestions and post back to this thread.
  33. 3 points
    LOL. Actually it's total BS. You cannot magically increase server tickrate from 60Hz to 120Hz. So whatever you are seeing in DumaOS is a measuring error. Battlenonsense has tested with wireshark, not DumaOS. Cables. Maximum bandwidth quoted for a cat 8 cable is 2000 Mhz. That is what the cable can sustain at peak performance. But if you hook it up to a 1GBps port the port will always be limited to 125 Mhz. So you can have a cable that is able to sustain 2000 MHz but it won't do anything for you as long as it's a 1GBps port, since maximum transmission frequency is only 125 MHz. The cable is a dumb piece of copper that can't decide data frequency on it's own. For higher transferspeeds, not only do the networking ports increase their operating frequency, but also they use a completely different transfer protocol. (1GBps = 125 MHz, 10Gbps = 800 MHz, so if you punch that in a calculator, (800 / 125)*1000 = 6,4Gbps, so something doesn't add up there. 10 GBPs uses more bits per amplitude than 1Gbps, but this is not applied until you stick the cable in a 10Gbps port. In short, using Cat.8 cables in a 1 Gbps system will do absolutely nothing for you. Or to use some analogy. My car has a top speed of 250 km/u. I can drive on a 4 lane highway with 250 km/u. But if there is no other car on the road it won't get me there faster than a 2 lane highway. In theory you can see reduced latency by scaling up the network. Ie on a 10Mbps system, sending a ethernet frame (max 1522 bytes) takes about 0.1ms, on 1Gbps system it takes 0.001ms. I'm sure you realize how insignificant these numbers are.
  34. 3 points
    So i finally figured it out after i had to factory reset my phone. When i did this i started getting no internet at all for my phone , even after a delay. I set everything to static and hard set my dns to google. After i did this i had internet instantly. After a bit of fiddling i figured out it is indeed my PiHole acting up(seems like my new ISPs way of doing stuff puts off my pihole, as before it had no problem). I am very sorry for wasting your time, you very correct from the beginning. All i had to do was set my dns to a set one other than pihole on the phone AND flush my internet settings (seems like the pihole dns was getting cached so just changing without flushing didnt help, thats why i didnt notice. It stucks even through phone resets). Thank you so much and sorry i wasted your time.
  35. 3 points
    Killhippie

    High Priority Traffic Bug

    Was not graphical on mine as my antibufferbloat settings stayed applied with the light on, no rules added, Jack. Just DumaOS classified games ticked and unticking them , turning off antibufferbloat and even QoS didn't stop the issue it was just in a frozen state thinking something was high priorty traffic I even had a friend pull the plug on my TV etc and I turned off all the wifi devices and it still stayed on, always had to be a reboot and since I'm in a wheelchair and my router is high up that was really hard work if in the end a reset (using the reset button on the back always seemed to give a cleaner reset oddly enough) was needed as it seemed to do it more and more often until a factory reset was performed and then it would be okay for a while, until a long gaming session on Destiny 2
  36. 3 points
    Is there something you would have liked to see or hear that we didn't mention? If you're having issues with the router just make a new topic and we'll be glad to help.
  37. 3 points
    Try this 1. Place geo location on top of server of choice smallest radius(69) 2. Boot game with filtering mode on 3.once you see all servers being blocked and your at the main multiplayer menu expanded the radius between 600-1000 miles 4. Search for a game Let me know if you have any luck
  38. 3 points
    Thanks for the feedback. I appreciate it's frustrating to have to wait so long for an update, but I assure you that this upcoming version update is totally real, and totally on track. Regarding the XR500, why would we want to leave this update off our most popular product? We are planning on releasing this update to every DumaOS router. We can't promise that it will be a simultaneous release, but any delay would only be caused by time constraints. We would not use a delayed release as a marketing ploy. Bear in mind that the XR500 is by far our most popular product so it's going to be a priority for us. Regarding lack of updates so far, I will say that the vast majority of routers only get bug fixes and security updates. We are bringing a massive update that will add many new features and will represent a huge leap forward for DumaOS, and it will be provided to all existing customers free of charge. How many routers have you had that received an update that overhauled the entire experience and made your router feel like a brand new product all over again? That's what 3.0 is doing to do. Anyway, i'm sorry that you won't support us any longer, but I hope that you'll take another look at us once 3.0 is released.
  39. 3 points
    ArcaPulse

    QOS issues (again)

    To be fair to them I left both the home hub and the R1 there and they both took no notice and didn't blame the hardware. For this one though I'll definitely remove everything so that there's no excuses
  40. 3 points
    Netduma Alex

    Sign up to DumaOS Insiders

    Everybody's welcome to join while applications are open!
  41. 3 points
    Bert

    Must Be Magic?!

    Not even throttling but there is instances where the lagger can gain the advantage simply due to in game mechanics. If I play at 150ms and you at 4ms. Assume the game has approx. 50ms interpolation lag for 60Hz servers. We are playing on Freqency. You run through the middle, I camp one of the hallways on either side of the map. As soon as I come out of cover and aim and shoot at you, this needs to be put in an update by my console, 0-16ms, send to the server, which takes 75ms, they need to process it in the master gamestate, which takes 0-16ms in theory (time between 1 update) then it gets send to your console, which takes 2ms. Then this gets processed by your client, 50-83ms interpolation lag (time between updates and frame rounding. in the best case it takes 127ms for me to be visible on your screen, worst case it will take 192ms. Average, 160ms. If I use a gun that kills in 300 ms I can have killed you before you finished raising your gun. Also in the above example, in CoD damage is dealt directly, so there is no interpolation delay, but there is a delay for it going in the update to the server, 0-16ms. So actually you would receive damage after just 0+75+0+2 = 77ms best case, or 16 (update rate)+75+16+2+32(frame rounding) = 141ms. So you can actually start recieving damage or be instakilled before I even appear on your screen fully. Also, my shots lag but register at the server after 75ms best or 107ms worst case scenario. What a lot of people forget that with high latency connections, that it gives the lagger a window to shoot at you without having flinch, because you can't shoot back yet. Where it hurts him is that hitmarkers will come at a delay. If situation above was reversed. You would come out of cover and this would be visible to me after 2+0+75+50 = 127ms best case or 16+2+16+75+83 = 192ms. Same numbers. But you fire and your shots hit at the server in 2ms best or 18ms worst case scenario. So I would already be dead at the server before I even see you moving. Now 2 players that both have 4ms to the server: Best case for coming out of cover: 0+2+0+2+50 = 54ms Worst case for coming out of cover 16+2+16+83 = 117ms Average, 85ms delay. You you see, it's not just your ping, but the other guy's ping plays a big role in the gunfight. And this is assuming clean connections which is usually not the case in a online environment. And a server that is not limited by CPU cycles etc etc. If you do the math for LAN with no latency then you will see that it's still not 100% fair. In reality. Most of the times latency is not symmetrical. And game updates are not recieved in exact 16ms intervals etc. Server can be at max capacity. It can go on forever. Low ping just means that you have the lowest possible path to the server. Less hops in between so the least chance of something going wrong. You have the advantage when coming out of cover and in straight up fights. But there is times where you are disadvantaged.
  42. 3 points
    It’s a netgear router that runs DumaOS as well, netgear update the router as it’s their hardware. It needs updates from netgear to patch security holes and to update drivers which netduma can’t do with DumaOS on this router as it’s not their hardware. Also it was a turn of phrase too, because there were things that needed fixing in the netgear side of it while netduma work on milestone 1.4
  43. 3 points
    Netduma Alex

    Connection logs

    I like these ideas a lot! We're aware of how useful these features would be... And i'll make sure the devs know that people really want this.
  44. 3 points
    Killhippie

    Dos attack

    Netgear routers label port scans and almost all traffic as DoS attacks it seems, they are very paranoid as far as logs, and its totally normal. This is the noise of the internet, as I said none are Dos Attacks, and the fact the firewall dropped the packets is good anyway. Port scans are done all the time and most of this is probably normal traffic the router does not like. Don't worry about it, its normal. If it was a Dos attack you would not be posting. My logs look the same, in fact every Netgear router I have ever had has logs like this.
  45. 3 points
    DJ*

    XR500 access and reset issues

    Resetting whilst disconnecting all Ethernet cables worked. Cheers Zippy 👊🏼
  46. 3 points
    Micbot

    DumaOS Developer Q&A

    What are some of the new features coming to the 1.4 milestone?
  47. 3 points
    Zippy

    Xr500 firmware updates

    Features! Its not features most of us here are looking for.. We are talking more in the present of current features and bugs that don't work and need fixing! We just want what we have now to work somewhat consistent and stable.. Its cool to look into the future but lets work on the present conditions first! You guys need to push on Netgear a bit also to fix things on there end too.. Lets not become the little guy here.. Flex some Duma muscle.. Don't roll over and play dead to Netgear.. Zippy.
  48. 3 points
    Sunaikinti

    Xr500 firmware updates

    We went the entire first quarter of the year without an update.
  49. 3 points
    cyberswine

    IPVanish VPN problem

    Sorry guys, wasn't monitoring the forum. Success on this one: client dev tun proto udp remote iad-a69.ipvanish.com 443 resolv-retry infinite nobind persist-key persist-tun persist-remote-ip <ca> -----BEGIN CERTIFICATE----- MIIErTCCA5WgAwIBAgIJAMYKzSS8uPKDMA0GCSqGSIb3DQEBDQUAMIGVMQswCQYD VQQGEwJVUzELMAkGA1UECBMCRkwxFDASBgNVBAcTC1dpbnRlciBQYXJrMREwDwYD VQQKEwhJUFZhbmlzaDEVMBMGA1UECxMMSVBWYW5pc2ggVlBOMRQwEgYDVQQDEwtJ UFZhbmlzaCBDQTEjMCEGCSqGSIb3DQEJARYUc3VwcG9ydEBpcHZhbmlzaC5jb20w HhcNMTIwMTExMTkzMjIwWhcNMjgxMTAyMTkzMjIwWjCBlTELMAkGA1UEBhMCVVMx CzAJBgNVBAgTAkZMMRQwEgYDVQQHEwtXaW50ZXIgUGFyazERMA8GA1UEChMISVBW YW5pc2gxFTATBgNVBAsTDElQVmFuaXNoIFZQTjEUMBIGA1UEAxMLSVBWYW5pc2gg Q0ExIzAhBgkqhkiG9w0BCQEWFHN1cHBvcnRAaXB2YW5pc2guY29tMIIBIjANBgkq hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt9DBWNr/IKOuY3TmDP5x7vYZR0DGxLbX U8TyAzBbjUtFFMbhxlHiXVQrZHmgzih94x7BgXM7tWpmMKYVb+gNaqMdWE680Qm3 nOwmhy/dulXDkEHAwD05i/iTx4ZaUdtV2vsKBxRg1vdC4AEiwD7bqV4HOi13xcG9 71aQ55Mj1KeCdA0aNvpat1LWx2jjWxsfI8s2Lv5Fkoi1HO1+vTnnaEsJZrBgAkLX pItqP29Lik3/OBIvkBIxlKrhiVPixE5qNiD+eSPirsmROvsyIonoJtuY4Dw5K6pc NlKyYiwo1IOFYU3YxffwFJk+bSW4WVBhsdf5dGxq/uOHmuz5gdwxCwIDAQABo4H9 MIH6MAwGA1UdEwQFMAMBAf8wHQYDVR0OBBYEFEv9FCWJHefBcIPX9p8RHCVOGe6u MIHKBgNVHSMEgcIwgb+AFEv9FCWJHefBcIPX9p8RHCVOGe6uoYGbpIGYMIGVMQsw CQYDVQQGEwJVUzELMAkGA1UECBMCRkwxFDASBgNVBAcTC1dpbnRlciBQYXJrMREw DwYDVQQKEwhJUFZhbmlzaDEVMBMGA1UECxMMSVBWYW5pc2ggVlBOMRQwEgYDVQQD EwtJUFZhbmlzaCBDQTEjMCEGCSqGSIb3DQEJARYUc3VwcG9ydEBpcHZhbmlzaC5j b22CCQDGCs0kvLjygzANBgkqhkiG9w0BAQ0FAAOCAQEAI2dkh/43ksV2fdYpVGhY aFZPVqCJoToCez0IvOmLeLGzow+EOSrY508oyjYeNP4VJEjApqo0NrMbKl8g/8bp LBcotOCF1c1HZ+y9v7648uumh01SMjsbBeHOuQcLb+7gX6c0pEmxWv8qj5JiW3/1 L1bktnjW5Yp5oFkFSMXjOnIoYKHyKLjN2jtwH6XowUNYpg4qVtKU0CXPdOznWcd9 /zSfa393HwJPeeVLbKYaFMC4IEbIUmKYtWyoJ9pJ58smU3pWsHZUg9Zc0LZZNjkN lBdQSLmUHAJ33Bd7pJS0JQeiWviC+4UTmzEWRKa7pDGnYRYNu2cUo0/voStphv8E VA== -----END CERTIFICATE----- </ca> verify-x509-name iad-a69.ipvanish.com name auth-user-pass comp-lzo no verb 3 auth SHA256 cipher AES-256-CBC keysize 256 tls-cipher TLS-DHE-RSA-WITH-AES-256-CBC-SHA:TLS-DHE-DSS-WITH-AES-256-CBC-SHA:TLS-RSA-WITH-AES-256-CBC-SHA
  50. 3 points
    Zippy

    Xr500 firmware updates

    I totally agree here... Ive seen slow firmware updates before on other brand routers as well but not like this... This approach we have now here with the XR500 is not the right approach at all. When there are issues that can be addressed then they should send out firmware patches once they have them.. Not wait months on end.. Another thing that bothers me is on the Netgear forum I see Netduma posting there to help those with issues.. But I never see Netgear folks post here on Netduma forum.. Theres a disconnect there.. Heres the problem with this current relationship we have here.. If we are on here posting with issues and need further assistance or help we now have to go over there and totally start from scratch with them with issues we are having.. This is extremely important when it comes to a issue where one might need to have there router exchanged for a new one.. Posting here on Netduma doesn't count even though it should.. We shouldn't have to cross post on two forums to resolve issues.. That alone is very problematic.. And by the time one does that there warranty is likely over.. I can easily see this happening.. Moving forward I can only say this.. Anyone new buying a XR500, XR700, and the XR300 id pay close attention to your return policy.. If you get close to your return policy date and are having issues just return the router for a refund.. That will be the safest course of action for yourself.. Don't wait for firmware patches because by that time one could easily run past there warranty timeframe.. And then your stuck!! Zippy.
×
×
  • Create New...