lebuser
lebuser
Comments
-
I wonder if your router is able to forward the SIT protocol (41) which you are trying to use. BTW GRE also use its own protocol (47), but WireGuard uses UDP.
-
There is no DHCPv6 server in systemd anyway. A DHCPv6 server with prefix delegation was one of the requirements. Open issue on systemd: network: implement DHCPv6 Server #16039
-
Which Linux distribution do you recommend for routers? Do they have DHCPv6-PD clients, and servers and are able to receive IPv6 prefixes from the upstream routers, which they split into sub-prefixes that are assigned to interfaces, or delegated to other routers using its DHCPv6 server?
-
I'm using certbot and have configured dns-rfc2136-propagation-seconds=120 which works for me. The propagation delay was about 90 seconds last time I checked. And that's the total delay from my master via my opendnssec live signer, and a slave of mine.
-
The IPv6 address ::2/128 used on Openvz 7 is invalid. Using it is completely broken. Bird also fills the log with: KIF: Invalid interface address ::2 for venet0
-
IPv6 is great, but I would prefer if I didn't have to configure each IPv6 address I want to use in the VPS configuration. I wonder why I can't have the whole IPv6 prefix (/64 or other size) routed to the VPS.
-
Do you need to use IPv6 NAT? Can't you instead add more global IPv6 addresses to the VPS, and assigned them to your peers. (The addresses also have to be removed from /etc/network/interfaces if you want to use them on the peers.) If you have a /112 with the VPS then you theoretically can use more than 60000 addresses. If…
-
What I'd like to see is one IPv6 address assigned on the external network interface, and one reasonably big IPv6 prefix that's routed via that address (or the link-local address). The routed IPv6 prefix will give you the flexibility to decide how to use the addresses, for example for docker, VPN clients etc. Having a /64…