Jump to content

kssxs

Members
  • Content count

    23
  • Joined

  • Last visited

  • Days Won

    1
  1. kssxs

    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!
  2. 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 .
  3. My ISP supports IPv6, and I would like to start using it in my network. The benefits of a no-NAT configuration are, I believe, self-explanatory. Just a quick few questions with regards to IPv6 support on the R1: 1) What is its current state with regards to usage? Can I enable it and expect to use v6 on my network successfully in a dual-stack configuration the same as a lot of other third-party routers out there? 2) The current implementation on the R1 seems to be very basic. We can't see any v6 addresses that are assigned (DHCP or otherwise) to the R1, and can't see nor modify any relevant info on its status or LAN details. Is this going to be improved over time and is there a timeline for it? I realize you're busy with bug fixes and newer betas, etc, but this IS 2018 and the R1 needs to be future-proof to some degree, so this is a big area for improvement. 3) If nothing else right now, can we at least get support for console IPv6 support so that we can benefit from the no-NAT nature of v6 for our Xboxes? Thanks for reading!
  4. kssxs

    Hope this Helps

    Get an 8-port dumb switch and put everyone on that behind the R1, otherwise the R1 is pointless. Here's what it should look like: Modem ---> R1 ---> 8-port dumb switch ---> Everyone's connection (and a separate WiFi access point) The way you have it right now, the only one the R1 affects is you, and since you're the only one on it, anyone affecting your connection in your household is outside of your R1's ability to control their impact on your gaming. That's just.... wrong... lol . If you're concerned about your R1's WiFi performance, add a separate new WiFi access point behind the switch as well.
  5. 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
  6. Without restarting anything, NAT is 'Moderate' again. It was 'Open' last night during my gaming session. Shut down the Xbox then, and turned off the Geo Filter. Tonight, I started up the Xbox and the game, and checked the in-game NAT status and found it 'Moderate'. Did not enable Geo Filter until I checked the NAT status. I also realized I had QOS disabled on the Netduma, but that just wasn't a factor as my tests were done with it disabled. Something's not right here. This should not be an issue.
  7. So Jack, is it possible that you guys will be able to correct this behaviour? It would be nice to not have to turn off the Geo Filter manually every night to get an open NAT the next gaming session. I'd love to be able to leave this on, and in fact, not have to do anything with the Netduma at all.
  8. So far so good! I've got an 'Open' NAT on both the console and in-game in BO4. Geo Filter is disabled (still), so don't know what it'll be after I enable it. I'll restart my game after and report again. Afterwards: Enabled Geo Filter, re-started the game (did NOT restart the console at this point) and the NAT is still 'Open'. Now I guess the true test will be disabling the Geo FIlter (like I do every night), a restart of the console, restart the game, and check to see if NAT in-game is still 'Open', report back here, re-enable the Geo Filter, and wreck some n00bs! BRB... Afterwards again: I disabled the Geo Filter, restarted the console, found console NAT to be 'Open', restarted the game, and found in-game NAT to be 'Open'. Success! Now, hopefully, it stays that way without having to restart my Internet modem, router and console. I'll report back in the next few days if it reverts to 'Moderate' NAT without me restarting anything. Thanks for reading so far down .
  9. Just as a suggestion, try changing the network cable between your Xbox and the Netduma. Sometimes connection drops are the result of a cable that's gone faulty over time. Good luck!
  10. 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?
  11. I end my gaming sessions by shutting down my Xbox, and then turning off the Geo Filter. Doing this ensures my console NAT always reports as 'Open' when I turn it back on next time. However regardless of if the console NAT is 'Open', UPNP is enabled or not, or manually using Port Forwarding instead, no matter which setting, or combination of settings, the game will always report 'Moderate', even before I turn on the Geo Filter. I think since I've upgraded to DumoOS, I've only had one BO4 session show as 'Open'. Are you guys actively adding NAT servers for Xbox Live? It would be nice to not have to manually shut off the Geo Filter every time I turn my console off. By 'turning off the Geo Filter' I mean that I put my console into 'Spectating' mode. I don't delete the device or anything like that. Hopefully the additional info helps you guys out with getting to the bottom of this. Thanks for your efforts!
  12. I would classify that as a bug. Jack, is this something being looked at; can anything be done to correct this behaviour or does anything even need to be done? It especially doesn't make sense considering that before a reboot, it shows 'Moderate', yet afterwards it's 'Open'. I can accept your statement that most likely the NAT is open, but the game is reporting 'Moderate' (mine does the same thing), yet I have no issues getting into games at all, and no issues communicating via voice for in-game chat or Xbox Live party, however my OCD won't let this go either . For the record, this is my first complaint with regards to this DumaOS/BO4 combination, lol.
  13. Understood, thanks guys!
  14. Hey guys, I noticed there doesn't seem to be a legend for the icons used in the Geo-Filter map. Can we get an explanation of what the icons are, please, as compared to the old ones? Thank you!
  15. Awesome, thanks for clearing that up... PHEW! Thought I was going to miss out! 😛
×