mygamertagsucks

Thanks, @Netduma Fraser. I will give this a go come daylight. It seems like, the last couple of nights, despite only "playing" one match (was online "playing", but as a performance check) Saturday, and Sunday morning. I will say that something has definitely changed with how I am connecting, personally, so I am hoping this is a good sign. In the past, people who seemed to have issues like I'm describing, also complained about being placed in match mid-game, on the losing end of a blowout, and naturally, always on the losing team. Since AW, that is one thing that has not been a frequent issue for me. Since dealing with this issue, every single game had been an "in-progress" match, despite the fact I wouldn't leave the match early since A. It's a game, and B. The stats do not apply to your profile. However, the last two nights, I was back to the "waiting on more players", but it was under 10 seconds. My in-game ping, was showing 16ms. Which, is great, but it's not true. I've come to realize that when they (Activision) say "searching for ² under 16ms ping..." Then searching for match under 34ms ping...." It is their way of saying "searching for a match with attributes A", which are usually ideal, but if it's 16ms in game, it's always been just over 30ms for the PS5 when looking at the DumaOS auto-ping host, when using the geo-filter. Oh, the other weird thing is that despite rubber banding, ghost-bullets, death bullets, seeing other players doing the running man dance, where they stand still, even though their feet are moving; I have not received one single network icon while playing BO7's multiplayer. Yet, in my "killcams" (I know, they're a generality as to what happened, using 70(ish)% of data that the server has leading up to your death, and then kind of "stitches the rest together" based on most likely case scenarios. I hate people b**ng about killcams who think they are instant replays. End tangent), I do see where they are receiving red indicators that the network, on their end, is suffering from extreme packet loss AND packet burst, while also showing the latency symbol above packet loss. It only seems to happen against certain players who are absolutely dominating the lobby, to the tune of 53-2, with a sniper rifle. Makes me suspicious of how legitimate their gameplay is, and I know that players have found a way to cheat on console via remote-play, and a computer, and a capture card, I just don't know: Why? For the last couple of days, I have run the game with no regard to fine tuning connection, and while it is working better, better is still is a far cry from where I was before this mess started. I can not believe that I forgot to set the NAT to open in the router somehow. Just goes to show how preoccupied I had become with other parts of our overall Internet connection. And hell, I may realize that, while sleep deprived, I jumped into the settings and somehow messed something up. But, I'll let you know how it goes once the NAT is once again set to open, even though I'm getting open NATs literally Everytime I connect. Thanks for all the help so far. I know this has to have been a huge headache for you all to be so kind to me. I feel like the old dog trying to learn new tricks.

@Netduma FraserSorry, forgot to post the WAN

@Netduma Fraserhere are the pics, arriving late to the party as usual. Not sure which order these will end up posting. But, there will be the LAN pic showing the subnet mask, even tho it is showing the router as my local IP address.The Internet Setup Picture shows that the subnet mask is 255.255.248.0

I'm a dumbass. Sorry. I think amidst all of this, I saw the W, and assumed it was the screenshot I took of the wireless setup. I'm sorry for that. Let me grab the pictures again real quick, and make sure I upload the correct ones this time. I have, admittedly, grown so frustrated with this that I literally cannot see straight when I'm looking at small thumbnails on my phone. Back in one second, hopefully. Also, thank you for a better explanation as to how the congestion control works. I knew that giving my PS5 all of that bandwidth was a dumb idea, and did it anyhow. Sucks when I'm trying to learn things on the fly, bc the stuff that was relevant when I took networking does not seem to apply to anything that I'm doing now. But hey, at least I have all these fun cable stripping tools, and crimpers and old dialup modems laying around. One last thing before I post the correct pictures; I was going through every little setting on the DumaOS interface, and clicking on every single question mark that explained what everything is, and how it works, etc. I noticed that when I checked in on AdBlocker, it was enabled, so my AdBlocker should have been working. Yet, I noticed that my phone, and my mother's phone, were letting some queries through, which I understand. But, my phone was getting multiple tracking and "ads" bubbles. When I clicked on the list of what was being tracked or advertised, it was a running list, in real time, from "googletagmanager", "googleadmanager", and one other Google thing. So, I took my phone offline, rebooted the router (habit), plugged my PlayStation in and played one match. I don't know if this is a placebo effect, or if taking my phone offline really made that much of a difference, but my connection was steady, but bullet reg, and the sync seemed off with the server. I would shoot one bullet into someone, in core gamemodes, and it would kill them, but show that I landed 4 or 5 shots. For the record, crossplay was set to "on/console only". Could this really have made the difference it felt like it did?

The subnet mask has always been 255.255.255.0, which is what the LAN setup shows, but the wireless, which I let the setup wizard handle (actually, the setup wizard did everything is 255.255.248.0. My speeds in LAN port 1 are terrible, when tested on PS5. When I test it on port 2, I get great results (will post picture). Port 3 seems to be broken, as it doesn't register anything at all, and port 4 seems to be very inconsistent. Ran the PS5 speed test with and without the game going, which, I forgot would log me out of the game, but I was going to hop out of that silly mess anyhow. One question regarding congestion control (and I'm going to fine tune it, starting at 70 and working my way around if the MFer ever decides to connect, without me skipping, teleporting, and rubberbanding all to hell), let's say I assign my PlayStation 90% of the download bandwidth, and 90% of the upload bandwidth, and turn congestion control on, set at 70 down and up. Will my PS5 be limited by that 70%? The guide just says something along the lines of limiting how much a bandwidth hogging device can use, but my overthinking (poorly) ass over here is wondering if I'm limiting myself. I'll just turn the Playstation on and upload the results. I thought my PS app had the screenshots on it. Shocker- it doesnt.

Those pics are how I try to basically convert the wifi into a dedicated gaming line. Probably not the best technique. Edit to add: my wired connection from the router to PS5 is what is being affected only in game.

I had disabled the cloud prioritization bc my Mom was playing something on her phone and for some reason, it seemed to be getting prioritized. I manually add my PS5 and should have a pic on here, as well as how the congestion control was set up.

@Netduma FraserI'll be honest, I'm starting to second guess my router at this point. Of course, this is the first time I haven't gone in and manually assigned a static IP to my PS5, and port forwarded the required ports for Call of Duty Black Ops 7. I didn't think I still needed to. I did notice my nat type shows up with a checked box to make it strict, so I have to uncheck that. When I ran the congestion control setup, dl stayed at 100% and upload only went down to 93 or 98%. I don't know if I have the geo-filter pics or not up there, but I didn't even mess with the geo-filter after seeing my unstable connection, I would shoot one minute and be across the map the next. AdmiMy modem is getting a good signal now. I replaced the cat5e cables with cat7 patch cables. It's down to the following, at least as far as I can tell. 1. Bad LAN port on my PS5, despite network tests showing 515.2 down, 36.5 up. (Later, unexpectedly dropped 06.20mbps up. 2. My router is either broken, or setup improperly. A month now, and at least we have Wi-Fi. Subnet mask for LAN is correct but not wireless setup, even though the primary and secondary DNS servers are showing up correctly. Like I said. huge pain in the arse at this point. I only tried for 15 min before I got too pissed off and admitted defeat for the night.

@Netduma FraserOn second hand, I can do this beforehand and will do this in one second.

Get ready for a deluge of pictures

@Netduma FraserOn second hand, I can do this beforehand and will do this in one second.

@Netduma FraserOn second hand, I can do this beforehand and will do this in one second.

8jh @Netduma FraserI can absolutely do that, but it will be after 4pm my time (Eastern Daylight Time) because we have an in-store meeting tomorrow at our local Xfinity office because we have dealt with this for three weeks. I have called them 5 times, each time getting reassured that they would send someone to check our node. Finally, after three weeks, I got a call saying a technician has found and repaired an issue on their end and to press 1 to confirm the fix worked , 2 to keep our appointment. We chose #2. I did run pingplotter straight from the modem, and I'll post those when I get inside. But. I have no problems going thru and showing you my step by step approach. Hell, I kind of welcomed someone asking me to do this.

I do not see any servers that are blocked. Prior to the intermittent outages becoming full-time, I never experienced any of this type of odd in game behavior. Since switching modems, however, all but one device are showing up with an IPv6 address. Previously, it wasn't uncommon for my phone to show up twice, under the device manager section.

So, it is currently Sunday, March 22, 2026. My current time is 01:44am. On my router, it shows as being Saturday, March 21, 2026 w/ a time of 21:40:08. The closest I can get, using the default netduma NTP server is Sat, Mar 21, 2026 at 21:04:40. What in the hell am I continuing to do incorrectly?