/srv/irclogs.ubuntu.com/2021/01/29/#netplan.txt

=== akp55_ is now known as akp55__
=== Kamilion|ZNC is now known as Kamilion
egon96nmcli general shows reduced connectivity but my netplan has ip4v and ipv6 addreses. Why is the connectivity reduced to LAN? (But I have ssh connections)09:18
egon96@sil2100 @slyon I asked: [10:18:40 AM] <egon96> nmcli general shows reduced connectivity but my netplan has ip4v and ipv6 addreses. Why is the connectivity reduced to LAN? (But I have ssh connections)10:07
egon96[10:53:05 AM] → sil2100 hat den Raum betreten10:07
egon96[11:02:10 AM] → slyon hat den Raum betreten10:07
slyonegon96: oh I must have missed that. what do you mean by "reduced connectivity"? How does you netplan YAML look like?10:15
egon96This is my netplan:network:10:25
egon96  version: 210:25
egon96  renderer: NetworkManager10:25
egon96  ethernets:10:25
egon96    ens3:10:25
egon96      addresses: [37.120.185.29/22, "2a03:4000:f:786::2/64","2a03:4000:f:786::a/64"]10:25
egon96      gateway4: 37.120.184.110:25
egon96      gateway6: fe80::110:25
egon96      nameservers:10:25
egon96        addresses: [85.214.20.141]10:25
egon96And this the nmcli message in german:thomas@thomasKVM:~$ nmcli general10:26
egon96STATE                    CONNECTIVITY  WIFI-HW    WIFI       WWAN-HW    WWAN10:26
egon96verbunden (nur Gelände)  begrenzt      aktiviert  aktiviert  aktiviert  aktiviert10:26
egon96thomas@thomasKVM:~$10:26
egon96ping ipv4 functions, ping6 ipv6 gets no answers10:28
slyonaccording to nmcli's manpage the "CONNECTIVITY: begrenzt" (i.e. "limited") means: "the host is connected to a network, but it has no access to the Internet."10:32
slyonis fe80::1 an actual IP6 gateway? that IP looks odd to me... its a link-local address, but not derived from a MAC.10:33
slyondid you assing this IP to your routers interfaces manually/statically?10:37
slyoncan you ping6 fe80::1?10:38
egon96no10:40
egon96The gateway address is told me from my vserver's provider10:42
slyonokay. Can you show the output of "nmcli dev ens3" and or "ip addr ens3"? To check if you have a link-local IP6 assigned to your interface?10:44
slyonYou might be able to force this by using netplan's "link-local: [ ipv6 ]" setting10:45
slyonmaybe you can't ping the gateway because there is not link-local address assigned to ens310:45
egon66My laptop lost power so I am disrupted. I have to restore my environment11:06
slyonre posting my last messages:11:06
slyonokay. Can you show the output of "nmcli dev ens3" and or "ip addr ens3"? To check if you have a link-local IP6 assigned to your interface?11:06
slyonYou might be able to force this by using netplan's "link-local: [ ipv6 ]" setting11:06
slyonmaybe you can't ping the gateway because there is not link-local address assigned to ens311:06
egon66thomas@thomasKVM:~$ ip a ens311:41
egon66Command "ens3" is unknown, try "ip address help".11:41
egon66thomas@thomasKVM:~$ ip addr ens311:41
egon66Command "ens3" is unknown, try "ip address help".11:41
egon66thomas@thomasKVM:~$ nmcli dev show11:41
egon66GENERAL.DEVICE:                         ens311:41
egon66GENERAL.TYPE:                           ethernet11:41
egon66GENERAL.HWADDR:                         86:67:B6:38:68:9911:41
egon66GENERAL.MTU:                            150011:41
egon66GENERAL.STATE:                          100 (verbunden)11:41
egon66GENERAL.CONNECTION:                     netplan-ens311:41
egon66GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveC>11:41
egon66WIRED-PROPERTIES.CARRIER:               an11:41
egon66IP4.ADDRESS[1]:                         37.120.185.29/2211:41
egon66IP4.GATEWAY:                            37.120.184.111:41
egon66IP4.ROUTE[1]:                           dst = 37.120.184.0/22, nh = 0.0.0.0, mt>11:41
egon66IP4.ROUTE[2]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt >11:41
egon66IP4.ROUTE[3]:                           dst = 0.0.0.0/0, nh = 37.120.184.1, mt >11:41
egon66IP4.GATEWAY:                            37.120.184.111:41
egon66IP4.ROUTE[1]:                           dst = 37.120.184.0/22, nh = 0.0.0.0, mt>11:41
egon66IP4.ROUTE[2]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt >11:41
egon66IP4.ROUTE[3]:                           dst = 0.0.0.0/0, nh = 37.120.184.1, mt >11:41
egon66IP4.DNS[1]:                             85.214.20.14111:41
egon66IP6.ADDRESS[1]:                         2a03:4000:f:786::2/6411:41
egon66IP6.ADDRESS[2]:                         2a03:4000:f:786::a/6411:41
egon66IP6.ADDRESS[3]:                         fe80::8467:b6ff:fe38:6899/6411:41
egon66IP6.GATEWAY:                            fe80::111:41
egon66IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 10011:41
egon66IP6.ROUTE[2]:                           dst = 2a03:4000:f:786::/64, nh = ::, mt>11:41
egon66IP6.ROUTE[3]:                           dst = fe80::1/128, nh = ::, mt = 2010011:41
egon66IP6.ROUTE[4]:                           dst = ff00::/8, nh = ::, mt = 256, tabl>11:41
egon66IP6.ROUTE[5]:                           dst = ::/0, nh = fe80::1, mt = 2010011:41
egon66GENERAL.DEVICE:                         lo11:41
egon66GENERAL.TYPE:                           loopback11:41
egon66GENERAL.HWADDR:                         00:00:00:00:00:0011:41
egon66GENERAL.MTU:                            6553611:41
slyonwell it looks like you have an actual ipv6 link-local address: fe80::8467:b6ff:fe38:6899/64. You should be able to ping your gateway (fe80::1) then, if that exists..11:52
slyondoes this work: ping6 fe80::1%ens3 ?12:02
=== akp55_ is now known as akp55__
=== akp55__ is now known as akp55
egon66yes, it works:13:56
egon66thomas@thomasKVM:~$ ping6 fe80::1%ens313:56
egon66PING fe80::1%ens3(fe80::1%ens3) 56 Datenbytes13:56
egon6664 Bytes von fe80::1%ens3: icmp_seq=1 ttl=64 Zeit=0.472 ms13:56
egon6664 Bytes von fe80::1%ens3: icmp_seq=2 ttl=64 Zeit=1.02 ms13:56
egon6664 Bytes von fe80::1%ens3: icmp_seq=3 ttl=64 Zeit=14.9 ms13:56
egon6664 Bytes von fe80::1%ens3: icmp_seq=4 ttl=64 Zeit=0.361 ms13:56
egon6664 Bytes von fe80::1%ens3: icmp_seq=5 ttl=64 Zeit=0.507 ms13:56
egon6664 Bytes von fe80::1%ens3: icmp_seq=6 ttl=64 Zeit=0.624 ms13:56
egon6664 Bytes von fe80::1%ens3: icmp_seq=7 ttl=64 Zeit=0.516 ms13:56
egon6664 Bytes von fe80::1%ens3: icmp_seq=8 ttl=64 Zeit=0.409 ms13:56
egon66^C13:56
egon66--- fe80::1%ens3 ping statistics ---13:56
egon668 Pakete übertragen, 8 empfangen, 0% Paketverlust, Zeit 7111ms13:56
egon66rtt min/avg/max/mdev = 0.361/2.347/14.869/4.736 ms13:56
egon66thomas@thomasKVM:~$13:56
egon66slyon (I had  to do other things.) Have you seen my message that ping6 with %ens3 works? What does that mean? What should I do? (In netplan?)15:19
slyonegon66: ah! that's good news. It means the gateway6 is working15:19
slyonI'm still wondering why it can't reach the internet though... can you "ping6 2001:4860:4860::8888" (i.e. the IPv6 google DNS)15:20
slyonmaybe it's a DNS issue after all, as there is not IPv6 DNS in you netplan config15:21
egon66ping6 with google-address say there is no service. Yes, this should be a nameserver problem.15:25
slyonwhat is the exact error message? If you cannot ping, then is must be something else than DNS, no?15:28
egon66The message:15:33
egon66thomas@thomasKVM:~$ ping6 2001:4860:4860:888815:33
egon66ping6: 2001:4860:4860:8888: Der Name oder der Dienst ist nicht bekannt15:33
egon66thomas@thomasKVM:~$ ^C15:33
egon66thomas@thomasKVM:~$15:33
egon66Should I have a line with nameservers6 or so?15:34
slyonI have two ideas:15:35
slyon1) define "gateway6: fe80::1%ens3" (not sure if this is supported by netplan)15:35
slyon2) add "2001:4860:4860:8888" to the list of nameservers.addresses15:35
egon66I"ll try your ideas. Then you "ll hear from me. Thanks!15:37
egon66Second idea: I get:15:58
egon66Error in network definition: malformed address '2001:4860:4860:8888', must be X.X.X.X or X:X:X:X:X:X:X:X15:59
egon66        addresses: [85.214.20.141, "2001:4860:4860:8888"]15:59
slyonsorry, the google DNS is "2001:4860:4860::8888" (note the :: there)16:12
egon66This ping is correct.16:23
egon66But now the other way.16:24
egon66thomas@Epsil192:~$ ping6 2a03:4000:f:786::216:25
egon66PING 2a03:4000:f:786::2(2a03:4000:f:786::2) 56 Datenbytes16:25
egon66^C16:25
egon66--- 2a03:4000:f:786::2 ping statistics ---16:25
egon665 Pakete übertragen, 0 empfangen, 100% Paketverlust, Zeit 4095ms16:25
egon66thomas@Epsil192:~$16:25
egon66(This is the address of thomasKVM in netplan.)16:25
egon66quit17:25
egon66exit17:26
egon66leave17:26
=== King_InuYasha is now known as Conan_Kudo
=== Conan_Kudo is now known as King_InuYasha
=== King_InuYasha is now known as Conan_Kudo
=== Conan_Kudo is now known as King_InuYasha

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!