This provides native ipv4 to clients on a network having an ipv6-only backend, relying on external plat. This allows to use clients in ipv6-only networks that would otherwise refuse to connect without a valid ipv4 route. Limitations: * External plat must be provided, for example by jool - for example by https://github.com/FreifunkMD/jool-docker.git * This implementation will break ipv4 connections when clients roam.
33 lines
915 B
ReStructuredText
33 lines
915 B
ReStructuredText
gluon-464xlat-clat
|
|
==================
|
|
|
|
This package provides the kernel module and functionality required to support
|
|
ipv4 clients on an ipv6-only backbone.
|
|
|
|
Assumptions
|
|
-----------
|
|
|
|
* Clients will be given IPv4 addresses by a dhcp daemon that runs on each node.
|
|
gluon-ddhcpd is a great choice for this.
|
|
* There is a component on the network that does plat on the default network
|
|
64:ff9b::/96. https://github.com/FreifunkMD/jool-docker.git can do this.
|
|
|
|
Limitations
|
|
-----------
|
|
* When roaming, clients will experience temporary loss of IPv4 connectivity
|
|
|
|
site.conf
|
|
---------
|
|
|
|
clat_range : mandatory
|
|
- infrastructure net (ULA) from which a /96 clat prefix will be generated.
|
|
- This must be a /48 prefix.
|
|
- This can be the same for each community and is pre-registered at https://wiki.freifunk.net/IP-Netze#IPv6 as part of fdff:ffff:ff00::/40
|
|
|
|
Example::
|
|
|
|
{
|
|
clat_range = 'fdff:ffff:ffff::/48',
|
|
}
|
|
|