If you use a network mask of 255.255.255.0, then a total of 254 host ID's are addressable on any arbitrary network using the last octet. A subnet utilizes the mathematical bitwise operator AND. For the default private class C addressing scheme, any network ID that is returned after the subnet mask bitwise AND operator 255.255.255 that equals 192.168.0 is on the same network; any OTHER network ID will be a different network and will require a router to handle the packets addressed to it.
For example, 192.168.1 is on a different network than 192.168.0. If the subnet mask implemented is 255.255.255.0, then 254 hosts can exist on each of 254 seperate networks. A packet addressed to 192.168.1.10 from any host on network 192.168.0 gets sent by the router (192.168.0.1) to the router handling that network, i.e. 192.168.1.1. 192.168.0.1 knows to do that, because 192.168.1.10 is not in his domain.
If I utlize subnet mask 255.255.255.248, then I have 6 hosts avaialable on each of 8190 networks. I can use class A addressing of 10.10.10 if I'd like, but the last octet is tricky because its sharing network ID & host ID simultaneously. 248 translates to 11111000. And so any combination of 1 or 0 for the first 5 bits are available for network ID, while only the last three bits are avaialable for host ID.
28 bits translates to 256 combinations. However, 0 (all bits in the octet off) is reserved for the network address, and 255 (all bits in the octet on) is reserved for the broadcast address; two network IDs for each network are unuseable.
Your VM host machine has network ID of 192.168.0.70. That is the real network ID for the network adapter (NIC). The VM itself is configured with a virtual network adapter having a network address of 192.168.0.100. The VM should be able to ping itself, 127.0.0.1 (or 0.0.0.0), as the local loopback address. It should also be able to see 192.168.0.70 without any issues.
Any other host on the network, including the router, e.g., 192.168.0.1, should be able to see 192.168.0.70. However, NOBODY else is going to know what 192.168.0.100 is; as far as they're concerned it doesn't exist. Depending on how you configure the VM, will depend on the network resources available to 192.168.0.100.
When you use "host-only networking" on the VM, a network connection between the virtual machine and the host computer, using a virtual Ethernet adapter that is visible to the host operating system. This approach can be useful if you need to set up an isolated virtual network.
If you use host-only networking, your virtual machine and the host virtual adapter are connected to a private TCP/IP network. Addresses on this network are provided by the VMware DHCP server.
If you want to connect to the Internet or other TCP/IP network using the host computer’s dial-up networking or broadband connection and you are not able to give your virtual machine an IP address on the external network, NAT is often the easiest way to give your virtual machine access to that network. However your virtual machine will not have its own IP address on the external network when implementing NAT on the VM. Instead, a separate private network is set up on the host computer. Your virtual machine gets an address on that network from the VMware virtual DHCP server. The VMware NAT device passes network data between one or more virtual machines and the external network. It identifies incoming data packets intended for each virtual machine and sends them to the correct destination.
Bridged networking is often the easiest way to give your virtual machine access to the network when your host computer is on an Ethernet network. On a Windows host, you can use bridged networking to connect to either a wired or a wireless network. On a Linux host, you can use bridged networking to connect to a wired network.
If you use bridged networking, your virtual machine needs to have its own identity on the network. For example, on a TCP/IP network, the virtual machine needs its own IP address. Your network administrator can tell you whether IP addresses are available for your virtual machine and what networking settings you should use in the guest operating system. Generally, your guest operating system can acquire an IP address and other network details automatically from a DHCP server. You might need to set the IP address and other details manually in the guest operating system.
Using bridged networking enables the virtual machine to be a full participant in the network. It has access to other machines on the network and can be contacted by other machines on the network as if it were a physical computer on the network.
If the host computer is set up to boot multiple operating systems and you run one or more of them in virtual machines, you need to configure each operating system with a unique network address. People who boot multiple operating systems often assign all systems the same address, since they assume only one operating system will run at a time. If you use one or more of the operating systems in a virtual machine, this assumption is no longer true.
