VMware Cloud Community
techmen8080
Contributor
Contributor

First vm is connected to network/internet - second vm will not connect to anything.

The vm listed below this sentence is able to use the network and access the internet.

root@asimov ~]# route

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

64.84.15.248 * 255.255.255.248 U 0 0 0 eth0

169.254.0.0 * 255.255.0.0 U 0 0 0 eth0

default 249-15.84.64.ma 0.0.0.0 UG 0 0 0 eth0

The vm listed below this paragraph(second one I created) cannot ping even the above vm and is not accessing the internet. They both show green lights on the VMnetwork port group and look like they are attached to Nic2 which is attached to the physical network. All attempts to ping anything come back with Network is unreachable - which I interpret as a routing problem.

root@werner ~]# route

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

64.84.15.208 * 255.255.255.248 U 0 0 0 eth0

169.254.0.0 * 255.255.0.0 U 0 0 0 eth0

It seems the second vms Destination is wrong as 64.84.15.208 is not one of my assigned ips or the address of the local network, however, I am not sure how to change it but when I did try I got "invalid argument" error.

These two vms are both on VMnetwork and attached to nic2, however, they show different MAC addresses for their internet adapters? I thought that they would have to have the same MAC as the MAC is the address for the hardware connecting the VMnetwork to the physical network.

1) is there something I have to do in VI CLient to add another computer to the VMnetwork and give it connectivity?

2) How come the vm1 can not even ping vm2 if they are both showing on VMnetwork?

3) Why does vm2 show 64.84.15.208 as destination and no gateway when I have 64.84.15.248 set as the local network and 64.84.15.249 as the gateway in the ifcnfg-eth0 file and have restarted network service many times.

Thanks in advance to anyone who offers a response.

Reply
0 Kudos
2 Replies
vm_arch
Enthusiast
Enthusiast

look at your subnet mask.

These two machines (without a router) will never see each other as the second one is outside the subnet of the first

a 255.255.255.248 SNM gives you a max of 8 ip addresses per subnet (with 6 considered 'useable')

I also note that the second doesnt have the default gateway - likely because it is outside the range that the default gateway on the first one can see.

Your range should be (I am guessing)... 64.84.15.248 - 64.84.15.255 (obviously the last is unuseable as it is a broadcast address)

therefore the machine sitting with 208 as the IP is not in that range of addresses and will not work.

Reply
0 Kudos
techmen8080
Contributor
Contributor

Super information it worked!

Thanks so much Vm-arch.

I changed the ip to xx..254 which is in the range you indicated and then the rest of the addresses were in the proper range to be accepted and not return a "invalid argument."

My second vm is now up on the network.

The only question I have now is how do I get my other three IPs 212,213,214

I seems I have to change to a subnet mask that will acommodate all of them?

Thanks again, Techmen

Reply
0 Kudos