From 86802acefdbdb5e9a60ea552c6ebaa3af94d7dd1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Linus=20L=C3=BCssing?= Date: Thu, 15 Nov 2018 01:44:27 +0100 Subject: [PATCH] gluon-mesh-batman-adv: Add IPv4 subnet to br-client MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This allows us to route and NAT between br-client and br-wan in the future. Which is necessary for the gluon-alt-esc-provider package, for instance. With the local-node routes separated in their own table, the issue described in: 3ef28a46842b ("gluon-client-bridge: Revert "move IPv4 local subnet route to br-client (#1312)" and initially introduced in: b3762fc61cca ("gluon-client-bridge: move IPv4 local subnet route to br-client (#1312)") does not apply anymore, which makes this change safe again. Signed-off-by: Linus Lüssing --- .../gluon/upgrade/320-gluon-mesh-batman-adv-client-bridge | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/package/gluon-mesh-batman-adv/luasrc/lib/gluon/upgrade/320-gluon-mesh-batman-adv-client-bridge b/package/gluon-mesh-batman-adv/luasrc/lib/gluon/upgrade/320-gluon-mesh-batman-adv-client-bridge index 58c6084a..16ae140a 100755 --- a/package/gluon-mesh-batman-adv/luasrc/lib/gluon/upgrade/320-gluon-mesh-batman-adv-client-bridge +++ b/package/gluon-mesh-batman-adv/luasrc/lib/gluon/upgrade/320-gluon-mesh-batman-adv-client-bridge @@ -25,6 +25,11 @@ uci:section('network', 'interface', 'client', { uci:delete('network', 'client_lan') +uci:section('network', 'route', 'br_client_route', { + interface = 'client', + target = site.prefix4(), +}) + uci:section('network', 'rule', 'local_node_rule', { src = next_node.ip4 .. '/32', lookup = 2,