On 5/26/19 12:15 PM, Hans Dedecker wrote:
Hi,
On Sun, May 26, 2019 at 12:19 PM Fabian Bläse via openwrt-devel
<[email protected]> wrote:
[...]
Please use git send-email to deliver the patch
Hans
---
package/network/config/gre/files/gre.sh | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/package/network/config/gre/files/gre.sh
b/package/network/config/gre/files/gre.sh
index 2bb1010b76..3414ed3047 100755
--- a/package/network/config/gre/files/gre.sh
+++ b/package/network/config/gre/files/gre.sh
[...]
I can confirm the need to manage the routing generated by the call.
When I was using Layer 2, GRE tunnels I found that I had reverse
at least some of effect of the call to get routing to work properly.
I was unable to determine why the routing was being set as it was,
and crudely reversed it with
( proto_add_host_dependency "$cfg" "$peeraddr" "$tunlink" )
+ # jmk -- hack for broken logic somewhere
+
+ ip route delete proto static "$peeraddr"
+
Jeff
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
