wsproxy: limit access, reconnect / timeout, other questions

[streaps]

I'm new to VpnCloud and tried it the first time yesterday. I enjoyed the easy setup for a basic VPN configuration. Downloaded the deb packages for three different archs (i386, amd64, armhf), installed, vpncloud config, started wsproxy and the vpncloud services -> success.

There are some open questions and problems I have:

1. If I understand it correctly, the wsproxy is just a dumb proxy without any authentication or any other way to deny access for strangers. How can I prevent that it is used by anyone? My understanding is that it's usually has to be accessible from the public internet and I cannot filter by IP as peers should be able to connect from everywhere. Can the wsproxy misused for other connections than vpncloud traffic? Like getting access to the internal network?

2. I've tested vpncloud over a mobile connection which disconnects occasionally. When it's online again, it takes a long time for the vpncloud connection to reconnect. With zerotier the VPN is online again instantly after the mobile connection is online again. Do I need to lower the peer-timeout for all peers? Or has it something to do with the wsproxy.

3. I'm using wsproxy to reach a IPv6-only peer from an IPv4-only network. For other connections to IPv4 peers, in case there is IPv6 connectivity or for multiple peers in a local network, it would be useful if it were listening on the local port too.

4. If there is no internet connection and the DNS lookup of the wsproxy address fails, the vpncloud process exits on startup:

sudo systemctl start vpncloud@abc
Job for [email protected] failed because the control process exited with error code.
See "systemctl status [email protected]" and "journalctl -xe" for details.

07:04:58 vpncloud[904]: ERROR - Failed to open socket ws://example.com:80: Failed to connect to URL ws://example.com:80: IO error: failed to lookup address information: Temporary failure in name resolution
07:04:58 systemd[1]: [email protected]: Control process exited, code=exited, status=255/EXCEPTION
07:04:58 systemd[1]: [email protected]: Failed with result 'exit-code'.
07:05:03 systemd[1]: [email protected]: Scheduled restart job, restart counter is at 1.

Is this intentional? (failing and letting systemd restart instead of handling it internally).