I'm trying to use wireguard on tl-wdr4300 running 17.01.4, but the route inserted by proto_add_host_dependency is incorrect. After a /etc/init.d/network restart it adds a host route on dev lo which obviously will make it unreachable.
If I remove the host route and bring the wireguard interface down and up, then the host route is added on the wan interface. This is also incorrect in my case, since I use dynamic routing using the babeld routing daemon, but the route inserted by babeld isn't used by proto_add_host_dependency+netifd.
Should we add a way for the user to stop host dependencies from inserting host routes? Or can this be fixed in another way?
I think I found it in the issue tracking system, I guess I'll continue there: https://bugs.openwrt.org/index.php?do=details&task_id=1358