Call Of Duty Battlenet Issue again

[18RayF]

Hi I’m still getting the issue of being disconnected from Battlenet when trying to launch Call of duty despite turning off BI still doesn’t work .

I have done the following for troubleshooting and used AI to just summarise what happened .

I’m escalating an intermittent connectivity issue that appears to be related to NAT/session handling on the Netduma R3. I’ve done extensive isolation and packet-level troubleshooting and would appreciate engineering review rather than standard support steps.

 

Topology

• FTTP connection (ONT → Netduma R3 → PC)
• The R3 is the only NAT device in the path (no modem, no double NAT)

Issue

• Call of Duty / Warzone intermittently fails at “Fetching Online Profile”
• Error states include “not signed in” or “disconnected”
• Battle.net launcher login is stable and always succeeds
• When the failure occurs, restarting the game or Battle.net does not reliably resolve it
• On rare occasions the profile fetch succeeds, but success is non-deterministic

Key observations

• The issue works 100% of the time when using a mobile hotspot on the same PC (same account, same install)
• This definitively rules out account, PC, OS, or game installation issues
• The problem has existed intermittently for ~1 year and has gradually worsened over time
• Historically, restarting Battle.net helped; now it often does not

 

Troubleshooting already performed

• Removed endpoint DSCP marking (previously CS6); confirmed via Wireshark
• Disabled Geo-Filter entirely
• Set QoS from “Always On” to “Auto”
• Disabled IPv6 on both router and PC
• Verified clean TCP/TLS behaviour post-QoS changes via packet capture
• Issue persists intermittently despite all of the above
•  

Behavioural pattern

• Hotspot: profile fetch succeeds every time
• Home network (R3): profile fetch intermittently fails
• Cold power-off of the R3 sometimes improves success temporarily

 

Conclusion

Based on the above, this strongly points to a stateful NAT / session reuse / backend affinity incompatibility between the R3 firmware and Activision’s backend services. The intermittent nature, gradual degradation over time, and complete success on hotspot are consistent with NAT state reuse or UDP session handling rather than packet loss, DNS, or application-level faults.

 

I’m happy to provide:

• Wireshark PCAPs (before/after QoS changes)
• Reproduction steps
• Additional logs if required

Please let me know if this can be escalated to an engineer for review, as this does not appear to be resolvable via standard configuration changes.

[Netduma Fraser]

It's better to get a summary from you of what happened for example - you did this how? "Removed endpoint DSCP marking"

Disable SmartBOOST fully from the menu, does it work then?

[18RayF]

No so initially I tried to login to battlenet this never worked made me go offline whenever I tried restarting it would make me sign back in . I flushed dns etc.   restarted pc and still nothing worked . Then I started a wireshark capture while trying to launch and saw many retransmissions and out of order packets . PC showed it had a DSCP marking of 42 this is for routing protocol etc so I disabled this as I set a  QOS policy on my pc .  Then battlenet allowed me to logon but when launching the game it still fails to launch the profile . I also have scan and repaired game files reinstalled the game , Sfc /scannow ,  etc.  

[Netduma Fraser]

I think setting QoS policies on the PC is more likely to confuse matters, I would revert that so we can know it's not affecting it whatsoever. Then what error specifically are you getting when going onto Battle.net/the game with Geo-Filter & SmartBOOST fully disabled?

[18RayF]

when the game launches in the top left of it successfully fetches my profile it will work but majority of time it shows not signed into profile and then I get this error above

[Netduma Fraser]

Thank you, have you tried the following, if not please do so:

1. Clear cache for Battle.net: https://www.youtube.com/watch?v=9Qx6kSeH2Jg
2. Uninstall then reinstall Battle.net
3. You're using WiFi on the PC to the R3 right - have you split the WiFi bands, if so which are you connecting to 2.4GHz or 5GHz? If you haven't, split them then try each band to see if there is a difference.
4. Are you able to test via ethernet to the router?

[18RayF]

Yes I’ve done that also and I’m connected via Ethernet .

[Netduma Fraser]

So if you connect via WiFi instead to the router rather than the hotspot does it work?

[18RayF]

Nope 

[Netduma Fraser]

Make the issue happen and then grab the logs please. Also if you connect via ethernet to the ONT do you get the same issue?

[18RayF]

I’ve got logs already if you would like me to attach 

[Netduma Fraser]

If they're directly after the issue happens and before a reboot then yes. Do you get the same issue with the PC connected directly to the ONT?

[18RayF]

