GL-XE3000 Puli terrible repeater performance

@bruce Unfortunately, it looks like the problem wasn’t fixed. I’m back at a public hotel and experiencing the same problems.

Logs like:
```
Sun Feb 8 00:16:34 2026 kern.err kernel: [71807.907913] 7981@C13L1,tx_free_v3_notify_handler() 3576: ContTxFailCntTotal = 1, ContTxFailCnt300ms = 1
Sun Feb 8 00:16:34 2026 kern.err kernel: [71807.917306] 7981@C13L1,tx_free_v3_notify_handler() 3579: token used by current wcid = 52, free_token_cnt = 2250
Sun Feb 8 00:19:24 2026 kern.err kernel: [71978.018460] 7981@C13L1,tx_free_v3_notify_handler() 3576: ContTxFailCntTotal = 1, ContTxFailCnt300ms = 1
Sun Feb 8 00:19:24 2026 kern.err kernel: [71978.027851] 7981@C13L1,tx_free_v3_notify_handler() 3579: token used by current wcid = 100, free_token_cnt = 2201
```

And speed drops to 1-2mbps. Speed goes back to 60mbps immediately after reboot.

Hello,

R&D guy just checked remotely and found that your XE3000 initially repeated/connected to the hotel Wi‑Fi with the best signal (BSSID is 28:76:10:1e:2c:aa). But we have no idea, probably due to interference or an the hotel Wi-Fi problem (the XE3000 logs event: received a beacon loss), the XE3000 proactively disconnected from the best BSSID (28:76:10:1e:2c:aa).
After re‑connecting/re-repeating, it connected to the same hotel Wi-Fi but a different BSSID with a much weaker signal (28:76:10:1e:29:08), and the signal fluctuates around -86 to -75 dBm, which is quite weak.

This is likely the cause of the slow or intermittent connectivity in this environment.

We cannot remote to your XE3000 now. You can try locking to the stronger BSSID in the repeater and test again.