KVM Ubuntu Guest IPV6 DHCP не работает

У меня есть сервер KVM, сидящий на сервере Debian.

Настройка сети через модель устройства Macvtap/ Bridge rtl8139

Я установил Ubuntu Server 18.10 без X.

/etc/netplan/50-cloud-init.yaml
network:
    version: 2
    ethernets:
        ens3:
            addresses:
            - 192.168.1.236/24
            dhcp4: false
            dhcp6: true
            gateway4: 192.168.1.1
            nameservers:
                addresses:
                - 1.1.1.1
                - 8.8.8.8
                - 8.8.4.4
                search:
                - jlbprof.com

IPV4 работает отлично, я могу пинговать мир, но ipv6 не так много

root@testing:/var/log# ping www.google.com
PING www.google.com(dfw25s17-in-x04.1e100.net (2607:f8b0:4000:804::2004)) 56 data bytes
^C
--- www.google.com ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 137ms

root@testing:/var/log# ifconfig
ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.236  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::5054:ff:fe6c:b320  prefixlen 64  scopeid 0x20<link>
        inet6 2601:2c1:8380:3b42:5054:ff:fe6c:b320  prefixlen 64  scopeid 0x0<global>
        inet6 2601:2c1:8380:3b42::83cf  prefixlen 128  scopeid 0x0<global>
        ether 52:54:00:6c:b3:20  txqueuelen 1000  (Ethernet)
        RX packets 808  bytes 462118 (462.1 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 359  bytes 79145 (79.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 1210

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  (Local Loopback)
        RX packets 114  bytes 8607 (8.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 114  bytes 8607 (8.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Из системного журнала:

/var/log/syslog
Dec 25 21:00:19 testing systemd[1]: Started Network Service.
Dec 25 21:00:19 testing systemd[1]: Starting Wait for Network to be Configured...
Dec 25 21:00:19 testing systemd[1]: Starting Network Name Resolution...
Dec 25 21:00:19 testing systemd-networkd[691]: ens3: Gained carrier
Dec 25 21:00:19 testing systemd-timesyncd[490]: Network configuration changed, trying to establish connection.
Dec 25 21:00:19 testing systemd-networkd-wait-online[723]: ignoring: lo
Dec 25 21:00:19 testing systemd-resolved[730]: Positive Trust Anchors:
Dec 25 21:00:19 testing systemd-resolved[730]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Dec 25 21:00:19 testing systemd-resolved[730]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Dec 25 21:00:19 testing systemd-resolved[730]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Dec 25 21:00:19 testing systemd-resolved[730]: Using system hostname 'testing'.
Dec 25 21:00:19 testing systemd[1]: Started Network Name Resolution.
Dec 25 21:00:19 testing systemd[1]: Reached target Network.
Dec 25 21:00:19 testing systemd[1]: Reached target Host and Network Name Lookups.
Dec 25 21:00:19 testing systemd-networkd[691]: ens3: Gained IPv6LL
Dec 25 21:00:19 testing systemd-timesyncd[490]: Network configuration changed, trying to establish connection.
Dec 25 21:00:19 testing systemd-networkd-wait-online[723]: ignoring: lo
Dec 25 21:00:19 testing systemd-networkd[691]: ens3: DHCPv6 address 2601:2c1:8380:3b42::83cf/128 timeout preferred 604800 valid 604800
Dec 25 21:00:19 testing systemd-networkd[691]: ens3: Configured
Dec 25 21:00:19 testing systemd-networkd-wait-online[723]: ignoring: lo
Dec 25 21:00:19 testing systemd-networkd-wait-online[723]: managing: ens3
Dec 25 21:00:19 testing systemd-timesyncd[490]: Network configuration changed, trying to establish connection.
Dec 25 21:00:19 testing systemd[1]: Started Wait for Network to be Configured.
Dec 25 21:00:19 testing systemd[1]: Starting Initial cloud-init job (metadata service crawler)...
Dec 25 21:00:19 testing cloud-init[756]: Cloud-init v. 18.4-7-g4652b196-0ubuntu1 running 'init' at Tue, 25 Dec 2018 21:00:17 +0000. Up 11.65 seconds.
Dec 25 21:00:19 testing cloud-init[756]: ci-info: ++++++++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++++++++
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +--------+------+-----------------------------------------+---------------+--------+-------------------+
Dec 25 21:00:19 testing cloud-init[756]: ci-info: | Device |  Up  |                 Address                 |      Mask     | Scope  |     Hw-Address    |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +--------+------+-----------------------------------------+---------------+--------+-------------------+
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |  ens3  | True |              192.168.1.236              | 255.255.255.0 | global | 52:54:00:6c:b3:20 |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |  ens3  | True |       2601:2c1:8380:3b42::83cf/128      |       .       | global | 52:54:00:6c:b3:20 |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |  ens3  | True | 2601:2c1:8380:3b42:5054:ff:fe6c:b320/64 |       .       | global | 52:54:00:6c:b3:20 |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |  ens3  | True |        fe80::5054:ff:fe6c:b320/64       |       .       |  link  | 52:54:00:6c:b3:20 |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   lo   | True |                127.0.0.1                |   255.0.0.0   |  host  |         .         |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   lo   | True |                 ::1/128                 |       .       |  host  |         .         |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +--------+------+-----------------------------------------+---------------+--------+-------------------+
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +-------+-------------+-------------+---------------+-----------+-------+
Dec 25 21:00:19 testing cloud-init[756]: ci-info: | Route | Destination |   Gateway   |    Genmask    | Interface | Flags |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +-------+-------------+-------------+---------------+-----------+-------+
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   0   |   0.0.0.0   | 192.168.1.1 |    0.0.0.0    |    ens3   |   UG  |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   1   | 192.168.1.0 |   0.0.0.0   | 255.255.255.0 |    ens3   |   U   |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +-------+-------------+-------------+---------------+-----------+-------+
Dec 25 21:00:19 testing cloud-init[756]: ci-info: ++++++++++++++++++++++++++++++++++Route IPv6 info++++++++++++++++++++++++++++++++++
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +-------+-------------------------+---------------------------+-----------+-------+
Dec 25 21:00:19 testing cloud-init[756]: ci-info: | Route |       Destination       |          Gateway          | Interface | Flags |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +-------+-------------------------+---------------------------+-----------+-------+
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   1   | 2601:2c1:8380:3b42::/64 |             ::            |    ens3   |   Ue  |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   2   |        fe80::/64        |             ::            |    ens3   |   U   |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   3   |           ::/0          | fe80::5e8f:e0ff:fe41:4957 |    ens3   |  UGe  |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   4   |           ::/0          | fe80::5e8f:e0ff:fe41:4957 |    ens3   |  UGe  |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   6   |          local          |             ::            |    ens3   |   U   |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   7   |          local          |             ::            |    ens3   |   U   |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   8   |          local          |             ::            |    ens3   |   U   |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: |   9   |         ff00::/8        |             ::            |    ens3   |   U   |
Dec 25 21:00:19 testing cloud-init[756]: ci-info: +-------+-------------------------+---------------------------+-----------+-------+
Dec 25 21:00:19 testing systemd[1]: Started Initial cloud-init job (metadata service crawler).
Dec 25 21:00:19 testing systemd[1]: Reached target System Initialization.

Здесь я могу пинговать шлюз настройки

root@testing:/var/log# ping fe80::5e8f:e0ff:fe41:4957
PING fe80::5e8f:e0ff:fe41:4957(fe80::5e8f:e0ff:fe41:4957) 56 data bytes
64 bytes from fe80::5e8f:e0ff:fe41:4957%ens3: icmp_seq=1 ttl=64 time=3.10 ms
64 bytes from fe80::5e8f:e0ff:fe41:4957%ens3: icmp_seq=2 ttl=64 time=2.49 ms
64 bytes from fe80::5e8f:e0ff:fe41:4957%ens3: icmp_seq=3 ttl=64 time=2.09 ms
^C
--- fe80::5e8f:e0ff:fe41:4957 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 2.090/2.557/3.097/0.418 ms
root@testing:/var/log# ping www.google.com
PING www.google.com(dfw25s26-in-x04.1e100.net (2607:f8b0:4000:813::2004)) 56 data bytes
^C
--- www.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 31ms

У меня есть другие настройки VM, которые отлично работают, если я ничего не делаю с конфигом (где все по умолчанию, я полагаю, dhcp4 и 6), но netplan в основном и пустой файл.

Что не так с моей настройкой IPV6?

Thanx

Bodger

0 ответов

Другие вопросы по тегам