Battlefield 6 Beta Game mode (boost, QOS) not working

[Redflame]

43 minutes ago, Netduma Fraser said:

You shouldn't have a double NAT if the R3 is in the EE hub DMZ so I'd suggest checking the WAN IP on the R3 is the same as the IP entered in the DMZ.

In that scenario if you need PPPoE for example then yes you can just put those details in and leave everything else the same. You may need to fine tune your Congestion Control settings a little more to get the same results you're used to but otherwise it would be fine. I would look into the DMZ thing though first as you can see reduced speeds and there is also a disconnect issue with PPPoE we're looking into. The R3 won't change any settings unless you change them so no need to screenshot. 

If you have a double NAT even after connecting to the ONT then you have a CG-NAT in which case you only have these options to resolve it:

1. Get a static public IP from the ISP (usually a charged extra)
2. Use a VPN (using a VPN generally gives you a moderate/strict NAT anyway, also an extra charge)
3. Change ISP to one that doesn't use CG-NAT

Hi

So I double checked.

Wan IP > 192.xx.xx.xx is the same as the static ip that is set on ee hub - the one I used since day one.

public ip > is the same one that call of duty, whatismyipaddress dot com and ip info see. 

I don’t know if this is a sign of double Nat or just the way things work in DMZ. But I noticed in trace routes that after dumaos.lan I hit ee router default gateway. 

I’ll show a screenshot,
 

 

[Netduma Fraser]

That's normal, follow this guide to see if you have a CG-NAT https://support.netduma.com/docs/dumaos-3/open-nat/#cg-nat

[Redflame]

On 1/16/2026 at 3:07 PM, Netduma Fraser said:

You shouldn't have a double NAT if the R3 is in the EE hub DMZ so I'd suggest checking the WAN IP on the R3 is the same as the IP entered in the DMZ.

In that scenario if you need PPPoE for example then yes you can just put those details in and leave everything else the same. You may need to fine tune your Congestion Control settings a little more to get the same results you're used to but otherwise it would be fine. I would look into the DMZ thing though first as you can see reduced speeds and there is also a disconnect issue with PPPoE we're looking into. The R3 won't change any settings unless you change them so no need to screenshot. 

If you have a double NAT even after connecting to the ONT then you have a CG-NAT in which case you only have these options to resolve it:

1. Get a static public IP from the ISP (usually a charged extra)
2. Use a VPN (using a VPN generally gives you a moderate/strict NAT anyway, also an extra charge)
3. Change ISP to one that doesn't use CG-NAT

Hi Fraser

Before getting back you I wanted to check lots of stuff.

I can’t do the windows/pc test. We have a laptop but bizarrely my mom’s laptop doesn’t have an Ethernet port. 

R3 and EE hub = the R3 wan ip address is same as DMZ.

So I did port forwarding for cod. And the game still reported moderate Nat type with port forwarding.

My Ps5 connection test says I have the type 2 Nat type.

I asked EE myself for clarification on this and I know you can get conflicting info from isp based on agent, but the agent was adamant they use CG-Nat on all products fibre and mobile (some customers on forums argue they don’t use it for fibre).

Although when I was with BT before my migration opening up a port to cod services give me open Nat. 

So I’m guessing it’s highly plausible that I’m sitting behind CG-Nat. My contract is over in May so I’m going to PlusNet (as BT backbone does give me a good below 1ms jitter connection to most game servers if my local network is kept in check with QOS)

Or I’m going to try Sky but option 61 hurdle worries me lol.

Thanks for all your support, I am very grateful.

[Netduma Fraser]

Does sound like you're on it unfortunately, appreciate you providing an update, good luck with it. You're very welcome!