=== akp55_ is now known as akp55__
=== Kamilion|ZNC is now known as Kamilion
[09:18] <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> @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 betreten
[10:07] <egon96> [11:02:10 AM] → slyon hat den Raum betreten
[10:15] <slyon> egon96: oh I must have missed that. what do you mean by "reduced connectivity"? How does you netplan YAML look like?
[10:25] <egon96> This is my netplan:network:
[10:25] <egon96>   version: 2
[10:25] <egon96>   renderer: NetworkManager
[10: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.1
[10:25] <egon96>       gateway6: fe80::1
[10:25] <egon96>       nameservers:
[10:25] <egon96>         addresses: [85.214.20.141]
[10:26] <egon96> And this the nmcli message in german:thomas@thomasKVM:~$ nmcli general
[10:26] <egon96> STATE                    CONNECTIVITY  WIFI-HW    WIFI       WWAN-HW    WWAN
[10:26] <egon96> verbunden (nur Gelände)  begrenzt      aktiviert  aktiviert  aktiviert  aktiviert
[10:26] <egon96> thomas@thomasKVM:~$
[10:28] <egon96> ping ipv4 functions, ping6 ipv6 gets no answers
[10:32] <slyon> according 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:33] <slyon> is fe80::1 an actual IP6 gateway? that IP looks odd to me... its a link-local address, but not derived from a MAC.
[10:37] <slyon> did you assing this IP to your routers interfaces manually/statically?
[10:38] <slyon> can you ping6 fe80::1?
[10:40] <egon96> no
[10:42] <egon96> The gateway address is told me from my vserver's provider
[10:44] <slyon> okay. 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:45] <slyon> You might be able to force this by using netplan's "link-local: [ ipv6 ]" setting
[10:45] <slyon> maybe you can't ping the gateway because there is not link-local address assigned to ens3
[11:06] <egon66> My laptop lost power so I am disrupted. I have to restore my environment
[11:06] <slyon> re posting my last messages:
[11:06] <slyon> okay. 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] <slyon> You might be able to force this by using netplan's "link-local: [ ipv6 ]" setting
[11:06] <slyon> maybe you can't ping the gateway because there is not link-local address assigned to ens3
[11:41] <egon66> thomas@thomasKVM:~$ ip a ens3
[11:41] <egon66> Command "ens3" is unknown, try "ip address help".
[11:41] <egon66> thomas@thomasKVM:~$ ip addr ens3
[11:41] <egon66> Command "ens3" is unknown, try "ip address help".
[11:41] <egon66> thomas@thomasKVM:~$ nmcli dev show
[11:41] <egon66> GENERAL.DEVICE:                         ens3
[11:41] <egon66> GENERAL.TYPE:                           ethernet
[11:41] <egon66> GENERAL.HWADDR:                         86:67:B6:38:68:99
[11:41] <egon66> GENERAL.MTU:                            1500
[11:41] <egon66> GENERAL.STATE:                          100 (verbunden)
[11:41] <egon66> GENERAL.CONNECTION:                     netplan-ens3
[11:41] <egon66> GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveC>
[11:41] <egon66> WIRED-PROPERTIES.CARRIER:               an
[11:41] <egon66> IP4.ADDRESS[1]:                         37.120.185.29/22
[11:41] <egon66> IP4.GATEWAY:                            37.120.184.1
[11:41] <egon66> IP4.ROUTE[1]:                           dst = 37.120.184.0/22, nh = 0.0.0.0, mt>
[11:41] <egon66> IP4.ROUTE[2]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt >
[11:41] <egon66> IP4.ROUTE[3]:                           dst = 0.0.0.0/0, nh = 37.120.184.1, mt >
[11:41] <egon66> IP4.GATEWAY:                            37.120.184.1
[11:41] <egon66> IP4.ROUTE[1]:                           dst = 37.120.184.0/22, nh = 0.0.0.0, mt>
[11:41] <egon66> IP4.ROUTE[2]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt >
[11:41] <egon66> IP4.ROUTE[3]:                           dst = 0.0.0.0/0, nh = 37.120.184.1, mt >
[11:41] <egon66> IP4.DNS[1]:                             85.214.20.141
[11:41] <egon66> IP6.ADDRESS[1]:                         2a03:4000:f:786::2/64
[11:41] <egon66> IP6.ADDRESS[2]:                         2a03:4000:f:786::a/64
[11:41] <egon66> IP6.ADDRESS[3]:                         fe80::8467:b6ff:fe38:6899/64
[11:41] <egon66> IP6.GATEWAY:                            fe80::1
[11:41] <egon66> IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 100
[11:41] <egon66> IP6.ROUTE[2]:                           dst = 2a03:4000:f:786::/64, nh = ::, mt>
[11:41] <egon66> IP6.ROUTE[3]:                           dst = fe80::1/128, nh = ::, mt = 20100
[11:41] <egon66> IP6.ROUTE[4]:                           dst = ff00::/8, nh = ::, mt = 256, tabl>
[11:41] <egon66> IP6.ROUTE[5]:                           dst = ::/0, nh = fe80::1, mt = 20100
[11:41] <egon66> GENERAL.DEVICE:                         lo
[11:41] <egon66> GENERAL.TYPE:                           loopback
[11:41] <egon66> GENERAL.HWADDR:                         00:00:00:00:00:00
[11:41] <egon66> GENERAL.MTU:                            65536
[11:52] <slyon> well 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..
[12:02] <slyon> does this work: ping6 fe80::1%ens3 ?
=== akp55_ is now known as akp55__
=== akp55__ is now known as akp55
[13:56] <egon66> yes, it works:
[13:56] <egon66> thomas@thomasKVM:~$ ping6 fe80::1%ens3
[13:56] <egon66> PING fe80::1%ens3(fe80::1%ens3) 56 Datenbytes
[13:56] <egon66> 64 Bytes von fe80::1%ens3: icmp_seq=1 ttl=64 Zeit=0.472 ms
[13:56] <egon66> 64 Bytes von fe80::1%ens3: icmp_seq=2 ttl=64 Zeit=1.02 ms
[13:56] <egon66> 64 Bytes von fe80::1%ens3: icmp_seq=3 ttl=64 Zeit=14.9 ms
[13:56] <egon66> 64 Bytes von fe80::1%ens3: icmp_seq=4 ttl=64 Zeit=0.361 ms
[13:56] <egon66> 64 Bytes von fe80::1%ens3: icmp_seq=5 ttl=64 Zeit=0.507 ms
[13:56] <egon66> 64 Bytes von fe80::1%ens3: icmp_seq=6 ttl=64 Zeit=0.624 ms
[13:56] <egon66> 64 Bytes von fe80::1%ens3: icmp_seq=7 ttl=64 Zeit=0.516 ms
[13:56] <egon66> 64 Bytes von fe80::1%ens3: icmp_seq=8 ttl=64 Zeit=0.409 ms
[13:56] <egon66> ^C
[13:56] <egon66> --- fe80::1%ens3 ping statistics ---
[13:56] <egon66> 8 Pakete übertragen, 8 empfangen, 0% Paketverlust, Zeit 7111ms
[13:56] <egon66> rtt min/avg/max/mdev = 0.361/2.347/14.869/4.736 ms
[13:56] <egon66> thomas@thomasKVM:~$
[15:19] <egon66> slyon (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] <slyon> egon66: ah! that's good news. It means the gateway6 is working
[15:20] <slyon> I'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:21] <slyon> maybe it's a DNS issue after all, as there is not IPv6 DNS in you netplan config
[15:25] <egon66> ping6 with google-address say there is no service. Yes, this should be a nameserver problem.
[15:28] <slyon> what is the exact error message? If you cannot ping, then is must be something else than DNS, no?
[15:33] <egon66> The message:
[15:33] <egon66> thomas@thomasKVM:~$ ping6 2001:4860:4860:8888
[15:33] <egon66> ping6: 2001:4860:4860:8888: Der Name oder der Dienst ist nicht bekannt
[15:33] <egon66> thomas@thomasKVM:~$ ^C
[15:33] <egon66> thomas@thomasKVM:~$
[15:34] <egon66> Should I have a line with nameservers6 or so?
[15:35] <slyon> I have two ideas:
[15:35] <slyon> 1) define "gateway6: fe80::1%ens3" (not sure if this is supported by netplan)
[15:35] <slyon> 2) add "2001:4860:4860:8888" to the list of nameservers.addresses
[15:37] <egon66> I"ll try your ideas. Then you "ll hear from me. Thanks!
[15:58] <egon66> Second idea: I get:
[15:59] <egon66> Error in network definition: malformed address '2001:4860:4860:8888', must be X.X.X.X or X:X:X:X:X:X:X:X
[15:59] <egon66>         addresses: [85.214.20.141, "2001:4860:4860:8888"]
[16:12] <slyon> sorry, the google DNS is "2001:4860:4860::8888" (note the :: there)
[16:23] <egon66> This ping is correct.
[16:24] <egon66> But now the other way.
[16:25] <egon66> thomas@Epsil192:~$ ping6 2a03:4000:f:786::2
[16:25] <egon66> PING 2a03:4000:f:786::2(2a03:4000:f:786::2) 56 Datenbytes
[16:25] <egon66> ^C
[16:25] <egon66> --- 2a03:4000:f:786::2 ping statistics ---
[16:25] <egon66> 5 Pakete übertragen, 0 empfangen, 100% Paketverlust, Zeit 4095ms
[16:25] <egon66> thomas@Epsil192:~$
[16:25] <egon66> (This is the address of thomasKVM in netplan.)
[17:25] <egon66> quit
[17:26] <egon66> exit
[17:26] <egon66> leave
=== 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