reox hat geschrieben: 22.08.2021 10:32:54
Hast du net.ipv6.conf.all.forwarding=1 in sysctl gesetzt?
Kannst du aus der VM fe80::5054:ff:fefb:7846 pingen?
was macht ein ping6 ff02::2 bzw ping6 ff02::1 (pinge alle router bzw alle hosts)?
Punkt 1 ist von Anfang an gesetzt.
Punkt 2 funktioniert auch
Code: Alles auswählen
# ping6 fe80::5054:ff:fefb:7846
PING fe80::5054:ff:fefb:7846(fe80::5054:ff:fefb:7846) 56 data bytes
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=1 ttl=64 time=0.192 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=2 ttl=64 time=0.251 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=3 ttl=64 time=0.260 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=4 ttl=64 time=0.249 ms
Punkt 3 ebenfalls
Code: Alles auswählen
root@mx ~ # ping6 ff02::2
PING ff02::2(ff02::2) 56 data bytes
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=1 ttl=64 time=0.099 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=2 ttl=64 time=0.273 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=3 ttl=64 time=0.267 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=4 ttl=64 time=0.272 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=5 ttl=64 time=0.252 ms
^C
--- ff02::2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 77ms
rtt min/avg/max/mdev = 0.099/0.232/0.273/0.069 ms
root@mx ~ # ping6 ff02::1
PING ff02::1(ff02::1) 56 data bytes
64 bytes from fe80::5054:ff:fe38:a916%enp1s0: icmp_seq=1 ttl=64 time=0.061 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=1 ttl=64 time=0.320 ms (DUP!)
64 bytes from fe80::5054:ff:fe38:a916%enp1s0: icmp_seq=2 ttl=64 time=0.070 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=2 ttl=64 time=0.374 ms (DUP!)
64 bytes from fe80::5054:ff:fe38:a916%enp1s0: icmp_seq=3 ttl=64 time=0.071 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=3 ttl=64 time=0.374 ms (DUP!)
64 bytes from fe80::5054:ff:fe38:a916%enp1s0: icmp_seq=4 ttl=64 time=0.069 ms
64 bytes from fe80::5054:ff:fefb:7846%enp1s0: icmp_seq=4 ttl=64 time=0.285 ms (DUP!)
^C
--- ff02::1 ping statistics ---
4 packets transmitted, 4 received, +4 duplicates, 0% packet loss, time 78ms
rtt min/avg/max/mdev = 0.061/0.203/0.374/0.137 ms
Dieser Ping bleibt so hängen
Code: Alles auswählen
root@mx ~ # ping6 www.google.com
PING www.google.com(fra02s19-in-x04.1e100.net (2a00:1450:4001:808::2004)) 56 data bytes
Das geht allerdings auch, der hat aber auch keinen AAAA-Record sondern nur A:
Code: Alles auswählen
root@mx ~ # ping www.lihas.de
PING www.lihas.de (45.150.154.30) 56(84) bytes of data.
64 bytes from rproxy.lihas.de (45.150.154.30): icmp_seq=1 ttl=53 time=5.96 ms
64 bytes from rproxy.lihas.de (45.150.154.30): icmp_seq=2 ttl=53 time=6.21 ms
64 bytes from rproxy.lihas.de (45.150.154.30): icmp_seq=3 ttl=53 time=6.25 ms
64 bytes from rproxy.lihas.de (45.150.154.30): icmp_seq=4 ttl=53 time=6.19 ms
^C
--- www.lihas.de ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 5.959/6.151/6.246/0.112 ms
Was bei der Interfaces auf dem Host bei virbr0 (weil über libvirt konfiguiert) fehlt, sind diese 3 Optionen
Code: Alles auswählen
bridge_stp off # disable Spanning Tree Protocol
bridge_waitport 0 # no delay before a port becomes available
bridge_fd 0 # no forwarding delay
die im Bridge-Modus die vmbr0 erhält.