You can find the vpn interface with the ifconfig terminal command.Īnd the last part it needs to be added to the specific anchor's nat rules. The address can be copied from the results of the first command. It is really important, that the interface and ip address you see above needs to be changed to yours. In my case this is utun8.Įcho "nat on utun8 inet from 192.168.29.0/24 to any -> (utun8) extfilter ei" >nf Need to add a new rule with the tun interface of your vpn client. Sudo pfctl -a -sharing/shared_v4 -s nat 2>/dev/null >nf I copied the output of this command to a text file nf with the first command If you are familiar with this or brave enough to run this commands, then here is the workaround: Sudo pfctl -a -sharing/shared_v4 -s nat 2>/dev/null If you run this command in the terminal it will lists the created rules by vmware after the guest started: (Big Sur disallow to load external kexts - so this is probably because of this new rule)Īnd the main reason is F12 only add the necessary rules to the main interfaces (en0, en1 - in my case) and the openvpn utun8 has no rules to allow address translations so that's sees the patckets with the guest internal ips. In F12 and BS there is a new bridge device bridge100 in my case which needs packetfilter nat rules to route through the other interfaces. Previously there were no bridge interfaces to manage nat data it was inside the network stack of fusion vmnet devices. In Big Sur or in Fusion 12 the network handling changed.
0 kommentar(er)
