nothepin0 Qual è il tuo setup?
Problema stabilità upload FTTH dimensione
andreagdipaolo PC desktop connesso con cavo ethernet direttamente al router, NIC Realtek 2.5Gb e connessione negoziata correttamente a 2500/2500, ONT Nokia G-010G-T, quello nero di OF per la 2.5G.
nothepin0 se hai il router zte la causa del upload failed o basso su server lontani o con ping maggiore di 20ms è lui
LucaPerazzolo Si, il router è proprio lo ZTE H6645P V2 fornito da dimensione. Come dovrei procedere? è una cosa che posso risolvere con l'assistenza di dimensione o devo attrezzarmi io a comprare un altro router?
- Modificato
nothepin0 qualche mese fa si parlava di una beta che sembrava risolvesse il problema, però non se ne è più saputo nulla.
personalmente ci ho perso le speranze, tra questo e vari bug del router mai risolti
nothepin0 è una cosa che posso risolvere con l'assistenza di dimensione o devo attrezzarmi io a comprare un altro router?
potresti provare a chiedere questo aggiornamento all'assistenza o a giuseppe, oppure dovresti cercarti un router che supporti correttamente i pause frame (vedi altre discussioni a riguardo)
nothepin0 probabilmente fai prima a cambiarlo con un flint2 ad esempio
@giusgius scusa il disturbo, tu sai qualcosa di questo problema ed il relativo aggiornamento?
giusgius No, negoziando 1000/1000 il problema persiste
Ora ho inviato una mail all'assistenza, grazie
Aggiornamento: oggi mi ha chiamato l'assistenza di dimensione per caricare un firmware fornito da ZTE che doveva risolvere il problema, ma nulla. Sempre le stesse problematiche sugli stessi server sui quali avevo provato io e anche quelli dettati dal supporto. Ora dicono di dover sentire OF (presumo per scongiurare eventuali problemi di trasporto?) e poi mi sapranno dire. Assistenza da 5 ma spero di riuscire ad uscirne presto perchè tra questo ed altri problemi, sta fibra mi sta sembrando un po' un calvario.
nothepin0 Ho provato per curiosità e anche sotto linea Fibercop e ONT Sercomm ottengo risultati molto simili. A me completa la Stage 3 dell'upload ma la velocità è ugualmente bassa e ci sono gli stessi errori di connessione.
Dubito che il problema sia OpenFiber, altrimenti non si verificherebbe anche a me...
Direi che c'è un problema sulla prima parte in carico alla rete Fastweb o semplicemente il firmware aggiornato non ha risolto nulla.
E:\Downloads\ookla-speedtest-1.2.0-win64>speedtest -v -v -s 56181
[2024-09-11 21:09:54.851] [info] Resolved address 1: 104.17.147.22
[2024-09-11 21:09:54.851] [info] Resolved address 2: 104.17.148.22
[2024-09-11 21:09:55.024] [info] HTTP request (effective url: https://cli.speedtest.net/api/cli/config?deviceId=5489a767c9927c43f5b786bce51b445f80eea42bccfef684e1f031887823be33&hid=(n%253BgE%2515O%251C&serverid=56181&sid=e393e1763a99f0f74076a7d3ba1c8493ec33b9c627460c69e049ab2c8bd1bad4&uname=Windows%20%20Microsoft%20Windows%20%5BVersione%2010.0.22631.4037%5D%20AMD64) completed with response code 200
[2024-09-11 21:09:55.040] [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":"75a3cba866eb6980-Cc861720ee17a64ad-3335a31c05352bab","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: 1726704000
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: 2604:9440:2300:1::5060
[info] Resolved address 2: 69.162.234.239
[info] Opening socket to '2604:9440:2300:1::5060'
[info] Ping 1: 144.66 ms (144.66ms min, 0.00ms jitter)
[info] Ping 2: 144.40 ms (144.40ms min, 0.27ms jitter)
[info] Ping 3: 144.81 ms (144.40ms min, 0.34ms jitter)
[info] Ping 4: 145.02 ms (144.40ms min, 0.30ms jitter)
[info] Ping 5: 144.78 ms (144.40ms min, 0.28ms jitter)
[info] Final Ping: 144.40 ms
[info] Stage 1 completed
Idle Latency: 144.76 ms (jitter: 0.28ms, low: 144.40ms, high: 145.02ms)
[info] Starting stage 2 of type 3
info] Stage 2 completed atency: 214.11 ms
[warning] Loaded latency: cannot read response.: [10053] Connessione interrotta dal software del computer host.
[info] Smoothing graph for test with 0.894 progress, with duration of 1000 ms in 60 updates
Download: 18.12 Mbps (data used: 29.6 MB)
215.46 ms (jitter: 70.99ms, low: 143.70ms, high: 289.22ms)
[info] Starting stage 3 of type 4
[info] Packet loss sent=214, received=214, dupes=0, maxId=213
[warning] Receive error: 10060 (Impossibile stabilire la connessione. Risposta non corretta della parte connessa dopo l'intervallo di tempo oppure mancata risposta dall'host collegato.
)
[info] Connection 1 failed. Added connection and continuing test.
[warning] Receive error: 10060 (Impossibile stabilire la connessione. Risposta non corretta della parte connessa dopo l'intervallo di tempo oppure mancata risposta dall'host collegato.
)
[info] Connection 2 failed. Added connection and continuing test.
[warning] Receive error: 10060 (Impossibile stabilire la connessione. Risposta non corretta della parte connessa dopo l'intervallo di tempo oppure mancata risposta dall'host collegato.
)
[info] Connection 3 failed. Added connection and continuing test.
warning] Loaded latency: cannot read response.: [10053] Connessione interrotta dal software del computer host.
[info] Stage 3 completed
Upload: 76.30 Mbps (data used: 134.7 MB)
214.59 ms (jitter: 70.67ms, low: 142.68ms, high: 286.44ms)
[info] final result - serverid: 56181 ping: 144 download: 18124 upload: 76297
[info] latency 144ms jitter: 0.28ms packet loss 0.00%
[info] total download bytes: 29638957
[info] total download stage duration: 13408.949000 ms
[info] total upload bytes: 134691137
[info] total upload stage duration: 15010.000000 ms
[info] Resolved address 1: 104.17.147.22
[info] Resolved address 2: 104.17.148.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/6847042f-ac9b-480d-90d4-026a0c422db3
- Modificato
nothepin0 Mi aggiorni anche a me su come va a finire e se risolvi? Così poi mi faccio fare l'aggiornamento dall'assistenza anche io.
Provando anche io su un server Salt Lake come te (Comcast) mi da risultati migliori dei tuoi, seppur i miei sono in WiFi https://www.speedtest.net/my-result/a/10369554073
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
Premesso che sulla mia FTTH Dimensione su rete OF con consegna Milano ed ONT ZTE F6005 l'anomalia non si riscontra (indipendentemente dal router, comunque al momento utilizzo proprio un Flint 2)
Server: UTOPIA Fiber - Salt Lake City, UT (id: 56181)
ISP: Dimensione
Idle Latency: 144.48 ms (jitter: 0.08ms, low: 144.38ms, high: 144.57ms)
Download: 16.89 Mbps (data used: 21.8 MB)
218.60 ms (jitter: 65.66ms, low: 144.67ms, high: 289.57ms)
Upload: 8.97 Mbps (data used: 9.0 MB)
212.32 ms (jitter: 64.69ms, low: 141.81ms, high: 283.17ms)
Packet Loss: 0.0%
espongo una mia curiosità: in generale la possibilità che essa dipenda quanto meno dal modello ONT è già stata vagliata?
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