U

Saturday, October 5th, 2024 12:44 AM

XB8 Packet loss every 3 mins on AX band

Hello,

I believe there is a firmware bug on XB8 side which is causing packet loss every 3 minutes or so causing lag in gaming. This only happens on Wi-Fi 6 (802.11ax) protocol. FWIW, I have validated this with forcing to pick 802.11ac band and it works fine for hours. I first noticed this roughly 9/11/2024. 


I have since then tried everything updating windows drivers (bios, chips, nic, etct), played with adapter settings (low roaming, throughput booster, etc), resetting windows entirely.

Last night I did a hard reset on the router and it worked fine for hours on AX band. I believe it updated firmware over night and we are back to the issue.

This might be due to bad firmware Prod_23.2_231009 & Prod_23.2_231009 and i also found this.

https://forums.xfinity.com/conversations/your-home-network/xb8-downstream-upstream-codewords-tables-missing-stats/66f71a53508eb700bea0a2dc

4 Messages

2 months ago

I would also like to add that I get Large Segment offload (intel warning 6062), "Connection telemetry fields and analysis usage" (7021), and "roam complete" (7003) every 3ish minutes (sometimes more or less) from my nic. These 3 info/warnings do not happen when I am on AC band or the router is hard resetted.

4 Messages

I performed another hard reset around 12am this morning. Its 2:30 now and few 6062 errors but nothing major.

I was able to play games without many lags, may be 1 or 2 with correlated warnings.

4 Messages

Around 3:00am i decided to manually reboot the router via "RESET" button and viola lags are back. I believe firmware upgrades are done on resets.

I also have a powershell script that pings every second to google's dns and warning times co-relate with ping timeouts too.

`ping.exe -t 8.8.8.8 | ForEach{"{0} - {1}" -f (Get-Date),$_}`

10/5/2024 3:23:40 AM - Reply from 8.8.8.8: bytes=32 time=14ms TTL=56
10/5/2024 3:23:41 AM - Reply from 8.8.8.8: bytes=32 time=52ms TTL=56
10/5/2024 3:23:46 AM - Request timed out.
10/5/2024 3:23:47 AM - Reply from 8.8.8.8: bytes=32 time=30ms TTL=56
10/5/2024 3:23:48 AM - Reply from 8.8.8.8: bytes=32 time=21ms TTL=56

...
10/5/2024 3:37:47 AM - Reply from 8.8.8.8: bytes=32 time=133ms TTL=56
10/5/2024 3:37:47 AM - Reply from 8.8.8.8: bytes=32 time=61ms TTL=56
10/5/2024 3:37:49 AM - Request timed out.
10/5/2024 3:37:50 AM - Reply from 8.8.8.8: bytes=32 time=19ms TTL=56
10/5/2024 3:37:51 AM - Reply from 8.8.8.8: bytes=32 time=15ms TTL=56
...

10/5/2024 3:40:47 AM - Reply from 8.8.8.8: bytes=32 time=135ms TTL=56
10/5/2024 3:40:48 AM - Reply from 8.8.8.8: bytes=32 time=85ms TTL=56
10/5/2024 3:40:52 AM - Request timed out.
10/5/2024 3:40:53 AM - Reply from 8.8.8.8: bytes=32 time=19ms TTL=56
10/5/2024 3:40:54 AM - Reply from 8.8.8.8: bytes=32 time=23ms TTL=56

...

Official Employee

 • 

1.2K Messages

Hello user_m7p7uz thank you for taking the time to reach out with these concerns on the XB8 modem and the context of that adjacent Forums post. We'd love to help look into this for you. 

 

Please send a direct message by clicking the chat icon in the upper right corner of the page, clicking on the pen and paper icon, and then entering “Xfinity Support” in the “To” section. Please include your name and address, and I'll be happy to help.

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick
forum icon

New to the Community?

Start Here