Problema stabilità upload FTTH dimensione

giuse56 Prova su server UTOPIA fiber, sempre Salt Lake City, sembra essere quello che crea più problemi sulla connessione.
Le versioni web/mobile di speedtest non hanno nessun problema a terminare il test, ma suppongo che sia perché quei warning vengono ignorati e continua ad aprire nuove connessioni (?)
Con vodafone 5G raggiungo i 330 down 60 up, che sono comunque più di quelli che speedtest CLI riporta prima di fallire in upload (e decisamente molti di più di quelli che riporta in download)

Nell'attesa del supporto di dimensione, @giacomix11 riusciresti a linkarmi alcune di queste discussioni sui router? non ne trovo neanche una; oppure direttamente, se riesci, consigliami qualche router che non abbia questa problematica. Prenderei il flint2 come consigliato ma vorrei capire se ci sono alternative

@giusgius @giuse56 Speedtest con Flint2

Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows


~
❯ speedtest -v -v -s 56181
[2024-09-15 14:18:06.974] [info] Resolved address 1: 104.17.148.22
[2024-09-15 14:18:06.975] [info] Resolved address 2: 104.17.147.22
[2024-09-15 14:18:07.183] [info] HTTP request (effective url: https://cli.speedtest.net/api/cli/config?deviceId=b919e86ccc9e22a2fe988d4880bb0634f661dd8d5a93a956b08388b2620c5bb8&hid=a91%2520%2520%2502%250E%2505W%250CZ&serverid=56181&sid=60aeeacd923819f5302a91b85c86c646849f1cf1dff978dd064a6c87cf9c7590&uname=Windows%20%20Microsoft%20Windows%20%5BVersion%2010.0.22621.4037%5D%20AMD64) completed with response code 200
[2024-09-15 14:18:07.188] [info] configuration content:
{"suite":{"global":{"engine":{"isUploadFirst":false,"testDurationSeconds":15,"threadCount":4,"packetSizeBytes":32000000},"dynamic":{"stableStop":{"isEnabled":true},"download":{"isScalingEnabled":true,"maxConnections":32}},"loadedLatency":{"enableUdp":true,"enableTcp":true}},"testStage":{"latency":{"pingCount":5},"upload":{"isServerUploadEnabled":true,"isClientPrimaryMeasureMethod":false}}},"app":{"ispName":"Dimensione","traceLevel":2,"licenseKey":"5af9bbc766f0af80-Ce890d00a2d98daeb-e4139b5e9fe2c55d","license":{"message":"You may only use this Speedtest software and information generated\nfromit for personal, non-commercial use, through a command line\ninterface on a personal computer. Your use of this software is subject\nto the End User License Agreement, Terms of Use and Privacy Policy at\nthese URLs:\n\n\thttps://www.speedtest.net/about/eula\n\thttps://www.speedtest.net/about/terms\n\thttps://www.speedtest.net/about/privacy","version":"aaa8331c62dcaeaf7cbefe8de3952b0240ccae4424412c2e498eeb1beb84b20b"},"gdpr":{"message":"Ookla collects certain data through Speedtest that may be considered\npersonally identifiable, such as your IP address, unique device\nidentifiers or location.Ookla believes it has a legitimate interest\nto share this data with internet providers, hardware manufacturers and\nindustry regulators to help them understand and create a better and\nfaster internet. For further information including how the data may be\nshared, where the data may be transferred and Ookla's contact details,\nplease see our Privacy Policyat:\n\n       http://www.speedtest.net/privacy","acceptTimeout":90},"saveTestResultUrl":"https://results.speedtest.net/reports","resultFormat":"json"},"servers":[{"id":"56181","host":"sh-speedtest.utopiafiber.com:8080","name":"Salt Lake City, UT","country":"United States","sponsor":"UTOPIA Fiber","sponsored":false,"host_functional":"1"}]}

[info] Configuration expiry date: 1727049600

   Speedtest by Ookla

[info] Server count: 1
[info] app.version: 1.2.0.84 (ea6b6773cf)
[info] server selected: 56181
[info] Server id: 56181
[info] Name: Salt Lake City, UT
[info] Country: United States
[info] Sponsor: UTOPIA Fiber
      Server: UTOPIA Fiber - Salt Lake City, UT (id: 56181)
         ISP: Dimensione
[info] Running TCP test suite
[info] Running Speedtest against host:port sh-speedtest.utopiafiber.com:8080
[info] Starting stage 1 of type 2
[info] Resolved address 1: 69.162.234.239
[info] Opening socket to '69.162.234.239'
[info] Ping 1: 144.65 ms (144.65ms min, 0.00ms jitter)
[info] Ping 2: 144.88 ms (144.65ms min, 0.23ms jitter)
[info] Ping 3: 145.27 ms (144.65ms min, 0.31ms jitter)
[info] Ping 4: 144.74 ms (144.65ms min, 0.38ms jitter)
[info] Ping 5: 144.84 ms (144.65ms min, 0.31ms jitter)
[info] Final Ping: 144.65 ms
[info] Stage 1 completed
Idle Latency:   144.82 ms   (jitter: 0.31ms, low: 144.65ms, high: 145.27ms)
[info] Starting stage 2 of type 3
[warning] recvfrom failed: An invalid argument was supplied.

info] Stage 2 completed                                     atency: 142.69 ms
[warning] Loaded latency: cannot read response.: [10053] An established connection was aborted by the software in your host machine.

