Jump to content

kssxs

Members
  • Content Count

    36
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Thanks
    kssxs got a reaction from Netduma Fraser in IPv6 - Current and future support level?   
    Thanks Fraser!
     
    Edit: As part of your testing, please make sure that IPv6 routes (pinging sites, v6 traffic, etc) still work after 90 minutes.  That was the main difficulty I have had so far, with routes going stale after the 90 minute RA limit.  Hearing that the rest of the feature-set is going to work is just awesome!
  2. Like
    kssxs reacted to Netduma Alex in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    IPV6 is coming! We’ve got it working on our development units
  3. Like
    kssxs reacted to Netduma Fraser in IPv6 - Current and future support level?   
    Yes it will, we've got it working on our dev units at the moment so will continue testing to ensure optimum compatibility.
  4. Like
    kssxs reacted to Netduma Fraser in ANNOUNCEMENT: The Future of DumaOS: Version 3.0   
    Of course there is pressure, all I'm saying is we are not going to put a deadline on it that we may have to extend - we've learnt our lesson, we've provided deadlines before and had to extend them again and again. This way is more practical for us and everyone else. We'll be doing a beta as soon as possible once we have ironed out some bugs that could impact general use, if we put out a beta we're not confident in and it bricks a load of routers then that would be a nightmare. We'll do what we have done before and what works, slow rollouts until we're sure its usable and stable. 
  5. Like
    kssxs reacted to Netduma Fraser in IPv6 - Current and future support level?   
    DumaOS will be available on all the routers so we'll be ensuring they work for all the routers so that includes the R1 as well. We wouldn't hold back something like that.
  6. Like
    kssxs got a reaction from Netduma Fraser in IPv6 - Current and future support level?   
    Sure thing Fraser!  My first piece of feedback is what I mentioned above (the routes going stale after 90 minutes; this has to do with subsequent IPv6 route advertisements after the initial advertisement and the current implementation not being able to receive the subsequent ones, from what I understand).  I'm sure there others with R1's that are also willing to help (for example, those in this thread).
     
    This isn't meant as a criticism at you guys, but I'm surprised you don't have any implementation at the office for IPv6.  Seeing as how the world is moving in that direction, maybe put some thought into implementing it, even if only on a small test network, so that we all, as users and customers, can get the benefits of you guys testing and implementing it directly?  I can definitely see advantages there when you guys build IPv6 support into DumaOS.  I'm still willing to provide specific feedback, but the troubleshooting/development cycle would go much faster if you're not waiting for user feedback when a change is made.
     
    Thanks for (hopefully) putting this into the next upgrade!
  7. Like
    kssxs got a reaction from Zippy in IPv6 - Current and future support level?   
    So...
     
    I'm resurrecting this since it was my original post.  I still have a need for this (amongst many, I'm sure), and would like to request a status update.  It's been a year and a half since my original post, and I would hope that, at least by now, there has been some progress in getting fully functional IPv6 support baked into an update.  From my last testing, IPv6 routes are dropped after 5400 seconds (90 minutes; routes go stale), requiring a reboot of the R1 to get them back.  This is, again, not doable, and a router in 2020 should have this functionality as part of its base layer.
     
    Have you guys done any work with regards to IPv6 for the R1?  Can I get a status update, please?
     
    Thank you
  8. Like
    kssxs got a reaction from Zippy in IPv6 - Current and future support level?   
    Hey guys,
     
    Any updates on this request?
     
    Through some recent testing, I've found out that the R1 eventually drops the IPv6 routes, and it causes all v6 functionality to stop throughout the network.  I know this is the case because if I connect my PC directly to the ISP modem/router, the routes, and functionality, continue to work just fine.  All of my devices behind the Netduma stop functioning on v6 after about 90 minutes, which is the time at which stale routes are dropped (5400 seconds).  On the PC that is directly connected, the routes are not dropped, and v6 is working as expected.
     
    Can I get an update, please?  As I stated above, I think all of the NAT issues that people experience will be resolved for those that are on v6 capable ISP's and networks, and so in my opinion, this should be of a higher priority rather than an afterthought.  Of course, I wouldn't want to sacrifice all of the fantastic feature-set that the R1 brings to the table, but I do think this is important enough to bring up again (not trying to give you guys a way to slip out adding this sooner, mind  ).  Hopefully you can figure out how to add the v6 support while maintaining the feature set, or at least, give us a toggle-able option to pick either v6 support, or v4-level functionality.
     
    Thank's again!
  9. Like
    kssxs got a reaction from ColonicBoom in Open Beta of DumaOS on the Netduma R1: General Discussion   
    That sounds like BufferBloat at work...
  10. Like
    kssxs got a reaction from Netduma Admin in Black Ops 4 - Getting P2P Only? Post Here!   
    Just reporting in to cover both sides of the fence. I'm one of the lucky few that didn't have issues with dedicated server games on the new OS.
    1) Which console are you using?
    Xbox One X
    2) Which game mode are you trying to play?
    HC TDM
    3) Which DumaOS powered router are you using?
    R1
    4) Where are you located (approximately)?
    Vancouver, Canada
    5) Describe any problems you're having.
    None, game works almost flawlessly. No issues getting dedicated servers when successful. It doesn't always work, but depends on how quickly I put it into 'Filtering' mode; either before or after I start multiplayer. If it doesn't connect to a lobby, I put the R1 into 'Spectating' mode, restart the game, start multiplayer, then put the R1 into 'Filtering' mode. Works every time.
    6) If you have the Netduma R1, please try setting Ping Assist to 50ms and make sure Filtering Mode is enabled. Then, reboot your game. Does this fix your problem?
    No issue to begin with .
    I haven't performed the 'Flush Cloud' update you guys recommended an hour ago, but again, I didn't have issues, sooooo....   I'll try it later tonight.
    Is it the idea that we're supposed to be able to leave 'Filtering' mode on permanently and not have to toggle it to get an open NAT and dedicated servers regardless of the setting?
    Thanks for your efforts guys!
  11. Like
    kssxs got a reaction from BIG__DOG in IPv6 - Current and future support level?   
    With all of the recent issues with BO4, and Moderate NAT (and of course previous and future games as well), IPv6 is an easy answer and seeing as how it's the future of the Internet, I think it's better to get on that train ASAP rather than waiting any longer.  We're far too behind on general implementation as it is.  A lot of ISP's and now most third-party routers support it as well by default.
     
    As for QoS and Bufferbloat.. I'm hoping Netduma engineers figure this out eventually.  For now, I've got a 300 Mbit up and down fiber setup, so I don't have congestion issues regardless.  My only issues are NAT related, and IPv6 solves those.
     
    Hence the wanting of those features sooner rather than later .
  12. Like
    kssxs got a reaction from JOE1305 in Open Beta of DumaOS on the Netduma R1: General Discussion   
    Unfortunately, I don't think I can do this test for you, unless I reconfigure another device as a router, which, at this point in time, isn't possible.  Hopefully the other guys here can assist with that test, although each case can end up being different.
     
    Based on what I'm seeing, I think it is an issue with the R1.  I'll have to do some further testing to confirm, but I believe there are 2 reasons for that:
     
    1) In-game voice chat doesn't seem to work when the in-game NAT is 'Moderate'.  Xbox Live party chat works fine, but then again, the console NAT is reported as 'Open' so that makes sense that there is no chat issues there.  Since the in-game NAT is different (different UPnP ports), it might be interfering with the in-game voice chat.  Could it be that the UPnP stack in the R1 is tying up the port that CoD wants to use, from a previous session?  Stabbing in the dark here...

    2)  To further my thinking that this is an R1 issue, and the strongest evidence so far, is that last night, after seeing an in-game 'Moderate' NAT, I rebooted the R1, rebooted my console, and afterwards both console and in-game NAT reported 'Open'.  I did not reboot my Internet modem, so I think that immediately eliminates that from what may be causing the issue.  With that evidence, I'm not sure your proposed test will be successful in eliminating the R1.  If other testers report that both console and in-game NAT remain open over multiple days and gaming sessions, then that firmly points to the R1 as the source of the problem.
     
    On the flip side, finding games doesn't seem to be an issue, mostly because the game is so popular right now that there doesn't seem to be any shortage of multiplayer games, so finding one even with a 'Moderate' NAT seems to be working just fine.  You wouldn't really notice this as an issue unless you knew there was only 1 MP game running, and you couldn't connect to it, or, with the sheer number of games running, finding a lobby took multiple minutes instead of less than 5 seconds the way it is right now.
     
    I'm sure some of my assumptions are way off, in which case, please correct me .  Just glad we can work together on trying to get this resolved
  13. Like
    kssxs reacted to Moofda in Getting disconnected from Black ops 4 servers (xbox) often   
    Thanks man, I went through and checked everything and noticed UPNP wasn't turned on, which I had on before I updated and that seems to have resolved the issue. I haven't had time to test much, but I didn't have any disconnects for a couple of hours or so last night, so that is promising.
  14. Like
    kssxs reacted to Netduma Jack in Open Beta of DumaOS on the Netduma R1: General Discussion   
    Awesome, great to hear you've got your open NAT
  15. Haha
    kssxs got a reaction from major masingil in Open Beta of DumaOS on the Netduma R1: General Discussion   
    Nope, at least not right now.  There hasn't been a second active console since the summer (while on the old firmware).
     
    I'll test again tonight.  I'll make sure to deactivate Xbox and game-related Port Forwarding, and ensure UPnP is enabled, ensure Geo Filter is off, reboot my Internet modem, reboot the R1 router, reboot my console, then check console NAT to ensure 'Open', launch game, check in-game NAT, report into here, enable Geo Filter and hope that I've seen and can maintain an 'Open' in-game NAT.  I'll get back to you guys tonight to confirm what the in-game NAT reported before I enable the Geo Filter.
     
    That should cover the test, unless you want to add any intermediary steps?
  16. Like
    kssxs got a reaction from Netduma Admin in Open Beta of DumaOS on the Netduma R1: General Discussion   
    Nope, at least not right now.  There hasn't been a second active console since the summer (while on the old firmware).
     
    I'll test again tonight.  I'll make sure to deactivate Xbox and game-related Port Forwarding, and ensure UPnP is enabled, ensure Geo Filter is off, reboot my Internet modem, reboot the R1 router, reboot my console, then check console NAT to ensure 'Open', launch game, check in-game NAT, report into here, enable Geo Filter and hope that I've seen and can maintain an 'Open' in-game NAT.  I'll get back to you guys tonight to confirm what the in-game NAT reported before I enable the Geo Filter.
     
    That should cover the test, unless you want to add any intermediary steps?
  17. Like
    kssxs got a reaction from Netduma Admin in New icons legend?   
    Understood, thanks guys!
  18. Thanks
    kssxs reacted to Netduma Fraser in Notify Beta testers of queue position   
    No, you will be fine. The download link is sent to the specific DumaOS form email that you signed up with. Forum email address does not affect this, the only thing with the forum email address being different is checking peoples place in the queue but we're not checking places now anyway so all good!
  19. Like
    kssxs got a reaction from Netduma Fraser in Notify Beta testers of queue position   
    Awesome, thanks for clearing that up... PHEW!  Thought I was going to miss out! 😛
  20. Like
    kssxs got a reaction from AzteQ in Notify Beta testers of queue position   
    I did as well... can we get an answer to this question?  I don't want to miss out on the update since my forum e-mail is different from my order e-mail that I used 2+ years ago...
  21. Like
    kssxs reacted to Netduma Luke in Announcement: DumaOS on Netduma R1 in Final Beta Testing   
    We have some good news to share: DumaOS for the Netduma R1 is now in the final stages of beta testing!  
    As many of you know, this has taken so much longer than we anticipated, but our developers have now resolved all the major issues. This means that DumaOS for the R1 is stable and crucially, backwards compatible, so you can go back to the original R1 firmware if you prefer. A big thank you to all the beta testers who worked tirelessly with us to get to this point. 
    We are tidying up some last loose ends to make it ready for full release. We will let you know it is ready to download across all our media platforms. Be sure to sign up to the DumaOS mailing list so you are the first to know when it's out.
    Stay tuned!

    The ND Team


  22. Like
    kssxs got a reaction from joaso in R1 DumaOS Briefly Delayed   
    Back in the olden days... we waited and we waited and WE LIKED IT.... dagnabbit.......
  23. Like
    kssxs got a reaction from PharmDawgg in R1 DumaOS Briefly Delayed   
    Back in the olden days... we waited and we waited and WE LIKED IT.... dagnabbit.......
  24. Like
    kssxs got a reaction from Sir_smooch in R1 DumaOS Briefly Delayed   
    Back in the olden days... we waited and we waited and WE LIKED IT.... dagnabbit.......
  25. Like
    kssxs got a reaction from major masingil in R1 DumaOS Briefly Delayed   
    Back in the olden days... we waited and we waited and WE LIKED IT.... dagnabbit.......
×
×
  • Create New...