Search results

bump for answers

What peculiarities? You're not really explaining anything, nor referring/linking to anything I can look up. What is preventing MacOS from using a VM as a gateway? It has no difficulty pinging the machine. Also, despite the fact I have authored a KEXT back in the day, I don't know what you mean...

This is my forum post on Apple with screen shots showing what's working and what isn't: https://discussions.apple.com/thread/255149391?page=1

Update: I managed to create a NetworkService for bridge101 (the host-only bridge). I seem to remember this is as far as I could get last time I tried to get this to work. The issue is while I can ping the VM and in the UI set the VM as the router, for whatever reason MacOS can't access the...

Try as I might, I cannot get the virtual network to show up in System Preferences (MacOS). This used to work just fine in Yosemite (and probably some more recent versions but I don't recall at the moment). Does anyone have any suggestions? The "Connect Mac to this network" check box doesn't...

I have a Windows 11 guest and a Monterey host in this specific setup. I manually set the IPs to make things foolproof. Using host-only networking. Windows IP: 10.37.129.4 Monterey IP: 10.37.129.2 Used ipconfig in windows to confirm IP. Used ifconfig in Monterey to confim IP. Windows can ping to...

I managed to create a Network Service for the virtual network by editing /Library/Preferences/SystemConfiguration/preferences.plist

I managed to create a Network Service for the bridge101 interface by editing /Library/Preferences/SystemConfiguration/preferences.plist Unsure why Parallels can't do this.

I managed to manually edit /Library/Preferences/SystemConfiguration/preferences.plist and for the Network Service to show, but the old method to use the virtual gateway which worked in Mojave isn't working in Monterey. The routing table is now automatically set and looks correct (same as I...

I attempted to add the entry in /Library/Preferences/SystemConfiguration/preferences.plist to make the Network Service show up like it used to in Mohave to no avail.

I've been trying to get a simple route working in Parallel Desktop for days with zero success. I had a similar setup working in Mohave using an older version. Setup: I have a linux router running on the host-only virtual network at 10.37.129.3. The host OS, Monterey, is at 10.37.129.2. I just...

It should be possible to route the traffic without using the GUI, but for some reason the route command lines don't work in Monterey. Interestingly, I can set the default gateway on a Windows 11 VM on the same host-only network and it connects to the Linux router just fine, so I know the router...

Monterey stinks so I'm looking into the painful process of downgrading to a more usable system. Is this going to cause me problems with Parallels Desktop?

I have the same issue, I think. There is no host network interface for the host-only network. I think this has more to do with the MacOS version than the platform.

I used a VM on my old core2duo as a router providing internet to the host. I did this via a host-only connection then turned on the option to display the interface in System Preferences. That option is now missing, supposedly due to changes in MacOS introduced in Big Sur (i'm using Monterey)...

According to prlsrvctl it isn't bound to a device. How do I fix this? ~  prlsrvctl net list Network ID Type Bound To Shared shared NAT server: Host-Only host-only Wi-Fi (en0) bridged en0 Default bridged FF:FF:FF:FF:FF:FF

I think the old interface was called vnic and I don't see that present.

There are a zillion devices listed if I type ifconfig in MacOS, but I can't find any documentation as to which is which

The option to show the interface in System Preferences described here is absent! https://kb.parallels.com/en/116528

How do I get the Parallels ethernet device ("interface") to show up in System Preferences -> Network when using Host-Only? I have this setup on a much older system with a much older Parallels Desktop, but I don't recall having to do anything special to make the virtual ethernet device show up...