Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 168455

Fusion (not Pro) NAT range vs VPN

$
0
0

Hi,

I have a Linux (Oracle Linux 5) VM, inmported from Virtual Box. At the same time, I have a VPN at the host.

When I start the VM, I can't connect through the VPN (the VPN itself connects, but I can't get through). Setting VPN to 'use the VPN for all connections' solves this, but it's not an acceptable solution, it's not feasible to route through all my traffic through it (latency, speed, data caps).

 

I may be jumping to conclusions here, but I noticed that one of the ranges used by the VPN tunnel is 172.16.1.*.

Route table when VPN is up:

 

172.16             ppp0               USc             1        0    ppp0
172.16.2.227       172.16.2.248       UH              1        0    ppp0

 

Route table when the VM is up:

172.16.186/24      link#12            UC              3        0  vmnet1
172.16.186.255     link#12            UHLWbI          1      158  vmnet1
172.16.236/24      link#13            UC              3        0  vmnet8
172.16.236.255     link#13            UHLWbI          1      158  vmnet8

 

Strangely this happens even for bridged networking.  Although the guest does indeed report a difference: a 172.16.* address with NAT, 192.168.* for bridged (which is correct).

 

Is there any way how to influence the range VMWare Fusion uses?

 

Thanks


Viewing all articles
Browse latest Browse all 168455

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>