WLAN Link Speed Incorrect

Owstap · ‎12-09-2022

Hi there!

I am currently signed up with EE for Fibre Max 900, with 900down and 100up. However on the router manager the WLAN Link speed is showing as 100Mbps, and the downstream and upstream rates are both saying 100Mbps instead of 900/100. Is there anything I can do to change this or is it a case of calling in?

I have checked my account and it is still showing Max 900, suggesting that I haven't been downgraded from EE's end??

Mustrum · ‎13-09-2022

@Owstap On your earlier pic it shows your WAN link has been up for 29mins, but the system up for 64 days. A quick power off to the modem and Openreach ONT may well get you back to full speed.

But also check and maybe try another cable between the router and ONT.

Let is know how it goes.

View solution in original post

XRaySpeX · ‎12-09-2022

That's not a Wireless LAN speed; that's an Ethernet speed.

What's the rest of that page say? Obscure your names & any numbers in the BB Username.

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP

Owstap · ‎13-09-2022

Sorry I linked the wrong photo. I've attached the bit that mentions WLAN, and the other page in full!

XRaySpeX · ‎13-09-2022

& still the rest of that page please?

WAN (Wide Area Network) is not the same as WLAN (Wireless Local Area Network).

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP

Owstap · ‎13-09-2022

XRaySpeX · ‎13-09-2022

OK! So, on which page do you see the WAN Link Speed, that you showed above the Home > Advanced Settings > BB > Internet page? Your pages are confusing me.

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP

Owstap · ‎13-09-2022

so the WAN link speed is showing under the Status Tab. And the other picture, is where you mentioned. Under advanced settings > BB > Internet

Mustrum · ‎13-09-2022

@Owstap On your earlier pic it shows your WAN link has been up for 29mins, but the system up for 64 days. A quick power off to the modem and Openreach ONT may well get you back to full speed.

But also check and maybe try another cable between the router and ONT.

Let is know how it goes.

pip11 · ‎13-09-2022

There is omething wrong somewhere. With FTTP the WAN speed should show as 1000Mb up & down as it is the link speed between ONT & Hub.

As suggested try chanking the ethernet patch cable between ONT and router.

Owstap · ‎13-09-2022

Okay I will try powering them both off and see how it goes.

So based on what you’re saying, am I right in thinking that if if the Ethernet cable from the openreach modem to the router is only capable of say 100Mbps then it will actually recognise that and limit it? I would have thought it would still show the 1000mbps cap but not actually be able to reach it?!

But then again I’m not clued up on BB ;D

Now you mention it, I did replace the cable from ONT > Hub around 2 months ago, which probably coincides with when the problem started