Host VPN breaks RDP connection to Windows guest

I installed WinApps and its working quite well so far. Only thing I noticed is, whenever I'm connected to a VPN on the Linux host using `ipsec`, the RDPWindows VM claims there is no network/internet connection available.

According to the output of `bin/winapps check` this also breaks RDP connections to the VM, therefore starting any Windows application from the Linux host while connected to the VPN does not work:

```bash
$ ./bin/winapps check
[10:48:00:413] [56779:56780] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state
[10:48:00:413] [56779:56780] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[10:48:00:413] [56779:56780] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[10:48:00:413] [56779:56780] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[10:48:00:413] [56779:56780] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rail
[10:48:00:413] [56779:56780] [INFO][com.freerdp.client.common.cmdline] - loading channelEx drdynvc
[10:48:00:728] [56779:56780] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized
[10:48:00:729] [56779:56780] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state
[10:48:00:729] [56779:56780] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state
[10:48:15:743] [56779:56780] [ERROR][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex ERRCONNECT_CONNECT_FAILED [0x00020006]
[10:48:15:743] [56779:56780] [ERROR][com.freerdp.core] - failed to connect to 192.168.122.62
```

FWIW, this is the VPN connection configured in `/etc/ipsec.conf`:

```
conn www.my-domain.tld
keyexchange=ike
dpdaction=clear
dpddelay=300s
eap_identity=my-user@my-domain.tld
leftauth=eap-mschapv2
left=%defaultroute
leftsourceip=%config
leftdns=%config4
right=www.my-domain.tld
rightauth=pubkey
rightsubnet=0.0.0.0/0
type=tunnel
auto=add
```

Start by reproducing the failure with the Linux host connected to the IPsec VPN, then run bin/winapps check and inspect the routing implied by /etc/ipsec.conf. Done means the Windows guest retains network access and bin/winapps check can connect to 192.168.122.62 while the VPN is active.

Written by the indexing model from the issue text.