Netduma R3 – Battlefield 6 Intermittently Detected as “Unknown Gaming” Instead of “EA

[GrandFathrs]

System Configuration

• Router: Netduma R3

• Firmware: DumaOS 4.0.540

• Game: Battlefield 6

• Platform: PC (Steam)

• Device Classification: PlayStation (configured for Geo-Filter compatibility)

• Internet Connection: T-Mobile Fiber, 2 Gbps

• Network Configuration: Netduma R3 primary router, Eero Pro 7 in bridge mode

• Geo-Filter: Enabled

• Strict Mode: Enabled

• Typical Battlefield Server Ping: 25–32 ms

Issue Description

I'm experiencing an intermittent application-detection issue with Battlefield 6.

Under normal conditions, the Netduma R3 correctly identifies the game as EA in Steady Ping. However, at seemingly unpredictable times, the application classification changes to Unknown Gaming.

The game remains connected, and Steady Ping continues to indicate that traffic is being stabilized.

Importantly, when the classification changes:

• The Geo-Filter map continues displaying the same server.

• The server location does not appear to change.

• The reported server ping remains approximately the same.

• The Geo-Filter and other visible router functionality appear unchanged.

• The primary observable difference is that the application classification switches from EA to Unknown Gaming.

The classification sometimes returns to EA after restarting the router or restarting the game, but the issue eventually recurs.

Observed Gameplay Impact

Although the router continues to report that the connection is stabilized, gameplay subjectively feels different when the game is identified as Unknown Gaming.

The most noticeable differences involve aiming and hit registration:

• Aiming feels less consistent.

• Tracking targets and making small aiming corrections feels more difficult.

• Aim assist appears to behave differently between sessions.

• Overall responsiveness feels less predictable.

These observations are subjective, and I have not established that application classification directly causes them.

However, the repeated association between the application label and perceived gameplay consistency makes me concerned that Steady Ping may be treating the traffic differently depending on how the game is identified.

Troubleshooting Already Performed

I have experimented with several configurations, including:

1. Restarting the game and router to restore EA detection.

2. Configuring the PC as PlayStation for Geo-Filter compatibility.

3. Enabling Strict Mode.

4. Adjusting congestion-control bandwidth limits.

5. Monitoring ping stability and latency spikes independently.

6. Comparing gameplay behavior when Steady Ping reports EA versus Unknown Gaming.

Restarting sometimes restores the EA classification, but this has not provided a permanent solution.

Questions for Netduma Engineering / Support

1. Does Steady Ping operate identically when Battlefield 6 is detected as EA versus Unknown Gaming?

Is the same stabilization algorithm applied to both classifications, or does EA identification enable any game-specific processing, traffic recognition, or prioritization?

2. Can a classification change occur without the actual game traffic or server changing?

Since the same server remains visible in Geo-Filter, could this simply be an application-signature recognition issue rather than a network-routing or game-session change?

3. Is there a way to manually assign Battlefield 6 traffic to EA?

Can the game/application classification be forced or manually defined using Traffic Prioritization, device settings, Geo-Filter, or another DumaOS feature?

4. Can the application-detection database be refreshed independently of firmware updates?

If this is a classification-signature issue, is it something that can be corrected through a cloud update?

5. Are there router logs or diagnostics that could confirm whether Steady Ping behavior changes when the application classification switches?

I'd like to compare a correctly identified EA session with an Unknown Gaming session and determine whether there's any measurable difference in the actual stabilization behavior.

6. Is Battlefield 6 on Steam fully supported by the current application-detection signatures in DumaOS 4.0.540?

If so, is intermittent classification as Unknown Gaming a known issue?

Desired Resolution

Ideally, I would like the router to consistently recognize Battlefield 6 as EA.

More importantly, I'd like to establish whether the classification change is purely cosmetic or whether it can affect Steady Ping, Traffic Prioritization, or any aspect of network traffic handling.

If the classification has no functional effect, confirmation of that would be valuable so I can focus my troubleshooting elsewhere.

If it does affect traffic handling, I'd appreciate guidance on restoring consistent recognition or providing diagnostic information that would help identify the underlying cause.

Thank you.

[Netduma Fraser]

Steady Ping doesn't show what has been classified so I'm not sure what you're referring to specifically.

1. Yes
2. Yes
3. You can specifically prioritize EA instead of gaming or the device you're playing on itself
4. It's something we'd need to update via the cloud
5. No and it's nothing to do with Steady Ping
6. You should upgrade to the latest firmware version regardless as there are improvements including to the Geo-Filter https://forum.netduma.com/topic/61215-new-r3-firmware-dumaos-401510/ but the cloud version would remain the same so it's unlikely classification would be better or worse.

It's still being detected as gaming so it is still being treated as a gaming application and therefore prioritized/filtered. No need to use AI for troubleshooting!