# not fully understood
# https://unix.stackexchange.com/q/509430/
# man `systemd.network`
# https://superuser.com/q/1562380
# https://docs.netgate.com/pfsense/en/latest/network/ipv6/subnets.html

[Match]
Name=eth0

[Network]
# Start at some time between 2025-02-20T08:32Z and 2025-02-22T11:21Z, this VPS
# can't ping public network ipv6, e.g., `ping  2606:4700:4700::1111` will have
# no response. So default ipv6 DNS will not work, I have to force to use ipv4
# DNS here to make the VPS partially work. But still, can't ping outside ipv6
# issue is not fixed.
DNS=9.9.9.9 1.1.1.1

[Address]
Address=216.126.232.27/22

[Address]
Address=2606:a8c0:3::75f/128

[Address]
# another ipv6 address for aa wireguard+swgp into
# not sure if it is corret, but it works
Address=2606:a8c0:3:773::b/64

[Address]
# the last address seems is the default?
# ...:1/64 also works, but I use ...:a/64 because crunchbits panel reverse DNS support this address
# 2024-06-27, ...:1/64 seems doe not work any more, not sure why
Address=2606:a8c0:3:773::a/64
# use the following will not need GatewayOnLink=yes in [Route] section, but I'm not sure if it is correct, I'm not sure if those ips could be accessed without gateway, more see https://superuser.com/q/1562380
#Address=2606:a8c0:3:773::a/48

[Route]
Gateway=216.126.232.1

[Route]
Gateway=2606:a8c0:3::1
# GatewayOnLink=yes needed for 2606:a8c0:3::1 gateway, maybe because 2606:a8c0:3::1 is not in the same subnet as 2606:a8c0:3:38d::a/64? see: https://serverfault.com/q/814419
GatewayOnLink=yes