[FS#1358] Wireguard interface and the wrong route to the ip of the peer

[LEDE Bugs]

The following task has a new comment added:

FS#1358 - Wireguard interface and the wrong route to the ip of the peer
User who did this - Mikael (mikma)

----------
I have verified that my idea for a patch indeed does solve the bug I described. I'm including a patch for netifd tested with version 650758b16e5185505a3fbc1307949340af70b611 which used in branch lede-17.01.

It still won't pick up routes inserted by routing protocols such as babeld. As a work-around you need to add a static route to the wireguard endpoint.

BTW is really a host route necessary if "Route Allowed IPs" isn't enabled for the peer?

----------

One or more files have been attached.

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=1358#comment4445