Was soll ich sagen:
Ich habe die Route gerade eben gelöscht und sicherheitshalber die OPNsense neu gestartet.
Nun funktionert auch der IPv6-Zugriff nach außen von der VM über die OPNsense.
Ich hatte zuvor allerdings mit einigen Routen gearbeitet und sicherlich habe ich die von dir benannte Route dort liegen lassen.
Ganz herzlichen Dank an dieser Stelle für die Hilfe.
Ich werde mir deine Tipps zu Herzen nehmen, schon jetzt habe ich wieder dazu gelernt. 
- Was passiert, wenn man auf der OpenSense Pings auf lokale oder entfernte Adressen absetzt?
ping google.de
PING6(56=40+8+8 bytes) X --> X
16 bytes from X, icmp_seq=0 hlim=119 time=3.827 ms
16 bytes from X, icmp_seq=1 hlim=119 time=3.710 ms
ping -4 google.de
PING google.de (X): 56 data bytes
64 bytes from X: icmp_seq=0 ttl=119 time=3.719 ms
64 bytes from X: icmp_seq=1 ttl=119 time=3.804 ms
ping X
PING6(56=40+8+8 bytes) X --> X
16 bytes from X, icmp_seq=0 hlim=64 time=0.113 ms
16 bytes from X, icmp_seq=1 hlim=64 time=0.091 ms
ping X
PING6(56=40+8+8 bytes) X --> X
^C
--- X ping6 statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
- wie sind die IP-Adressen verteilt auf die Interfaces?
LAN (vtnet1) -> v4: X/24
v6: X/64
WAN (vtnet0) -> v4: X/23
v6: X/64
Ja, das hab ich erwartet. Die neighbor solicitation kommt an, aber es gibt keine Antwort darauf. Entweder fühlt sich die OpenSense nicht angesprochen, oder sie schickt die Antwort an ein anderes Interface.
Das war meine Eingangsvermutung, dass hier eine Route gesetzt werden muss.
- Gibt es sowas wie Policy Based Routing?
Nein
- Welche Routen mit welcher Metric sind eingerichtet?
Bei IPv6 sind es diese lt. OPNsense (Weboberfläche)
| ipv6 | X:/64 | link#1 | U | NaN | 1500 | vtnet0 | wan |
| ipv6 | X | link#1 | UHS | NaN | 16384 | lo0 | Loopback | ||
| ipv6 | X | link#2 | UHS | NaN | 16384 | lo0 | Loopback | ||
| ipv6 | fe80::%vtnet0/64 | link#1 | U | NaN | 1500 | vtnet0 | wan | ||
| ipv6 | fe80::4872:c7ff:fe6f:ddc5%vtnet0 | link#1 | UHS | NaN | 16384 | lo0 | Loopback | ||
| ipv6 | fe80::%vtnet1/64 | link#2 | U | NaN | 1500 | vtnet1 | LAN | ||
| ipv6 | fe80::4872:c7ff:fe6f:ddc6%vtnet1 | link#2 | UHS | NaN | 16384 | lo0 | Loopback | ||
| ipv6 | fe80::%lo0/64 | link#4 | U | NaN | 16384 | lo0 | Loopback | ||
| ipv6 | fe80::1%lo0 | link#4 | UHS | NaN | 16384 | lo0 | Loopback |
Also nochmal, die Anonymisierung lasse ich jetzt weg ...
VM -> OPNsense:
a) tcpdump OPNsense
tcpdump -i vtnet1 -n icmp6
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vtnet1, link-type EN10MB (Ethernet), capture size 262144 bytes
19:22:55.279305 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:22:56.285342 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:22:57.309299 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:22:58.333569 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:22:59.357336 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:23:00.381284 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:23:01.405423 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:23:02.429293 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:23:03.453318 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
^C
9 packets captured
282 packets received by filter
0 packets dropped by kernel
b) tcpdump VM
tcpdump -i ens4 -n icmp6
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on ens4, link-type EN10MB (Ethernet), snapshot length 262144 bytes
19:22:55.281995 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:22:56.287933 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:22:57.311928 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:22:58.336116 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:22:59.359932 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:23:00.383951 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:23:01.408070 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
19:23:02.431922 IP6 2a03:4000:20:275:185:243:10:229 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:20:275::1, length 32
^C
8 packets captured
8 packets received by filter
0 packets dropped by kernel
Also nochmal:
-> OPNsense
tcpdump -n icmp6
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vtnet0, link-type EN10MB (Ethernet), capture size 262144 bytes
th 32
19:10:05.311682 IP6 fe80::4872:c7ff:fe6f:ddc5 > fe80::1: ICMP6, echo request, seq 9112, length 8
19:10:05.314569 IP6 fe80::1 > fe80::4872:c7ff:fe6f:ddc5: ICMP6, echo reply, seq 9112, length 8
19:10:05.528617 IP6 2a03:4000:2:c1e::1 > ff02::1:ff00:6: ICMP6, neighbor solicitation, who has fe80::6, length 32
19:10:05.801800 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:8:56f::1, length 32
19:10:05.801934 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:b:f9::1, length 32
19:10:06.327767 IP6 fe80::4872:c7ff:fe6f:ddc5 > fe80::1: ICMP6, echo request, seq 9113, length 8
19:10:06.336234 IP6 fe80::1 > fe80::4872:c7ff:fe6f:ddc5: ICMP6, echo reply, seq 9113, length 8
19:10:06.811397 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:b:f9::1, length 32
19:10:06.811530 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:8:56f::1, length 32
19:10:06.812311 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff31:e215: ICMP6, neighbor solicitation, who has 2a03:4000:7:122:d8ad:edff:fe31:e215, length 32
19:10:06.813669 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff00:3: ICMP6, neighbor solicitation, who has 2a03:4000:2:4ee::3, length 32
19:10:06.813977 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff05:56f7: ICMP6, neighbor solicitation, who has 2a03:4000:9:91:788a:b3ff:fe05:56f7, length 32
19:10:06.814286 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ffe6:5381: ICMP6, neighbor solicitation, who has 2a03:4000:2:4c7:5054:43ff:fee6:5381, length 32
19:10:06.814624 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff5b:68b2: ICMP6, neighbor solicitation, who has 2a03:4000:7:81:1462:76ff:fe5b:68b2, length 32
19:10:06.814774 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff89:910d: ICMP6, neighbor solicitation, who has 2a03:4000:9:76:b873:18ff:fe89:910d, length 32
19:10:06.815551 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff29:4ed0: ICMP6, neighbor solicitation, who has 2a03:4000:7:159:28f2:5bff:fe29:4ed0, length 32
19:10:06.816350 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff62:c09d: ICMP6, neighbor solicitation, who has 2a03:4000:2:ef:6421:76ff:fe62:c09d, length 32
19:10:06.816447 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff7d:60eb: ICMP6, neighbor solicitation, who has 2a03:4000:2:d:5054:2fff:fe7d:60eb, length 32
19:10:06.816582 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ffa6:c695: ICMP6, neighbor solicitation, who has 2a03:4000:8:442:5054:47ff:fea6:c695, length 32
19:10:07.071839 IP6 2a03:4000:2:24b::c7c7 > ff02::1:ffd6:b71c: ICMP6, neighbor solicitation, who has fe80::3835:93ff:fed6:b71c, length 32
19:10:07.361929 IP6 fe80::4872:c7ff:fe6f:ddc5 > fe80::1: ICMP6, echo request, seq 9114, length 8
19:10:07.365395 IP6 fe80::1 > fe80::4872:c7ff:fe6f:ddc5: ICMP6, echo reply, seq 9114, length 8
19:10:07.802711 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:8:56f::1, length 32
19:10:07.802787 IP6 fe80::22d8:b00:64ee:ff4 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has 2a03:4000:b:f9::1, length 32
19:10:08.102140 IP6 2a03:4000:2:24b::c7c7 > ff02::1:ffd6:b71c: ICMP6, neighbor solicitation, who has fe80::3835:93ff:fed6:b71c, length 32
19:10:08.381675 IP6 fe80::4872:c7ff:fe6f:ddc5 > fe80::1: ICMP6, echo request, seq 9115, length 8
19:10:08.384935 IP6 fe80::1 > fe80::4872:c7ff:fe6f:ddc5: ICMP6, echo reply, seq 9115, length 8
19:10:08.410272 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ffa6:c695: ICMP6, neighbor solicitation, who has 2a03:4000:8:442:5054:47ff:fea6:c695, length 32
19:10:08.410317 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ff31:e215: ICMP6, neighbor solicitation, who has 2a03:4000:7:122:d8ad:edff:fe31:e215, length 32
19:10:08.410617 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ffe6:5381: ICMP6, neighbor solicitation, who has 2a03:4000:2:4c7:5054:43ff:fee6:5381, length 32
19:10:08.411328 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ff89:910d: ICMP6, neighbor solicitation, who has 2a03:4000:9:76:b873:18ff:fe89:910d, length 32
19:10:08.411683 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ff29:4ed0: ICMP6, neighbor solicitation, who has 2a03:4000:7:159:28f2:5bff:fe29:4ed0, length 32
19:10:08.412157 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ff05:56f7: ICMP6, neighbor solicitation, who has 2a03:4000:9:91:788a:b3ff:fe05:56f7, length 32
19:10:08.412169 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ff00:3: ICMP6, neighbor solicitation, who has 2a03:4000:2:4ee::3, length 32
19:10:08.412197 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ff62:c09d: ICMP6, neighbor solicitation, who has 2a03:4000:2:ef:6421:76ff:fe62:c09d, length 32
19:10:08.412734 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ff5b:68b2: ICMP6, neighbor solicitation, who has 2a03:4000:7:81:1462:76ff:fe5b:68b2, length 32
19:10:08.412795 IP6 fe80::22d8:b00:64fa:424c > ff02::1:ff7d:60eb: ICMP6, neighbor solicitation, who has 2a03:4000:2:d:5054:2fff:fe7d:60eb, length 32
^C
42 packets captured
313 packets received by filter
0 packets dropped by kernel-> VM ping OPNsense-Gateway
ping6 a2
PING a2(a2) 56 data bytes
From a1 icmp_seq=1 Destination unreachable: Address unreachable
From a1 icmp_seq=2 Destination unreachable: Address unreachable
From a1 icmp_seq=3 Destination unreachable: Address unreachable
From a1 icmp_seq=4 Destination unreachable: Address unreachable
From a1 icmp_seq=5 Destination unreachable: Address unreachable
From a1 icmp_seq=6 Destination unreachable: Address unreachable
^C
--- a2 ping statistics ---
9 packets transmitted, 0 received, +6 errors, 100% packet loss, time 8176ms-> VM tcpdump
tcpdump -i ens4 -n icmp6
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on ens4, link-type EN10MB (Ethernet), snapshot length 262144 bytes
19:10:01.391690 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
19:10:02.399911 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
19:10:03.423936 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
19:10:04.448098 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
19:10:05.471933 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
19:10:06.495931 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
19:10:07.520077 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
19:10:08.543935 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
^C
8 packets captured
8 packets received by filter
0 packets dropped by kernelOK, hier nochmal von der VM (a1) auf OPNsense bzs. Gateway der OPNsense (a2):
ping a2
PING a2 (a2) 56 data bytes
From a1 icmp_seq=1 Destination unreachable: Address unreachable
From a1 icmp_seq=2 Destination unreachable: Address unreachable
From a1 icmp_seq=3 Destination unreachable: Address unreachable
From a1icmp_seq=4 Destination unreachable: Address unreachable
From a1 icmp_seq=5 Destination unreachable: Address unreachable
From a1 icmp_seq=6 Destination unreachable: Address unreachable
/tt]
-> tcpdump von a1
[tt]
tcpdump -i ens4 -q icmp6
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on ens4, link-type EN10MB (Ethernet), snapshot length 262144 bytes
18:58:18.028001 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
18:58:19.039924 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
18:58:20.063936 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
18:58:21.088117 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
18:58:22.111934 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
18:58:23.135910 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
18:58:24.160099 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
18:58:25.183936 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
18:58:26.207883 IP6 a1 > ff02::1:ff00:1: ICMP6, neighbor solicitation, who has a2, length 32
^C
9 packets captured
9 packets received by filter
0 packets dropped by kernel
Also:
-> VM
tcpdump -q icmp
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on ens4, link-type EN10MB (Ethernet), snapshot length 262144 bytes
=> Ergebnis: keine Logs bei Ping auf Gateway-Adresse der OPNsense
0 packets captured
0 packets received by filter
0 packets dropped by kernel
-> OPNsense
tcpdump -q icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vtnet0, link-type EN10MB (Ethernet), capture size 262144 bytes
18:24:18.624001 IP Host > gateway.netcup.net: ICMP echo request, id 20838, seq 6461, length 8
18:24:18.624652 IP gateway.netcup.net > Host : ICMP echo reply, id 20838, seq 6461, length 8
18:24:19.691744 IP HOST > gateway.netcup.net: ICMP echo request, id 20838, seq 6462, length 8
18:24:19.693354 IP gateway.netcup.net > Host: ICMP echo reply, id 20838, seq 6462, length 8
279 packets captured
19216 packets received by filter
0 packets dropped by kernel
Wie vorher schon angedeutet:
Ich habe keine Erfahrung mit tcpdump und habe meine Aussage aus Unwissenheit und Unkenntnis des Programms getätigt.
Entschuldigung hierfür.
Ich muss gestehen, das ich mit tcpdump noch gar nicht gearbeitet habe.
Eines aber scheint klar zu sein: tcpdump fängt von dem Interface ens4 keine IPv6-Pakete ab,
Alles anzeigenOPNSense hat eine Firewall - ist der IPv6 Verkehr in der Forward Chain hier blockiert?
Stimmt das Netzwerk Interface auf der VM - ist das Public Interface hier zusätzlich deaktiviert?
Wie sind denn die groben Ausgaben von ip a auf der VM?
Das funktioniert nur, wenn du die Adresse fe80::1 dem LAN-Interface des OPNSense zuweist. Ansonsten musst du die volle Adresse nehmen.
-> Forward Chain blockiert keinen IPv6-Verkehr
-> Interface auf der VM ist korrekt, das Public Interface ist komplett deaktivert.
Was genau meinst du mit "allgemeine Ausgaben" von ip a?
Ebenso: Was meinst du mit voller Adresse?
Dankeschön 
- Ping auf lokale Adresse 2a03:4000::10 funktioniert
- Ping auf Gateway-Adresse 2a03:4000::1 funktioniert schon nicht mehr
Als Gateway habe ich in "/etc/network/interfaces" gerade 2a03:4000::1 hinterlegt.
Erst einmal herzlichen Dank für die ersten Rückmeldungen.
In der Tat habe ich mich nicht ganz klar ausgedrückt bzw. Informationen nicht gegeben ...
WAN: 2a03:4000::a1
LAN: 2a03:4000::a2
Also, die VM liegen hinter der OPNsense in einem Cloud vLAN.
Aus diesem heraus sollen die VM über die OPNsense auf des Internet (sprich: Routing nach außen) zugreifen können.
Angepingt habe ich die berühmt berüchtigten Google-Server:
PING google.de(fra24s04-in-x03.1e100.net (2a00:1450:4001:827::2003)) 56 data bytes
From a1 icmp_seq=1 Destination unreachable: Address unreachable
From a1 icmp_seq=2 Destination unreachable: Address unreachable
From a1 icmp_seq=3 Destination unreachable: Address unreachable
From a1 icmp_seq=4 Destination unreachable: Address unreachable
Hierzu noch den Hinweis:
Wenn ich die betreffende VM mit Ihren "eigenen" (es geht hier auch um einen Root-Server) IP-Daten "ins Netz" lasse funktioniert alles prima.
Die IPv6-Konfiguration habe ich laut Netcup-Wiki vorgenommen:
net.ipv6.conf.default.accept_ra=0
net.ipv6.conf.default.autoconf=0
net.ipv6.conf.all.accept_ra=0
net.ipv6.conf.all.autoconf=0
net.ipv6.conf.eth0.accept_ra=0
net.ipv6.conf.eth0.autoconf=0IP-Forwarding ist an:
user@a1:~$ cat /proc/sys/net/ipv4/ip_forward
1Ein freundliches Hallo in die Runde,
ich habe für meinen Root-Server ein zusätzliches IPv6-Subnetz gebucht, komme aber beim Routing geneu dieses Subnetzes nicht wirklich weiter.
Im SCP werden die Daten wie folgt angegeben:
XXXX:XXXX:a:XXX::/64 -> Gateway / Routing auf fe80::1 (Standard-IPv6-Subnetz)
XXXX:XXXX:b:XXX::/64 -> Gateway / Routing auf XXXX:XXXX:a:XXX:XXXX:XXXX:XXXX:XXXX (zusätzlichen IPv6-Subnetz)
Zur Einrichtung habe ich in der OPNsense folgende Schritte unternommmen:
WAN-Interface:
IPv6-Address: XXXX:XXXX:a:XXX:XXXX:XXXX:XXXX:XXXX/64
Gateway: fe80::1
LAN-Interface:
IPv6-Address: XXXX:XXXX:b:XXX::1/64
Gateway: ? (bisher hahe ich hier nichts eingetragen)
Von der OPNsense aus kann ich über die Konsole und über das Webinterface alle möglichen IPv6-Adressen "anpingen".
Von meinen VM aus dem entsprechend konfigurierten LAN geht das allerdings nicht.
Für mich würde das auf ein Routing-Problem hindeuten ....
In der /etc/network/interfaces einer VM habe ich diese Einstellungen vorgenommen:
a)
iface ens4 inet6 static
address XXXX:XXXX:b:XXX::10/64
gateway XXXX:XXXX:b:XXX::1
Hier erhalte ich Fehlermeldungen:
icmp_seq=1 Destination unreachable: Address unreachable
icmp_seq=2 Destination unreachable: Address unreachable
icmp_seq=3 Destination unreachable: Address unreachable
icmp_seq=4 Destination unreachable: Address unreachable
icmp_seq=5 Destination unreachable: Address unreachable
b)
iface ens4 inet6 static
address XXXX:XXXX:b:XXX::10/64
gateway fe80::1
Hier erhalte ich Fehlermeldungen:
icmp_seq=1 Destination unreachable: Address unreachable
icmp_seq=2 Destination unreachable: Address unreachable
icmp_seq=3 Destination unreachable: Address unreachable
icmp_seq=4 Destination unreachable: Address unreachable
icmp_seq=5 Destination unreachable: Address unreachable
Muss ich in der OPNsense noch einen spezifische Route setzen?
Ich bin für jeden Tipp dankbar.
Viele Grüße
