You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I seem to have ended up with a few bridges. I have both UTM and Parallels installed.
I have at the moment three bridges:
bridge0
bridge100
bridge101
No VMs started (in either UTM or Parallels).
Now when I start a UTM MacOs Ventura VM, I get another one:
bridge102. 192.168.64.1
I assume the VM is connected to that bridge, because the IP addr matches the router settings inside the MacOs guest.
My problem is that I have no DNS inside the VMs from 192.168.64.1. Connectivity is good. Just no DNS.
A work around is to set the DNS inside the guest VM to 8.8.8.8 (or using my router gateway address has the same effect). But now, sadly I no longer resolve anything on my host machine which is a problem. I'm unsure what I've done to make this happen because I had both UTM and Parallels working just fine a week ago.
So I took this up with Parallels support first, because it's exactly the same problem for Parallels VMs and.. well... I'm paying them so may as well get my money's worth. Unfortunately after intensive data collection they've closed the ticket and pushed it to their engineering team... or something.
My problem is I don't really understand how bridges work, or how to interact with them on MacOs. Is there a way to delete those extra bridges and could they be part of the problem? Is there some process that runs the DNS server on 192.168.64.1 and what would it be called? Is this all part of the APIs created by Apple for HVF, or something in UTM? Could the UTM resolver somehow conflict with Parallels? I upgraded from Ventura to Sonoma on the host in case it fixed things... it didn't.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I seem to have ended up with a few bridges. I have both UTM and Parallels installed.
I have at the moment three bridges:
bridge0
bridge100
bridge101
No VMs started (in either UTM or Parallels).
Now when I start a UTM MacOs Ventura VM, I get another one:
bridge102. 192.168.64.1
I assume the VM is connected to that bridge, because the IP addr matches the router settings inside the MacOs guest.
My problem is that I have no DNS inside the VMs from 192.168.64.1. Connectivity is good. Just no DNS.
A work around is to set the DNS inside the guest VM to 8.8.8.8 (or using my router gateway address has the same effect). But now, sadly I no longer resolve anything on my host machine which is a problem. I'm unsure what I've done to make this happen because I had both UTM and Parallels working just fine a week ago.
So I took this up with Parallels support first, because it's exactly the same problem for Parallels VMs and.. well... I'm paying them so may as well get my money's worth. Unfortunately after intensive data collection they've closed the ticket and pushed it to their engineering team... or something.
My problem is I don't really understand how bridges work, or how to interact with them on MacOs. Is there a way to delete those extra bridges and could they be part of the problem? Is there some process that runs the DNS server on 192.168.64.1 and what would it be called? Is this all part of the APIs created by Apple for HVF, or something in UTM? Could the UTM resolver somehow conflict with Parallels? I upgraded from Ventura to Sonoma on the host in case it fixed things... it didn't.
Anything I can try?
Many thanks!
Beta Was this translation helpful? Give feedback.
All reactions