![]() ![]() I encountered the exact same problem after updating to Big Sur. ![]() Note: before updating (both to Fusion 12 and Big Sur) all was working between host and guest (both having a public IP address) and routing to Internet.Īny help or suggestions is very appreciated. This for saying that the problem should be strictly related to VLAN. What is interesting is if I move the guest bridge on the en0 (of the host), reconfiguring it with a public ip, all works (as expected). I already tried many of your dns or nat tested solutions to the related issues, but the problem persists. I also used tcpdump and I have verified that packets go out from guest and reach the host, but they do not come back. In other words, the default gateway for the vlan0 doesn’t respond to the guest (in any case both firewalls are off and forwarding is enabled). The problem is that the guest is unable to ping outside the host (guest host is ok). Network: public ip on a network adapter bridged on vlan0 Vlan0 -> tagged interface adapter on a public network I have this big problem with Fusion and Big Sur. The scenario is the following.Įn0 -> untagged interface adapter on a private network ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |