commit 7c3b5dcb95deb41fda40de7eb682629fcbdd3b46
author Maciej Żenczykowski <maze@google.com> Mon Nov 18 17:20:01 2019 -0800
committer Maciej Żenczykowski <maze@google.com> Sat Nov 30 09:34:56 2019 +0000
tree 7b3fb0cddf6492c5d8dfeacce3855a657c7aedb5
parent 69c840fe5363ead6c0d6e012965b7c1538055584

remove configuration option 'ipv4mtu'

Specifying the MTU in a per-device configuration file is in
general incorrect because different networks have different MTUs.

Carriers or operators that want to lower the MTU can lower the
IPv6 MTU (from which the IPv4 MTU is automatically calculated),
or set the MTU manually from Nat464Xlat or ConnectivityService.
Doing it this way has the benefit of supporting different MTUs
for different networks.

Test: builds
Bug: 144730808
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: Ia6005421e81fc0007067d9774e28f9aae64d1160

config.c

diff --git a/config.c b/config.c
index c370770..e820ba0 100644
--- a/config.c
+++ b/config.c
@@ -330,7 +330,7 @@
 
   if (!config_item_int16_t(root, "mtu", "-1", &Global_Clatd_Config.mtu)) goto failed;
 
-  if (!config_item_int16_t(root, "ipv4mtu", "-1", &Global_Clatd_Config.ipv4mtu)) goto failed;
+  Global_Clatd_Config.ipv4mtu = -1;
 
   if (!config_item_ip(root, "ipv4_local_subnet", DEFAULT_IPV4_LOCAL_SUBNET,
                       &Global_Clatd_Config.ipv4_local_subnet))