[S.Li.P] connessione internet saltata tramite router
Valentino Bocchino
valentinobocchino17 a gmail.com
Gio 28 Dic 2023 22:36:08 CET
Confermo le ipotesi di Davide.
Per modificare il DNS puoi direttamente agire sul router o modificare le
impostazioni su tutti i client del router (ovvero i tuoi computer). Per
modificare le impostazioni sui tuoi computer, in base al sistema operativo
che utilizzi devi fare in modo che loro non usino come riferimento DNS il
router ma un indirizzo che tu definisci. IPv4 o IPv6 sono soltanto
protocolli internet. Non è detto che il tuo ISP supporti IPv6. In ogni
caso, per farla semplice, impostare il DNS IPv4 dovrebbe essere sufficiente
per risolvere i tuoi problemi. 8.8.8.8 è il DNS di Google ed è uno dei più
diffusi e rapidi. Siccome però come in ogni argomento riguardante internet
potrebbero aprirsi discussioni etiche importanti, informati su cosa sia un
DNS e dopodiché fai una scelta consapevole.
In ogni caso... Se desideri configurare la versione IPv4 con il DNS di
Google, specifica come indirizzo IP 8.8.8.8 (oppure 8.8.4.4). Puoi anche
specificare entrambi gli indirizzi anche se come seconda scelta non userei
lo stesso DNS.
Se desideri configurare la versione IPv6 con il DNS di Google, specifica
come indirizzo IP 2001:4860:4860::8888 (oppure 2001:4860:4860::8844).
Questa è la forma abbreviata, tuttavia se non viene accettata...
2001:4860:4860:0:0:0:0:8888 (oppure 2001:4860:4860:0:0:0:0:8844). Anche se
configuri IPv6, se non dovesse essere supportato non dovrebbe succedere
nulla. Probabilmente andrà in "fallback" su IPv4.
Consiglio comunque di agire sul router perché così non dovrai riconfigurare
ogni dispositivo che si collega.
Ciaooo :)
Il gio 28 dic 2023, 22:07 Alessandra Neve via SLiP <
slip a liszt.softwareliberopinerolo.org> ha scritto:
> Con cavo ethernet
>
> ~$ ping -c 5 8.8.8.8
> PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=15.5 ms
> 64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=16.7 ms
> 64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=54.6 ms
> 64 bytes from 8.8.8.8: icmp_seq=4 ttl=118 time=16.0 ms
> 64 bytes from 8.8.8.8: icmp_seq=5 ttl=118 time=17.4 ms
>
> --- 8.8.8.8 ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 4006ms
> rtt min/avg/max/mdev = 15.527/24.042/54.619/15.301 ms
>
> Allora, modifico Ipv4 o Ipv6?
> e che numeri ci metto?
>
> Il giorno gio 28 dic 2023 alle ore 20:43 Valentino Bocchino via SLiP <
> slip a liszt.softwareliberopinerolo.org> ha scritto:
>
>> Ci sta, sarebbe interessante vedere con connessione Ethernet se fa la
>> stessa cosa. Perché se così fosse deve intervenire l'ISP.
>>
>> Il gio 28 dic 2023, 20:40 Davide Corio via SLiP <
>> slip a liszt.softwareliberopinerolo.org> ha scritto:
>>
>>> Presumo connessione wifi ad una certa distanza dal router
>>>
>>> Il gio 28 dic 2023, 20:36 Valentino Bocchino via SLiP <
>>> slip a liszt.softwareliberopinerolo.org> ha scritto:
>>>
>>>> Siamo sicuri che sia solo una questione di DNS? Perché una latenza di
>>>> 1797ms verso 8.8.8.8 è indecente.
>>>>
>>>> Il gio 28 dic 2023, 16:50 Alessandra Neve via SLiP <
>>>> slip a liszt.softwareliberopinerolo.org> ha scritto:
>>>>
>>>>> tipo Ip4 o IPv6?
>>>>>
>>>>> Il giorno gio 28 dic 2023 alle ore 16:49 Alessandra Neve <
>>>>> alessandra.neve a gmail.com> ha scritto:
>>>>>
>>>>>> E' quello che ho pensato io (credo mi fosse già capitato). Ma le mie
>>>>>> conoscenze si fermano qui e stavolta non riesco a trovare info alla mia
>>>>>> portata che mi permettano l'impostazione manuale.
>>>>>> Qualche dritta? Link dove guardare?
>>>>>> grazie..
>>>>>>
>>>>>> Il giorno gio 28 dic 2023 alle ore 16:45 Davide Corio via SLiP <
>>>>>> slip a liszt.softwareliberopinerolo.org> ha scritto:
>>>>>>
>>>>>>> Probabilmente è solo un problema di DNS.
>>>>>>> Magari il router sta fornendo DNS che non vanno.
>>>>>>>
>>>>>>> Puoi provare ad impostarli manualmente su PC.
>>>>>>> Tipo 8.8.8.8 che è quello di Google, oppure OpenDNS o simili che
>>>>>>> generalmente sono meglio di quelli del provider.
>>>>>>>
>>>>>>> Il gio 28 dic 2023, 16:39 Alessandra Neve via SLiP <
>>>>>>> slip a liszt.softwareliberopinerolo.org> ha scritto:
>>>>>>>
>>>>>>>> Ah già, dimenticavo
>>>>>>>>
>>>>>>>>
>>>>>>>> *:~$ ping -c 5 8.8.8.8*PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
>>>>>>>> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=25.6 ms
>>>>>>>> 64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=18.8 ms
>>>>>>>> 64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=395 ms
>>>>>>>> 64 bytes from 8.8.8.8: icmp_seq=4 ttl=118 time=1797 ms
>>>>>>>> 64 bytes from 8.8.8.8: icmp_seq=5 ttl=118 time=811 ms
>>>>>>>>
>>>>>>>> --- 8.8.8.8 ping statistics ---
>>>>>>>> 5 packets transmitted, 5 received, 0% packet loss, time 4034ms
>>>>>>>> rtt min/avg/max/mdev = 18.774/609.532/1797.103/661.394 ms, pipe 2
>>>>>>>>
>>>>>>>>
>>>>>>>> Il giorno gio 28 dic 2023 alle ore 16:38 Davide Corio via SLiP <
>>>>>>>> slip a liszt.softwareliberopinerolo.org> ha scritto:
>>>>>>>>
>>>>>>>>> Se lanci un semplice ping 8.8.8.8 che dice?
>>>>>>>>>
>>>>>>>>> Il gio 28 dic 2023, 16:23 Alessandra Neve via SLiP <
>>>>>>>>> slip a liszt.softwareliberopinerolo.org> ha scritto:
>>>>>>>>>
>>>>>>>>>> Ciao
>>>>>>>>>> non so se sia OT visto che non riguarda solo il mio portatile con
>>>>>>>>>> mate 20.04, ma anche l'altro col SO più antipatico del globo.
>>>>>>>>>>
>>>>>>>>>> I 2 portatili vedono il router tp-link a cui risultano connessi
>>>>>>>>>> correttamente ma da nessuno dei due si accede ad internet da quando il
>>>>>>>>>> portatile materno (il terzo) con win 11 ha provato a connettersi anche
>>>>>>>>>> lui...
>>>>>>>>>>
>>>>>>>>>> Se ci colleghiamo tramite antenna BBBell navighiamo, ma
>>>>>>>>>> attraverso il router no.
>>>>>>>>>>
>>>>>>>>>> Prove basic effettuate senza risultati:
>>>>>>>>>> - spegnimento e riaccensione (anche del frigorifero)
>>>>>>>>>> - togli e metti cavi
>>>>>>>>>> - riavvia pc
>>>>>>>>>> - rete domestica vs rete pubblica
>>>>>>>>>> - verifica antivirus
>>>>>>>>>> - pennichella per rilassarsi
>>>>>>>>>>
>>>>>>>>>> Output dei comandi:
>>>>>>>>>>
>>>>>>>>>> *~$ route -n*
>>>>>>>>>> Tabella di routing IP del kernel
>>>>>>>>>> Destinazione Gateway Genmask Flag Metric Ref Usa Iface
>>>>>>>>>> 0.0.0.0 192.168.43.1 0.0.0.0 UG 600 0
>>>>>>>>>> 0 wlo1
>>>>>>>>>> 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0
>>>>>>>>>> 0 wlo1
>>>>>>>>>> 192.168.43.0 0.0.0.0 255.255.255.0 U 600 0
>>>>>>>>>> 0 wlo1
>>>>>>>>>>
>>>>>>>>>> *~$ ifconfig*
>>>>>>>>>> eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
>>>>>>>>>> ether e8:d8:d1:33:a3:c3 txqueuelen 1000 (Ethernet)
>>>>>>>>>> RX packets 0 bytes 0 (0.0 B)
>>>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0
>>>>>>>>>> TX packets 0 bytes 0 (0.0 B)
>>>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>>>>>>>>>
>>>>>>>>>> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
>>>>>>>>>> inet 127.0.0.1 netmask 255.0.0.0
>>>>>>>>>> inet6 ::1 prefixlen 128 scopeid 0x10<host>
>>>>>>>>>> loop txqueuelen 1000 (Loopback locale)
>>>>>>>>>> RX packets 20400 bytes 1728204 (1.7 MB)
>>>>>>>>>> RX errors 0 dropped 0 overruns 0 frame 0
>>>>>>>>>> TX packets 20400 bytes 1728204 (1.7 MB)
>>>>>>>>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
>>>>>>>>>>
>>>>>>>>>> wlo1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
>>>>>>>>>> inet 192.168.43.104 netmask 255.255.255.0 broadcast
>>>>>>>>>> 192.168.43.255
>>>>>>>>>> inet6 fe80::20dc:9997:69df:ad54 prefixlen 64 scopeid
>>>>>>>>>> 0x20<link>
>>>>>>>>>> ether c0:e4:34:73:29:3d txqueuelen 1000 (Ethernet)
>>>>>>>>>> RX packets 31221 bytes 124773013 (124.7 MB)
>>>>>>>>>> RX errors 0 dropped 8812 overruns 0 frame 0
>>>>>>>>>> TX packets 30073 bytes 70483494 (70.4 MB)
>>>>>>>>>> TX errors 0 dropped 196 overruns 0 carrier 0
>>>>>>>>>> collisions 0
>>>>>>>>>>
>>>>>>>>>> Prima di addentrarmi oltre, ho pensato a voi, prodi linuxiani.
>>>>>>>>>> mciù
>>>>>>>>>> --
>>>>>>>>>> SLiP mailing list
>>>>>>>>>> SLiP a liszt.softwareliberopinerolo.org
>>>>>>>>>> https://liszt.softwareliberopinerolo.org/listinfo/slip
>>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> SLiP mailing list
>>>>>>>>> SLiP a liszt.softwareliberopinerolo.org
>>>>>>>>> https://liszt.softwareliberopinerolo.org/listinfo/slip
>>>>>>>>>
>>>>>>>> --
>>>>>>>> SLiP mailing list
>>>>>>>> SLiP a liszt.softwareliberopinerolo.org
>>>>>>>> https://liszt.softwareliberopinerolo.org/listinfo/slip
>>>>>>>>
>>>>>>> --
>>>>>>> SLiP mailing list
>>>>>>> SLiP a liszt.softwareliberopinerolo.org
>>>>>>> https://liszt.softwareliberopinerolo.org/listinfo/slip
>>>>>>>
>>>>>> --
>>>>> SLiP mailing list
>>>>> SLiP a liszt.softwareliberopinerolo.org
>>>>> https://liszt.softwareliberopinerolo.org/listinfo/slip
>>>>>
>>>> --
>>>> SLiP mailing list
>>>> SLiP a liszt.softwareliberopinerolo.org
>>>> https://liszt.softwareliberopinerolo.org/listinfo/slip
>>>>
>>> --
>>> SLiP mailing list
>>> SLiP a liszt.softwareliberopinerolo.org
>>> https://liszt.softwareliberopinerolo.org/listinfo/slip
>>>
>> --
>> SLiP mailing list
>> SLiP a liszt.softwareliberopinerolo.org
>> https://liszt.softwareliberopinerolo.org/listinfo/slip
>>
> --
> SLiP mailing list
> SLiP a liszt.softwareliberopinerolo.org
> https://liszt.softwareliberopinerolo.org/listinfo/slip
>
>
-------------- parte successiva --------------
Un allegato HTML è stato rimosso...
URL: <http://liszt.softwareliberopinerolo.org/pipermail/slip/attachments/20231228/1f0858e6/attachment-0001.htm>
Maggiori informazioni sulla lista
SLiP