Details
-
Task
-
Resolution: Done
-
P2: Important
-
6.0
-
-
3
-
a0bfa4e1f8e223927cbb285bb17d1a00a5c2d4b6 (qt/qtbase/dev) a96fc6e65cba14d80665ef5f8932f004f7f4a1e3 (qt/qtbase/5.15)
-
Qt6_Foundation_ Sprint 11
Description
We should try to connect even if some data points to us being disconnected (e.g. OS reporting LAN access only, or disconnected).
With both bearer (and now QNetworkStatusMonitor) there have been cases where making connections is impossible. These scenarios include being connected to VPN, where the OS thinks we're unable to access anything, or trying to connect when the OS is unable to ping their service of choice to see if it's accessible (done periodically, most commonly fails after reestablishing a connection or shortly after boot).
If we instead try to make the connection then it will still work reliably in these situations, and we'll just fail to connect if there's actually no network.
Note: it's not about removing QNetworkStatusMonitor (it has different thought-of usecases...), just about not using it to pre-emptively abort connections.
Attachments
Issue Links
- is required for
-
QTBUG-80947 [REG 5.13.1 -> 5.14] QNetworkAccessManager::get() fails with UnknownNetworkError when VPN is connected
- Closed
For Gerrit Dashboard: QTBUG-84907 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
304158,2 | QNAM: Remove network connectivity pre-check | dev | qt/qtbase | Status: MERGED | +2 | 0 |
304826,5 | QNAM: Fix my silly leftover mistake | dev | qt/qtbase | Status: MERGED | +2 | 0 |
308807,6 | QNAM: Remove network connectivity pre-check | 5.15 | qt/qtbase | Status: MERGED | +2 | 0 |