Fusion 8.5.10 hijacks route to 192.168.2.x

This post was originally published on this site

Running Fusion 8.5.10 on macOS 10.14.6.

 

I have 3 sites; let’s call them Office (192.168.0.0/24), Home1 (192.168.1.0/24), and Home2 (192.168.2.0/24). They are fully meshed via pfsense 2.4.4/IPSec hardware tunnels connecting:

Office<–>Home1

Office<–>Home2

Home1<–>Home2

 

I’m at Home1, and my Mac can’t see through the tunnel to Home2 whenever I have Fusion running with networking.

 

Here’s my Mac’s route through the working tunnel to Office:

 

route get 192.168.0.2

   route to: <hostname>

destination: default

       mask: default

    gateway: 192.168.1.1

  interface: en0

      flags: <UP,GATEWAY,DONE,STATIC,PRCLONING>

recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire

       0         0         0         0         0         0      1500         0

 

Here’s my Mac’s to Home2 when Fusion is running with a network adapter installed:

 

route get 192.168.2.2

   route to: 192.168.2.2

destination: 192.168.2.0

       mask: 255.255.255.0

  interface: vmnet1

      flags: <UP,DONE,CLONING>

recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire

       0         0         0         0         0         0      1500   -205028

 

and my Mac can no longer access any resources at 192.168.2.x. Curiously, the Win7 VM in Fusion can get to resources at 192.168.2.x just fine.

 

My VM is configured with Bridged networking, so it gets a 192.168.1.x address from my DHCP server, so I don’t know why it’s messing with 192.168.2.x. But even if I change the networking type to NAT, it doesn’t fix the problem of my Mac getting to 192.168.2.x.

 

If I remove the network adapter from the VM _or_ if I shut off Fusion, then my Mac sees:

 

route get 192.168.2.2

   route to: 192.168.2.2

destination: default

       mask: default

    gateway: 192.168.1.1

  interface: en0

      flags: <UP,GATEWAY,DONE,STATIC,PRCLONING>

recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire

       0         0         0         0         0         0      1500         0

 

and then my Mac has the expected access to everything in 192.168.2.x.

 

How do I change the configuration of this VM so that it has networking but doesn’t hijack the route to 192.168.2.x? I don’t see any reference to that in the .vmx file (attached).

 

Thanks!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.