Routing problems with bridge101 aka host-only in Sequoia (was Monterey, Ventura)

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 want to route traffic through the linux router. The routing table looks fine:

Code:

> netstat -nrf inet
Routing tables

Internet:
Destination        Gateway            Flags           Netif Expire
default            10.37.129.3        UGScg       bridge101
default            link#19            UCSIg       bridge100      !
default            link#21            UCSIg       bridge101      !
8.8.8.8            link#21            UHLWIg      bridge101      !
10.0.0.12          link#21            UHLWIig     bridge101      !
10.37.129/24       link#21            UC          bridge101      !
10.37.129.2        b2.be.83.d5.0.65   UHLWIi            lo0
10.37.129.3        0.1c.42.87.1e.68   UHLWIir     bridge101   1075
10.37.129.255      ff.ff.ff.ff.ff.ff  UHLWbI      bridge101      !
10.211.55/24       link#19            UC          bridge100      !
10.211.55.2        b2.be.83.d5.0.64   UHLWIi            lo0
10.211.55.255      ff.ff.ff.ff.ff.ff  UHLWbI      bridge100      !
127                127.0.0.1          UCS               lo0
127.0.0.1          127.0.0.1          UH                lo0
127.0.0.2          127.0.0.1          UHW3I             lo0   2068
224.0.0            link#1             UmCS              lo0
224.0.0.251        link#1             UHmW3I            lo0   3471
239.255.255.250    1:0:5e:7f:ff:fa    UHmLWIg     bridge100

This output looks good, too:

Code:

> route get 8.8.8.8
   route to: 8.8.8.8
destination: default
       mask: default
  interface: bridge101
      flags: <UP,DONE,CLONING,STATIC,IFSCOPE,GLOBAL>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu     expire
       0         0         0         0         0         0      1500     -1408

Running tcpdump on the router I can see when Monterey pings the router, but there is no traffic if I set it as the default gateway.
I can also use the linux router as the Windows 11 default gateway just fine, so the router doesn't appear to be the problem.
Anyone have any suggestions?!

 

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 managed to manually edit

Code:

/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 manually set it before), but still can't route and tcpdump on the router shows no attempt. The only curious change is

Code:

route get 8.8.8.8

now takes a long time, but with the same result.

 

I have encountered the same issue, Hi @BallO , have you resolved this issue
I am on Ventura 13.5 with M1

 

I'm also trying to figure out how to route traffic from host(macOS sonoma) to vm , but fail.
On linux , I install a virtualbox vm , and setup a route :

Code:

# 192.168.56.2 is the IP of vm
 ip r add 10.21.1.0/24 via 192.168.56.2

then ping 10.21.1.9 on host, I can see icmp message via tcpdump .

but on macOS , not working .

 

At this point I have given up getting any tech support on this issue and am looking for alternatives

 

Used wireguard

 

I experienced the same issue as u @BallO

I installed wireguard in the mac and on the linux guest and it worked.

Install server: https://github.com/angristan/wireguard-install
Install client in mac: https://www.wireguard.com/install/
Maybe we can look at the source code of the app and see what are they doing.

 

Is there any way to turn off encryption, which is just a waste of power considering it's all hosted on the same machine?
If not, I don't see any reason to use wireguard given ssh tunneling works the same way.

 

Haha, usual linux a-holes attacking the question instead of answering it:
https://www.reddit.com/r/WireGuard/comments/j03yby/peer_connection_without_encryption/
Pass.

 

好兄弟，你讲得太专业了

 

So I tried the script @Will_1231 linked and it didn't go so well:

 

It is not straightforward to configure but I can assure you that it works great!

 

Yeah, I think I have some missing packages. The script does things very blindly with fingers crossed. I'm going to try a different script.

 

I tried again and managed to get the wirechark client in MacOS to go "Active" but still no connection. I managed to get "Active" with two different wireguard scripts. Maybe the Mac client for Ventura is broken beyond repair.

 

OK I think I got it to work, finally. The trick for me was to use the "Edit" button in the "Manage WireGuard Tunnels" window. Hopefully that helps anyone else trying to work around the bug.

 

I've hit the limitations of this wireguard work-around. For example if the VM is connected to a gatewat that I need the Mac host to connect to, it seems impossible to do via WireGuard. I've tried to do this via ssh tunnels instead and it worked for about a minute then the mystery Parallels problem which causes packets to disappear down a black hole appears and kills all the ssh connections. Another problem is it's impossible to 'share' a VPN tunnel in MacOS with WiFi. If you need to connect another device to the gateway, like a phone, it's impossible with WireGuard.

Does anyone have a clue as to why I can't use a VM as a router as I used to do with Parallels running on x86 Catalina? It's a really frustrating situation.

 

My wireguard setup which worked in Ventura no longer works in Sequoia, perhaps because my hack for getting a Network Service for bridge101 no longer works. I found this was necessary to change the service order in order for wireguard to work.

I'm back to completely non-functional except via an ssh tunnel which only works for web stuff

 

wireguard also requires at least one Network Service to be connected