EA_Vendcera
Long post, but I've been troubleshooting this for the past 48 hours. Full disclosure I did use ChatGPT pro to help me keep track of what I had done. I utilized Microsoft Event Viewer, Windows Logs, and Hardware Monitoring software. I genuinely spent 48 hours working on this, please take the time to read through. I did include a part at the bottom for players; a TL;DR.
THIS IS NO LONGER WORKING. IT WORKED FOR 2 MATCHES AND CRASHES UPON CONNECTION TO ANOTHER MATCH. IT NO LONGER ALLOWS ME TO CONNECT TO A MATCH. EA FIX YOUR JAVELIN ANTICHEAT CLIENT
Root Cause Analysis – Battlefield 6 Network Disconnect During Gauntlet / RedSec Match Entry
Status: Issue reproduced across multiple devices and networks. Workaround identified (disable IPv6 on game client). Underlying defect still present.
Problem Description:
On multiple Windows 11 PCs in the same household, Battlefield 6 consistently caused a full network disconnect specifically when entering Gauntlet / RedSec (during helicopter insertion). Menus and normal multiplayer modes worked normally, but during Gauntlet load the PC would lose connectivity, Windows would report Connected – No Internet, DHCP lease renewal failed, DNS lookups failed, and the network only recovered after disabling and re-enabling the adapter or rebooting. Physical link never dropped.
This occurred on Ethernet and Wi-Fi, across two different Comcast gateways (XB8 and XB10), and on two separate PCs. No other applications or games were affected.
Troubleshooting Performed:
Clean Windows 11 reinstall performed. Latest chipset, NIC, and GPU drivers installed. Issue reproduced on a clean OS with no third-party utilities, overlays, tuning tools, or background services installed.
NIC settings tested at default and with conservative configurations. Same result.
Tested Ethernet and Wi-Fi independently. Same behavior.
Tested across two XB-series gateways. Same behavior.
Tested on mobile hotspot and Xfinity public Wi-Fi. Same behavior.
Tested on second PC in same environment. Same behavior.
This ruled out hardware faults, NIC firmware, router or gateway firmware, ISP routing, local DNS configuration, or operating system configuration.
Event Viewer Observations:
At the instant Gauntlet match entry begins, the following sequence consistently occurs:
DNS Client Event 1014 (name resolution timeout)
DHCP Client Event 1003 with error 0x79 (lease renewal failure)
Network transitions to No Network Access
EA Anti-Cheat / Javelin filter unload recorded
These appear to be downstream effects of a networking stack failure rather than primary causes. The adapter link remains up, but the routing layer collapses.
Network Path Findings:
Per EA request, traceroute, ipconfig, and route print output were captured on both home network and alternate network connections. Battlefield 6 traffic consistently routed to EA infrastructure in London / EU via Telia / twelve99 backbone and AWS / Akamai edge nodes. Routing paths were clean and stable. No packet loss or congestion signatures were present. The disconnect only occurred during protected Gauntlet session transition when anti-cheat filters attach.
Breakthrough Finding:
Disabling IPv6 on the game client network adapter immediately resolved the issue.
Adapter properties opened, Internet Protocol Version 6 unchecked, system rebooted.
After disabling IPv6:
Gauntlet and RedSec load normally
No DHCP failures
No DNS timeout events
No network disconnect
No anti-cheat filter unload events
Multiple matches played successfully
Same behavior confirmed on two separate PCs.
Conclusion – Likely Root Cause:
Issue appears to be caused by an IPv6-specific Battlefield 6 / Javelin Anti-Cheat Windows Filtering Platform (WFP) filter failure during Gauntlet / RedSec protected session hand-off.
During Gauntlet entry, BF6 prefers IPv6 transport. Javelin attaches IPv6 WFP security filters. Under certain routing or region assignment conditions, the IPv6 filter path triggers a networking stack failure, resulting in DHCP renewal failure, DNS resolution errors, and complete loss of gateway routing until adapter reset.
Disabling IPv6 forces IPv4 transport, which fully avoids the faulty path and restores stability.
Factors Confirmed Not Related:
Not caused by hardware, router firmware, Comcast routing, IPv6 at the network level, DNS provider, Windows configuration, driver versions, or local security software.
Issue is isolated to:
Battlefield 6
Multiplayer / Gauntlet / RedSec mode
IPv6 transport path
EA Anti-Cheat / Javelin filter behavior
Current Workaround:
Disable IPv6 only on affected PC network adapter. Do not disable IPv6 across entire network infrastructure.
Recommendation for EA Engineering Teams:
Areas suggested for investigation:
IPv6 WFP filter handling in Javelin Anti-Cheat
IPv6 session protection during Gauntlet transition
IPv6 to IPv4 fallback logic
Blaze IPv6 routing and region assignment interaction
Behavior across AWS / Akamai EU points of presence
Available diagnostic artifacts:
Traceroute logs across two network environments
Crash-time Windows networking logs
NIC driver and OS build data
Cross-system and cross-network reproduction notes
Willing to provide directly to engineering if needed.