[info] Smoothing graph for test with 0.707 progress, with duration of 1000 ms in 60 updates
    Download:    16.55 Mbps (data used: 21.1 MB)
                142.72 ms   (jitter: 0.22ms, low: 142.23ms, high: 143.56ms)
[info] Starting stage 3 of type 4
[warning] recvfrom failed: An invalid argument was supplied.

[info] Packet loss sent=171, received=171, dupes=0, maxId=170
[warning] Receive error: 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
)
[info] Connection 1 failed. Added connection and continuing test.
[warning] Receive error: 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
)
[warning] Receive error: 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
)
[info] Connection 2 failed. Added connection and continuing test.
[info] Connection 3 failed. Added connection and continuing test.
[warning] Receive error: 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
)
[info] Connection 4 failed. Added connection and continuing test.
[warning] Receive error: 10060 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
)
      Upload: FAILED
[error] Cannot read:

~ took 21s
❯

Quindi il router non è il colpevole

walt Avevo un sospetto, ma non se ne era mai parlato qui, e data la immediata risposta "è colpa dello ZTE" ho dato la colpa a lui. Il prossimo step nella catena sarebbe proprio l'ONT.
Non sono pratico con openwrt, ma se ci sono log più dettagliati da cui si può capire qualcosa sono disponibile a postare anche quelli

Il problema potrebbe essere un altro
Speedtest CLI Debian (Raspberry Pi OS, Raspberry Pi 5)
Server a londra:

