Jump to content

kssxs

Members
  • Content Count

    43
  • Joined

  • Days Won

    1

kssxs last won the day on May 16 2018

kssxs had the most liked content!

About kssxs

  • Rank
    Apprentice

Basic Info

  • DumaOS Routers Owned
    Netduma R1
  1. Hey Fraser, A while back, I was probably the main person complaining about the lack of IPv6 support, and remember reading that the beta would have that built-up as an important feature, and should apply to get in to primarily test the IPv6 feature-set. I know, based on what I read, that there wasn't a lot of people looking for that as an important update for that. I submitted to get in, but wasn't selected, unfortunately. Since IPv6 is so important for the future of the Internet, is there any chance I can pull your leg to get in, just to test out the IPv6 support? Pretty please?
  2. That might be more an issue of having IPv6 enabled on the router itself, not a problem with IPv6. We saw the recommendation from Netduma to disable IPv6 in a bunch of cases with issues on the R1, so that's what that might be. Most likely your game is NOT using IPv6 for data exchange, and if you turned it off in your router, not only will it fix your lag issue but it also won't stop your game from working.
  3. 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!
  4. I just re-read your response, and I wanted to get a clarification... My original post was regarding usage of the gaming feature-set with IPv6. Will the standard feature-set of the current firmware work for the IPv6 implementation on the R1? Specifically, will stuff like the Geo-Filter, and QoS, and all/most other features be supported for use with IPv6? Thanks again!
  5. Hey Fraser, Just wanted to reiterate, in case you didn't take note from my IPv6 thread that I would definitely be in to test for the IPv6 QoS, etc, on my R1. Thanks!
  6. Fraser, as a side-note to the testing, does this mean that you guys will also develop the standard R1 features for use with IPv6? While just basic support is better than nothing, I also don't want to lose the gaming features that make this router stand apart from all of the others out there...
  7. 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!
  8. It should have had more IPv6 support from day 1, considering that we've known the IPv4 address space was running out long ago. Having said that, I get that IPv6 is only now growing fast, so the R1 was built with supporting the most common protocol of the day. I can also understand if Netduma comes back and says that the R1 can't properly support IPv6 due to it's aging hardware, and we'll have to buy a newer model to get full support. My main issue is that we have no news in that regard, and I would love to hear the official word either way. That way, I (and the rest that are interested in a full IPv6 network) can plan to either keep the R1 in place, or move to a different piece of router gear that has full protocol support.
  9. I just saw this post, as I haven't been on the forum in quite a while. I've also asked for an update with regards to the issue of missing IPv6 support, here: https://forum.netduma.com/topic/27284-ipv6-current-and-future-support-level/ Other Duma users, please add your voice to that request if possible! Ultimately, I'd like to request that, if it's not already being considered or being worked on as part of this particular update, to have fully functional IPv6 support as part of this major 3.0 update. Please and thanks!
  10. 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
  11. Thanks for the info, Fraser. Would it be possible to at least get the route being dropped issue fixed in the interim? As it stands, if I want constant basic v6 functioniality in my network, I can't use the R1, as it drops the routes after 90 minutes, requiring a reboot to get them back (that's not doable). I really don't want to use my ISP's modem/router... Please and thanks for any more info you can provide! PS: Also, would it be possible to see this 'Ideas Sub-Forum' as Netduma Admin mentioned?
  12. 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!
  13. Wait until the cloud update in the next couple of days, and let's see what happens.
  14. 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 m´╗┐ode 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!
×
×
  • Create New...