Hi Olivier!
@olivierlambert said in Very scary host reboot issue:
IIRC, a fix was released preventing the issue to occur again.
Note there's no IPv6 support in Dom0 in 8.2 (only in 8.3), so I'm not sure how did you ended configuring v6 on 8.2
XCP-ng v8.2.1 may not have real IPv6 support (and remains ignorant, uses a single IPv4 for management), but CentOS in Dom0 does. Activation:
in /etc/sysctl.d/90-net.conf:
# Enable IPv6 on interfaces
net.ipv6.conf.all.disable_ipv6 = 0
net.ipv6.conf.default.disable_ipv6 = 0
# Enabling IPv4 forwarding
net.ipv4.ip_forward = 1
# ENABLE IPv6 forwarding
net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.default.forwarding = 1
/etc/rc.local addition:
# SAFETY: generous grace time period for XCP-ng xapi network start (allow xenbr0 to come up)
sleep 60
# activate additional IPv4 subnet
ip addr add xxx.251.xxx.1/28 dev xapi0
# prevent broadcasts leaking out externally
iptables -A FORWARD -m pkttype --pkt-type broadcast -i xenbr0 -j DROP
# IPv4 done
# activate IPv6 router address on xapi0
ip addr add 2a01:XXX:XXX:8041:ffff::2/127 dev xapi0
# add IPv6 default gw on xenbr0 (this is link-local)
ip -6 ro add default via fe80::1 dev xenbr0
# add IPv6 route for our /64 towards OPNsense
ip -6 ro add 2a01:XXX:XXX:8041::/64 via 2a01:XXX:XXX:8041:ffff::3 dev xapi0
# IPv6 done
This works flawlessly. The OPNsense VM is the ::3 destination of the /64 route.
As for the fix you mentioned, is that specific to 8.3 or is it also avaiable for 8.2.1? Can you point me to the relevant information?
Thanks a lot for your quick response.