~ $ speedtest -v -v -s 30690
[2024-09-15 15:46:22.844] [info] Resolved address 1: 104.17.147.22
[2024-09-15 15:46:22.844] [info] Resolved address 2: 104.17.148.22
[2024-09-15 15:46:22.986] [info] HTTP request (effective url: https://cli.speedtest.net/api/cli/config?deviceId=69a85da9bd39cc93a3ac14111bcad6130cfd6d28f99c3faac08cd8e8a995e378&hid=%2504%250FO%251E%2509%255EOG%2516C&serverid=30690&sid=ee40e4ea24332b0c6518d6818f9a76b407a7aeb373b8d458fd98ac21e37a511d&uname=Linux%206.6.31%2Brpt-rpi-2712%20%231%20SMP%20PREEMPT%20Debian%201%3A6.6.31-1%2Brpt1%20(2024-05-29)%20aarch64) completed with response code 200
[2024-09-15 15:46:22.986] [info] configuration content:
{"suite":{"global":{"engine":{"isUploadFirst":false,"testDurationSeconds":15,"threadCount":4,"packetSizeBytes":32000000},"dynamic":{"stableStop":{"isEnabled":true},"download":{"isScalingEnabled":true,"maxConnections":32}},"loadedLatency":{"enableUdp":true,"enableTcp":true}},"testStage":{"latency":{"pingCount":5},"upload":{"isServerUploadEnabled":true,"isClientPrimaryMeasureMethod":false}}},"app":{"ispName":"Dimensione","traceLevel":2,"licenseKey":"5af9bbc766f0af80-Cc4ca97ce9091beda-1bb55527eeb045d3","license":{"message":"You may only use this Speedtest software and information generated\nfrom it for personal, non-commercial use, through a command line\ninterface on a personal computer. Your use of this software is subject\nto the End User License Agreement, Terms of Use and Privacy Policy at\nthese URLs:\n\n\thttps://www.speedtest.net/about/eula\n\thttps://www.speedtest.net/about/terms\n\thttps://www.speedtest.net/about/privacy","version":"aaa8331c62dcaeaf7cbefe8de3952b0240ccae4424412c2e498eeb1beb84b20b"},"gdpr":{"message":"Ookla collects certain data through Speedtest that may be considered\npersonally identifiable, such as your IP address, unique device\nidentifiers or location. Ookla believes it has a legitimate interest\nto share this data with internet providers, hardware manufacturers and\nindustry regulators to help them understand and create a better and\nfaster internet. For further information including how the data may be\nshared, where the data may be transferred and Ookla's contact details,\nplease see our Privacy Policy at:\n\n       http://www.speedtest.net/privacy","acceptTimeout":90},"saveTestResultUrl":"https://results.speedtest.net/reports","resultFormat":"json"},"servers":[{"id":"30690","host":"speedtest.thn.lon.network.as201838.net:8080","name":"London","country":"United Kingdom","sponsor":"Community Fibre Limited","sponsored":false,"host_functional":"1"}]}

[info] Configuration expiry date: 1727049600

   Speedtest by Ookla

[info] Server count: 1
[info] app.version: 1.2.0.84 (ea6b6773cf)
[info] server selected: 30690
[info] Server id: 30690
[info] Name: London
[info] Country: United Kingdom
[info] Sponsor: Community Fibre Limited
      Server: Community Fibre Limited - London (id: 30690)
         ISP: Dimensione
[info] Running TCP test suite
[info] Running Speedtest against host:port speedtest.thn.lon.network.as201838.net:8080
[info] Starting stage 1 of type 2
[info] Resolved address 1: 93.113.26.250
[info] Resolved address 2: 2a02:6b67:ffff:fe01::2
[info] Opening socket to '93.113.26.250'
[info] Ping 1: 36.47 ms (36.47ms min, 0.00ms jitter)
[info] Ping 2: 36.31 ms (36.31ms min, 0.16ms jitter)
[info] Ping 3: 36.21 ms (36.21ms min, 0.13ms jitter)
[info] Ping 4: 36.08 ms (36.08ms min, 0.13ms jitter)
[info] Ping 5: 36.32 ms (36.08ms min, 0.15ms jitter)
[info] Final Ping: 36.08 ms
[info] Stage 1 completed
Idle Latency:    36.28 ms   (jitter: 0.15ms, low: 36.08ms, high: 36.47ms)
[info] Starting stage 2 of type 3
[info] Stage 2 completed                                    atency: 37.09 ms
    Download:   726.24 Mbps (data used: 966.6 MB)
                 37.14 ms   (jitter: 2.15ms, low: 36.79ms, high: 317.94ms)
[info] Starting stage 3 of type 4
[warning] Loaded latency: cannot read response.: [0] Cannot read from uninitialized socket.
[info] Packet loss sent=300, received=300, dupes=0, maxId=299
[info] Stage 3 completed                                    atency: 88.60 ms
[info] Smoothing graph for test with 0.681 progress, with duration of 1000 ms in 60 updates
      Upload:   447.11 Mbps (data used: 554.3 MB)
                193.86 ms   (jitter: 57.81ms, low: 37.63ms, high: 1072.03ms)
[info] final result - serverid: 30690 ping: 36 download: 726242 upload: 447110
[info] latency 36ms jitter: 0.15ms packet loss 0.00%
[info] total download bytes: 966608864
[info] total download stage duration: 15008.387000 ms
[info] total upload bytes: 554278259
[info] total upload stage duration: 10213.000000 ms
[info] Resolved address 1: 104.17.148.22
[info] Resolved address 2: 104.17.147.22
[info] Resolved address 1: 104.17.147.22
[info] Resolved address 2: 104.17.148.22
[warning] No libz support available, not compressing data.
[info] HTTP request (effective url: https://results.speedtest.net/reports) completed with response code 200
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/70f1bc36-a145-4702-b619-c4b71634b68f

Server UTOPIA Salt Lake City

~ $ speedtest -v -v -s 56181
[2024-09-15 15:51:09.494] [info] Resolved address 1: 104.17.147.22
[2024-09-15 15:51:09.494] [info] Resolved address 2: 104.17.148.22
[2024-09-15 15:51:09.632] [info] HTTP request (effective url: https://cli.speedtest.net/api/cli/config?deviceId=69a85da9bd39cc93a3ac14111bcad6130cfd6d28f99c3faac08cd8e8a995e378&hid=%2504%250FO%251E%2509%255EOG%2516C&serverid=56181&sid=ee40e4ea24332b0c6518d6818f9a76b407a7aeb373b8d458fd98ac21e37a511d&uname=Linux%206.6.31%2Brpt-rpi-2712%20%231%20SMP%20PREEMPT%20Debian%201%3A6.6.31-1%2Brpt1%20(2024-05-29)%20aarch64) completed with response code 200
[2024-09-15 15:51:09.632] [info] configuration content:
{"suite":{"global":{"engine":{"isUploadFirst":false,"testDurationSeconds":15,"threadCount":4,"packetSizeBytes":32000000},"dynamic":{"stableStop":{"isEnabled":true},"download":{"isScalingEnabled":true,"maxConnections":32}},"loadedLatency":{"enableUdp":true,"enableTcp":true}},"testStage":{"latency":{"pingCount":5},"upload":{"isServerUploadEnabled":true,"isClientPrimaryMeasureMethod":false}}},"app":{"ispName":"Dimensione","traceLevel":2,"licenseKey":"5af9bbc766f0af80-Ce71a58309c2ba339-85985e00c8394156","license":{"message":"You may only use this Speedtest software and information generated\nfrom it for personal, non-commercial use, through a command line\ninterface on a personal computer. Your use of this software is subject\nto the End User License Agreement, Terms of Use and Privacy Policy at\nthese URLs:\n\n\thttps://www.speedtest.net/about/eula\n\thttps://www.speedtest.net/about/terms\n\thttps://www.speedtest.net/about/privacy","version":"aaa8331c62dcaeaf7cbefe8de3952b0240ccae4424412c2e498eeb1beb84b20b"},"gdpr":{"message":"Ookla collects certain data through Speedtest that may be considered\npersonally identifiable, such as your IP address, unique device\nidentifiers or location. Ookla believes it has a legitimate interest\nto share this data with internet providers, hardware manufacturers and\nindustry regulators to help them understand and create a better and\nfaster internet. For further information including how the data may be\nshared, where the data may be transferred and Ookla's contact details,\nplease see our Privacy Policy at:\n\n       http://www.speedtest.net/privacy","acceptTimeout":90},"saveTestResultUrl":"https://results.speedtest.net/reports","resultFormat":"json"},"servers":[{"id":"56181","host":"sh-speedtest.utopiafiber.com:8080","name":"Salt Lake City, UT","country":"United States","sponsor":"UTOPIA Fiber","sponsored":false,"host_functional":"1"}]}

[info] Configuration expiry date: 1727049600

   Speedtest by Ookla

[info] Server count: 1
[info] app.version: 1.2.0.84 (ea6b6773cf)
[info] server selected: 56181
[info] Server id: 56181
[info] Name: Salt Lake City, UT
[info] Country: United States
[info] Sponsor: UTOPIA Fiber
      Server: UTOPIA Fiber - Salt Lake City, UT (id: 56181)
         ISP: Dimensione
[info] Running TCP test suite
[info] Running Speedtest against host:port sh-speedtest.utopiafiber.com:8080
[info] Starting stage 1 of type 2
[info] Resolved address 1: 69.162.234.239
[info] Resolved address 2: 2604:9440:2300:1::5060
[info] Opening socket to '69.162.234.239'
[info] Ping 1: 144.05 ms (144.05ms min, 0.00ms jitter)
[info] Ping 2: 144.06 ms (144.05ms min, 0.01ms jitter)
[info] Ping 3: 144.04 ms (144.04ms min, 0.01ms jitter)
[info] Ping 4: 144.37 ms (144.04ms min, 0.12ms jitter)
[info] Ping 5: 144.19 ms (144.04ms min, 0.14ms jitter)
[info] Final Ping: 144.04 ms
[info] Stage 1 completed
Idle Latency:   144.10 ms   (jitter: 0.14ms, low: 144.04ms, high: 144.37ms)
[info] Starting stage 2 of type 3
[info] Stage 2 completed                                    atency: 229.70 ms
[info] Smoothing graph for test with 0.721 progress, with duration of 1000 ms in 60 updates
    Download:    16.72 Mbps (data used: 21.5 MB)
                215.13 ms   (jitter: 65.21ms, low: 143.22ms, high: 286.91ms)
[info] Starting stage 3 of type 4
[info] Packet loss sent=216, received=216, dupes=0, maxId=215
[info] Stage 3 completed                                    atency: 208.19 ms
[info] Smoothing graph for test with 0.601 progress, with duration of 1000 ms in 60 updates
      Upload:     9.01 Mbps (data used: 10.0 MB)
                213.80 ms   (jitter: 64.81ms, low: 141.78ms, high: 282.84ms)
[info] final result - serverid: 56181 ping: 144 download: 16720 upload: 9011
[info] latency 144ms jitter: 0.14ms packet loss 0.00%
[info] total download bytes: 21534990
[info] total download stage duration: 10812.507000 ms
[info] total upload bytes: 10005120
[info] total upload stage duration: 9001.000000 ms
[info] Resolved address 1: 104.17.147.22
[info] Resolved address 2: 104.17.148.22
[info] Resolved address 1: 104.17.148.22
[info] Resolved address 2: 104.17.147.22
[warning] No libz support available, not compressing data.
[info] HTTP request (effective url: https://results.speedtest.net/reports) completed with response code 200
 Packet Loss:     0.0%
  Result URL: https://www.speedtest.net/result/c/daad89c3-a365-4f6b-9c1e-f825c6abd494

Sempre velocità basse su UTOPIA, ma qui i test finiscono senza problemi

Facendo altri test con un mio amico in inghilterra sembra che la singola connessione sia "cappata" a ~5MB/s, che va a salire quando si aprono più connessioni (che però cadono spesso, riportando la velocità a quella della singola connessione finchè non si riaprono altre connessioni)

Provato anche un trasferimento P2P con torrent privato, quello va dai 600kbps ai 3-4MB/s; ed un test iperf3, anch'esso apparentemente "cappato" alle velocità da single connection

Tutto questo fatto con un Raspberry Pi 5, settato in BBR come mi era già stato consigliato nel precedente thread.

Qualsiasi altra ipotesi è ben accetta, perchè non so più dove mettere le mani e dove/quale possa essere il problema.

giacomix11 router che supporti correttamente i pause frame

Giusto per aggiungere, il flow control/pause frame non sembra avere alcun impatto su questo problema:

root@GL-MT6000:~# ethtool -a eth1
Pause parameters for eth1:
Autonegotiate:  off
RX:             off
TX:             off

❯ speedtest -s 36817

   Speedtest by Ookla

      Server: Surfshark Ltd - New York, NY (id: 36817)
         ISP: Dimensione
Idle Latency:   101.12 ms   (jitter: 0.27ms, low: 100.90ms, high: 101.38ms)
    Download:  1220.81 Mbps (data used: 2.0 GB)
                101.26 ms   (jitter: 4.50ms, low: 100.69ms, high: 266.82ms)
      Upload: FAILED                                            cy: 100.86 ms
[error] Cannot read:

root@GL-MT6000:~# ethtool -A eth1 rx on tx on
root@GL-MT6000:~# ethtool -a eth1
Pause parameters for eth1:
Autonegotiate:  off
RX:             on
TX:             on
[ 4955.091271] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 2.5Gbps/Full - flow control rx/tx

❯ speedtest -s 36817

   Speedtest by Ookla

      Server: Surfshark Ltd - New York, NY (id: 36817)
         ISP: Dimensione
Idle Latency:    96.30 ms   (jitter: 0.42ms, low: 95.94ms, high: 96.55ms)
    Download:  1388.81 Mbps (data used: 2.3 GB)
                170.36 ms   (jitter: 35.56ms, low: 96.38ms, high: 1545.14ms)
      Upload: FAILED                                            cy: 102.79 ms
[error] Cannot read:

Aggiornamento: ieri ho chiamato l'assistenza di dimensione per sentire se ci fossero novità, mi hanno confermato che il problema è dell'ONT (quindi presumo sia il ben noto problema con il flow control su questo modello) e che stanno aspettando un aggiornamento del firmware, ma non hanno tempistiche specifiche perchè giustamente non è una cosa in carico a loro direttamente.
Domanda, sarebbe possibile richiedere ad OF un cambio di ONT con, per esempio, lo ZTE F6005v3 che risolve questo problema? Oppure devo armarmi di pazienza ed aspettare che nokia rilasci un aggiornamento (se mai lo rilasceranno, visto che il supporto mi dice che questo problema c'è da anni)? Mi sembra assurdo avere 500/1000mbit in upload e non poterli sfruttare per un bug software dell'ONT.

TheMarsican Dimensione potrebbe spingere per un cambio ma se gli approvigionamenti della ditta di zona sono carenti del v3 allora nada.

@giusgius allora credo sia meglio chiedere direttamente a te se è possibile

TheMarsican Non è un bug software, il nokia ha i buffer sottodimensionati.
Nemmeno con flow control o QoS si sistema.

Quindi anche con un aggiornamento software dell'ONT il problema potrebbe rimanere?