Add function TunnelManager._get_win32_ipv6_route_table.

'--ip any' was also broken due to missing parenthesis.

When 2 nodes were started for the first time whereas:
- one of them is in client-only mode, connected to the other one
- the registry node is temporarily down
then the normal node never tried to rebootstrap or connect directly to the
only node it knows (the registry node).
Such case required to restart the daemon when the registry is back.

Moreover, there was no reason to query the registry node immediately after
having open new tunnels to peers found in cache, when this number is less than
expected.

This reduces the probability to lose all connections at the same time when a
gateway becomes out-of-order.

This bug could even freeze re6st completely when trying to rejoin the network.

Non-numerical address should be rare and this could even be counter-productive:
such remotes are more likely to host other services and forcing routes may
break already opened non-re6st connections.

Also provides systemd units.

It's normally safe to use --table=0 because most nodes use SLAAC and by default,
any existing default route is deleted.
It's better to abort if someone who explicitely wants to use a separate table
whereas the kernel is limited.