connessione 3g tre, roma , ponte di nona, situazione scandalosa

ecco un report con un po’ di dati tecnici sulle fantasmagoriche performance delle mia chiavetta H3G a Roma (zona Ponte di Nona)

Dati di connessione:

Jun  6 17:31:04 pppd[351]: pppd 2.4.2 started by admin, uid 0 
Jun  6 17:31:06 pppd[351]: Serial connection established. 
Jun  6 17:31:06 pppd[351]: Using interface ppp0 
Jun  6 17:31:06 pppd[351]: Connect: ppp0 <--> /dev/usb/tts/0 
Jun  6 17:31:12 pppd[351]: Could not determine remote IP address: defaulting to 10.64.64.64 
Jun  6 17:31:12 pppd[351]: local  IP address 10.56.62.248 
Jun  6 17:31:12 pppd[351]: remote IP address 10.64.64.64 
Jun  6 17:31:12 pppd[351]: primary   DNS address 62.13.173.117 
Jun  6 17:31:12 pppd[351]: secondary DNS address 62.13.173.116 
Jun  6 17:31:12 dnsmasq[76]: read /etc/hosts - 5 addresses 
Jun  6 17:31:12 dnsmasq[76]: reading /tmp/resolv.conf 
Jun  6 17:31:12 dnsmasq[76]: using nameserver 62.13.173.116#53 
Jun  6 17:31:12 dnsmasq[76]: using nameserver 62.13.173.117#53 
Jun  6 17:31:15 USB Connection: connected to ISP

test ping di www.google.it

[admin@WL-0026180FA460 root]$ ping www.google.it 
PING www.l.google.com (72.14.234.104): 56 data bytes 
72 bytes from 72.14.234.104: icmp_seq=0 ttl=56 time=138.2 ms 
72 bytes from 72.14.234.104: icmp_seq=1 ttl=56 time=143.9 ms 
72 bytes from 72.14.234.104: icmp_seq=2 ttl=56 time=143.8 ms 
72 bytes from 72.14.234.104: icmp_seq=3 ttl=56 time=143.7 ms 
72 bytes from 72.14.234.104: icmp_seq=4 ttl=56 time=483.6 ms 
72 bytes from 72.14.234.104: icmp_seq=5 ttl=56 time=5254.1 ms 
72 bytes from 72.14.234.104: icmp_seq=6 ttl=56 time=4275.1 ms 
72 bytes from 72.14.234.104: icmp_seq=7 ttl=56 time=3525.0 ms 
72 bytes from 72.14.234.104: icmp_seq=8 ttl=56 time=2526.0 ms 
72 bytes from 72.14.234.104: icmp_seq=9 ttl=56 time=1527.0 ms 
72 bytes from 72.14.234.104: icmp_seq=10 ttl=56 time=529.0 ms 
72 bytes from 72.14.234.104: icmp_seq=11 ttl=56 time=134.0 ms 
72 bytes from 72.14.234.104: icmp_seq=12 ttl=56 time=133.9 ms 
72 bytes from 72.14.234.104: icmp_seq=13 ttl=56 time=133.8 ms 
72 bytes from 72.14.234.104: icmp_seq=14 ttl=56 time=133.7 ms 
72 bytes from 72.14.234.104: icmp_seq=15 ttl=56 time=829.5 ms 
72 bytes from 72.14.234.104: icmp_seq=16 ttl=56 time=319.5 ms 
72 bytes from 72.14.234.104: icmp_seq=17 ttl=56 time=329.4 ms 
72 bytes from 72.14.234.104: icmp_seq=18 ttl=56 time=329.3 ms 
72 bytes from 72.14.234.104: icmp_seq=19 ttl=56 time=4114.8 ms 
72 bytes from 72.14.234.104: icmp_seq=20 ttl=56 time=3135.8 ms 
72 bytes from 72.14.234.104: icmp_seq=21 ttl=56 time=2155.8 ms 
72 bytes from 72.14.234.104: icmp_seq=22 ttl=56 time=1156.8 ms 
72 bytes from 72.14.234.104: icmp_seq=23 ttl=56 time=214.8 ms 
72 bytes from 72.14.234.104: icmp_seq=24 ttl=56 time=136.7 ms 
72 bytes from 72.14.234.104: icmp_seq=25 ttl=56 time=135.6 ms 
72 bytes from 72.14.234.104: icmp_seq=26 ttl=56 time=135.5 ms 
72 bytes from 72.14.234.104: icmp_seq=27 ttl=56 time=1547.3 ms 
72 bytes from 72.14.234.104: icmp_seq=28 ttl=56 time=847.2 ms 
72 bytes from 72.14.234.104: icmp_seq=29 ttl=56 time=330.2 ms 
72 bytes from 72.14.234.104: icmp_seq=79 ttl=56 time=17541.3 ms 
72 bytes from 72.14.234.104: icmp_seq=80 ttl=56 time=24190.6 ms 
72 bytes from 72.14.234.104: icmp_seq=82 ttl=56 time=22230.6 ms 
72 bytes from 72.14.234.104: icmp_seq=81 ttl=56 time=23272.5 ms 
72 bytes from 72.14.234.104: icmp_seq=166 ttl=56 time=27151.7 ms 
72 bytes from 72.14.234.104: icmp_seq=291 ttl=56 time=17381.5 ms

--- www.l.google.com ping statistics --- 
323 packets transmitted, 36 packets received, 88% packet loss 
round-trip min/avg/max = 133.7/4630.8/27151.7 ms

n.b. il ping è stato fatto direttamente dal router. il traceroute non da segni di vita

riprovo a pingare il DNS server:

[admin@WL-0026180FA460 root]$ ping 62.13.173.117 
PING 62.13.173.117 (62.13.173.117): 56 data bytes

--- 62.13.173.117 ping statistics --- 
61 packets transmitted, 0 packets received, 100% packet loss

niente..

Sto pensando seriamente di chiedere una rescissione di contratto per mancata fornitura di servizi.

2 risposte a “connessione 3g tre, roma , ponte di nona, situazione scandalosa”

Mentions

  • acor3
  • damiano

Lascia un commento

Il tuo indirizzo email non sarà pubblicato. I campi obbligatori sono contrassegnati *

Questo sito utilizza Akismet per ridurre lo spam. Scopri come vengono elaborati i dati derivati dai commenti.

Per rispondere sul tuo sito web, inserisci l'URL della tua risposta che dovrebbe contenere un link all'URL del permalink di questo post. La tua risposta verrà quindi visualizzata (possibilmente dopo la moderazione) in questa pagina. Vuoi aggiornare o rimuovere la tua risposta? Aggiorna o elimina il tuo post e inserisci nuovamente l'URL del tuo post. (Ulteriori informazioni)