Change Details

Some ISPs use DHCPv6-PD to dynamically assign customer a `/64` network, which is not enough to use for several situations. I'm developing a NAT66 kernel module to implement stateless network prefix translation for IPv6, use EUI-64's identifier `0xFFFE` as tag, allows user to translate a `/64` public network to a private `/50` network (give user 14 more network prefix bits). So the address will be enough for most situations (but it has restricts on DHCPv6 server, or relys on SLAAC for subnets). Does VyOS accept this kernel patch and configuration scripts?

Some ISPs use DHCPv6-PD to dynamically assign customer a `/64` network, which is not enough to use for several situations. I'm developing a NAT66 kernel module to implement stateless network prefix translation for IPv6, use EUI-64's identifier `0xFFFE` as tag, allows user to translate a `/64` public network to a private `/50` network (give user 14 more network prefix bits). So the address will be enough for most situations (but it has restricts on DHCPv6 server, or relys on SLAAC for subnets), and help user to use private static IPv6 address in their internal network to avoid address changes by ISP. Does VyOS accept this kernel patch and configuration scripts?

Some ISPs use DHCPv6-PD to dynamically assign customer a `/64` network, which is not enough to use for several situations. I'm developing a NAT66 kernel module to implement stateless network prefix translation for IPv6, use EUI-64's identifier `0xFFFE` as tag, allows user to translate a `/64` public network to a private `/50` network (give user 14 more network prefix bits). So the address will be enough for most situations (but it has restricts on DHCPv6 server, or relys on SLAAC for subnets), and help user to use private static IPv6 address in their internal network to avoid address changes by ISP. Does VyOS accept this kernel patch and configuration scripts?