From 798f9934fca523dfb57136bd185cf6e9460323ad Mon Sep 17 00:00:00 2001 From: Lorenzo Colitti Date: Fri, 31 Oct 2014 21:54:33 +0900 Subject: Use different IPv4 addresses on different clat interfaces. Previously the code would use 192.0.0.4 on all clat interfaces. This works, but it has the problem when a clat interface goes down, we do not reset TCP connections on its IP address if there is another clat interface up. Fix this by assigning every clat interface its own IP address in 192.0.0.0/29. Bug: 12111730 Change-Id: I28c831acd93b0980efea8e90c1cdf8b607beac68 --- clatd.conf | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'clatd.conf') diff --git a/clatd.conf b/clatd.conf index 3805c6d..ff80975 100644 --- a/clatd.conf +++ b/clatd.conf @@ -3,8 +3,14 @@ # A host IID of :: means to generate a checksum-neutral, random IID. ipv6_host_id :: -# ipv4 subnet for the local traffic to use. This is a /32 host address +# IPv4 address configuration to use when selecting a host address. The first +# clat daemon started will use the address specified by ipv4_local_subnet. If +# more than one daemon is run at the same time, subsequent daemons will use +# other addresses in the prefix of length ipv4_local prefixlen that contains +# ipv4_local_subnet. The default is to use the IANA-assigned range 192.0.0.0/29, +# which allows up to 8 clat daemons (.4, .5, .6, .7, .0, .1, .2, .3). ipv4_local_subnet 192.0.0.4 +ipv4_local_prefixlen 29 # get the plat_subnet from dns lookups (requires DNS64) plat_from_dns64 yes -- cgit v1.2.3