Cant connect direct to ONT as PC is in different room and no cable long enough unfortunately ,  i realised there was a MTU mismatch from PC and Router could it cause this as i changed router to 1492 as PC already had that and its working fine now ?

These logs were yesterday after it happened and today after I changed the MTU on Router while attempting to load up also .

 

 

 

R3_2026-01-27T18_49_20.363Z_logs.txt R3_2026-01-26T22_39_49.174Z_logs.txt

[Netduma Fraser]

Yes a MTU mismatch could cause it, glad to hear you found the cause

[KinGzzy]

15 hours ago, 18RayF said:

Cant connect direct to ONT as PC is in different room and no cable long enough unfortunately ,  i realised there was a MTU mismatch from PC and Router could it cause this as i changed router to 1492 as PC already had that and its working fine now ?

These logs were yesterday after it happened and today after I changed the MTU on Router while attempting to load up also .

 

 

 

R3_2026-01-27T18_49_20.363Z_logs.txt 99.9 kB · 2 downloads R3_2026-01-26T22_39_49.174Z_logs.txt 99.64 kB · 1 download

Hi
According to the logs, your router is suffering from major software instability.

1. IPv6 configuration problem (odhcp6c)
2. Script and TLS errors (cli.lua)
3. Time instability (Time went backwards)
4. Very frequent DHCP renewal (udhcpc: lease obtained, lease time 600)
5. Memory cleanup (drop_caches) USER root cmd echo 3 > /proc/sys/vm/drop_caches
6. Processor instability (Time went backwards)
7. The conflict with "DPI" (Deep Packet Inspection)
In your logs, I also see: user.info dpiclass-daemon: Daemon shutdown user.warn overwatch: Changing category of appid=161... to VPN

Your router is suffering from major software instability. This isn't just a minor connection error; it's the DumaOS system crashing because it's trying to handle too many things at once.

[18RayF]

Hi

Thanks for that Is there anything I can do to fix this ? Adjust DHCP lease time etc or just wait till new update ?

[KinGzzy]

19 minutes ago, 18RayF said:

Hi

Thanks for that Is there anything I can do to fix this ? Adjust DHCP lease time etc or just wait till new update ?

No, you can't do anything; you have to wait for him to pass the information on to a Firmware (Embedded) Developer.

[DARKNESS]

@18RayFYour case is uncommon but not unheard of. What stands out is that you're using DHCP, which typically operates with an MTU of 1500. However, your ISP is clearly providing an MTU of 1492, commonly seen with PPPoE, and when the MTU exceeds the limit set by the router, fragmentation occurs, which can lead to issues like the one you experienced. In other cases, this might manifest more noticeably, such as through packet loss. It is not an issue on the router side as the router uses the most common configuration. 

@KinGzzyMost of what you said isn’t even an issue; the time going backwards is literally just the DPI reading the packets, and as you are using the AI, which you are, it doesn’t tell you the most obvious thing, which is that IPv6 is disabled.

[KinGzzy]

51 minutes ago, DARKNESS said:

@18RayFYour case is uncommon but not unheard of. What stands out is that you're using DHCP, which typically operates with an MTU of 1500. However, your ISP is clearly providing an MTU of 1492, commonly seen with PPPoE, and when the MTU exceeds the limit set by the router, fragmentation occurs, which can lead to issues like the one you experienced. In other cases, this might manifest more noticeably, such as through packet loss. It is not an issue on the router side as the router uses the most common configuration. 

@KinGzzyMost of what you said isn’t even an issue; the time going backwards is literally just the DPI reading the packets, and as you are using the AI, which you are, it doesn’t tell you the most obvious thing, which is that IPv6 is disabled.

Okay, so for you, "problem" rhymes with "breakdowns" in the IT world, which you clearly don't know much about, especially here, since it's supposed to be a gaming router, so latency and other factors should be optimized as much as possible. Well, in these logs, that's not the case. The router, especially the processor, is working unnecessarily and haphazardly, which affects the stability of the system and therefore the router... Basically, just because your car starts and runs doesn't mean it doesn't have a problem... But since it's you, I can understand.

[KinGzzy]

Anyway
just this error in its log:
`cli.lua: goto outils hook failed`

PS:
I didn't read it properly, and yes, I use AI to help me with my tasks to save time, both professionally and personally, like many admins and sysadmins.
But as you know better than anyone, if you don't understand it, unfortunately, AI isn't very useful, especially in the world of IT.
If you still have doubts, I can send you a screenshot of my qualifications.