![]() ![]() I don't do microsoft for network transport because, among other things, they generally seem to want extra money for things like active routing. I would presume that you have put in some sort of server-grade version of Windows into vm3 and configured it as a fully functioning router. On a linux host the kernel prevents/enjoins any sort of armor at that layer, which is why you can route between "host only" networks as first class network devices. That said, I have no idea if windows is "smart enough" to route between host-only networks since I don't know if there is any sort of "security armor" in the windows drivers to make them host only. It will help people to notice what you are doing, its less likely to run afoul of any sort of automations, and it is less likely to be clobbered by accident during an update. vmnet2, or vmnet9 or whatever) for your aditional host-only networks. So its better to leave zero (0) and eight (8) as is, and "add" a new vmnet endpoint (e.g. ![]() There are like 99 arbitrary endpoints in the vmnet driver. ![]() vmnet0 is bridged, vmnet1 is host-only, vmnet8 is natted). Its better to leave the existing pre-defined networks as is (e.g. Sometimes you see what you expect to see.Īs a suggestion you should _not_ go in and "de-nat" vmnet8. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |