Yggdrasill Gateway+Peer workaround

[darkdrgn2k]

ref #322

Two options to work around bug identified in #322

Options defined in /etc/yggdrasil.iptunnel.conf as "reroutepeers"

[general]
reroutepeers=unroutepeers

Default - empty no workaround

reroutepeers=routepeers

Iterate through peers and add them to the systems default gateway
Add default routes over ygg

Pros

Currently works for all listed peers

Cons

When gateway changes tunnel collapses

reroutepeers=unroutepeers

Instead adding default routes progressively add routes but omitting the peer's ip

Pros

When ygg interface collapses routes are removed
Since route for peer is never set it always uses the system default (survives roaming wifi etc)

Cons

Currently works for only the first peer
Fills up the route table with routes

Additional Notes

• when JQ installed on system, it will read the yggdarsill config file for peers.
• if JQ is not installed uses getPeers which means the peer must already be connected
• Cant parse hostnames (assumes ips)
• If/When Hostnames are used, DNS resolve may be an issue (round robin dns)

[darkdrgn2k]

TESTING

• Install yggdarsill
• Peer TCP to another node
• Make sure that TCP is the only path to the exit node
• Configure IPTunnel.client
• Report success and failures

[benhylau]

Do a global spell-check of yggdrasil