Guten Tag,
da im CCP stand man solle den Server mal powercyclen wegen KVM habe ich dies heute getan und bin auf ein Problem mit meinem IPv6 Setup gestoßen, was ich davor noch nicht hatte:
- Eingehend IPv6 geht (Server pingen von außen zum Beispiel)
- Ausgehend IPv6 geht nicht (ping google.de 100% Packet loss)
Meine Vorgabe von SCP:
Screenshot_2020-10-26 SCP - network interfaces (box2 bebna de).png
Ping von dritter Seite:
Screenshot_2020-10-26 IPv6 Ping IPv6 Now.png
Meine systemd-networkd config:
Code
[Match]
Name=eth0
[Network]
DHCP=no
DNS=46.38.225.230
DNS=46.38.252.230
DNS=2a03:4000:8000::fce6
DNS=2a03:4000:0:1::e1e6
Address=185.163.119.60/22
Gateway=185.163.116.1
Address=2a03:4000:3b:5cf::1/64
Gateway=fe80::1Debug Konsolen Ausgaben:
Code
❯ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether ba:d5:1d:a4:dc:0d brd ff:ff:ff:ff:ff:ff
altname enp0s3
altname ens3
inet 185.163.119.60/22 brd 185.163.119.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 2a03:4000:3b:5cf::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::b8d5:1dff:fea4:dc0d/64 scope link
valid_lft forever preferred_lft forever
❯ ip -6 r
::1 dev lo proto kernel metric 256 pref medium
2a03:4000:3b:5cf::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fe80::1 dev eth0 proto ra metric 1024 pref medium
❯ networkctl status eth0
● 2: eth0
Link File: /usr/lib/systemd/network/99-default.link
Network File: /etc/systemd/network/40-static.network
Type: ether
State: routable (configured)
Alternative Names: enp0s3
ens3
Path: pci-0000:00:03.0
Driver: virtio_net
Vendor: Red Hat, Inc.
Model: Virtio network device
HW Address: ba:d5:1d:a4:dc:0d
MTU: 1500 (min: 68, max: 65535)
QDisc: fq_codel
IPv6 Address Generation Mode: eui64
Queue Length (Tx/Rx): 1/1
Auto negotiation: no
Speed: n/a
Address: 185.163.119.60
2a03:4000:3b:5cf::1
fe80::b8d5:1dff:fea4:dc0d
Gateway: 185.163.116.1 (ICANN, IANA Department)
fe80::1 (ICANN, IANA Department)
DNS: 46.38.225.230
46.38.252.230
2a03:4000:8000::fce6
2a03:4000:0:1::e1e6
DHCP6 Client DUID: DUID-EN/Vendor:0000ab11663c881fb84022cd0000
Oct 26 13:25:22 v2202008127202124967 systemd-networkd[17266]: eth0: IPv6 successfully enabled
Oct 26 13:25:35 v2202008127202124967 systemd-networkd[17266]: eth0: Re-configuring with /etc/systemd/network/40-static.network
Oct 26 13:25:35 v2202008127202124967 systemd-networkd[17266]: eth0: DHCPv6 lease lost
Oct 26 13:25:35 v2202008127202124967 systemd-networkd[17266]: eth0: IPv6 successfully enabled
Oct 26 13:26:38 v2202008127202124967 systemd-networkd[17266]: eth0: Re-configuring with /etc/systemd/network/40-static.network
Oct 26 13:26:38 v2202008127202124967 systemd-networkd[17266]: eth0: DHCPv6 lease lost
Oct 26 13:26:38 v2202008127202124967 systemd-networkd[17266]: eth0: IPv6 successfully enabled
Oct 26 13:26:42 v2202008127202124967 systemd-networkd[17266]: eth0: Re-configuring with /etc/systemd/network/40-static.network
Oct 26 13:26:42 v2202008127202124967 systemd-networkd[17266]: eth0: DHCPv6 lease lost
Oct 26 13:26:42 v2202008127202124967 systemd-networkd[17266]: eth0: IPv6 successfully enabled
❯ ping google.de
PING google.de(fra16s20-in-x03.1e100.net (2a00:1450:4001:821::2003)) 56 data bytes
^C
--- google.de ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1014ms
❯ ping 2a03:4000:0:1::e1e6
PING 2a03:4000:0:1::e1e6(2a03:4000:0:1::e1e6) 56 data bytes
^C
--- 2a03:4000:0:1::e1e6 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2028ms
❯ tracepath 2a03:4000:0:1::e1e6
1?: [LOCALHOST] 0.023ms pmtu 1500
1: 2a03:4000:3b::2 0.488ms
1: 2a03:4000:3b::2 0.283ms
2: no reply
3: no reply
4: no reply
5: no reply
6: no reply
^C
❯ ping 2a03:4000:3b:5cf::1
PING 2a03:4000:3b:5cf::1(2a03:4000:3b:5cf::1) 56 data bytes
64 bytes from 2a03:4000:3b:5cf::1: icmp_seq=1 ttl=64 time=0.080 ms
64 bytes from 2a03:4000:3b:5cf::1: icmp_seq=2 ttl=64 time=0.062 ms
^C
--- 2a03:4000:3b:5cf::1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1019ms
rtt min/avg/max/mdev = 0.062/0.071/0.080/0.009 msEs ging definitiv davor, denn erst nach dem powercycle hat er die ipv4 Addresse von gitlab bei einem git push zu den known hosts hinzugefügt, nachdem er bei ipv6 in den Timeout lief.
Ich seh leider nicht was falsch ist, ich hoffe Ihr seht den Fehler. Danke.
