Openstack Instances are not pinging when they are in different network - openstack

I have created two network in openstack (Hawana -ubuntu 12.04 LTS) (192.168.1.0/28, 192.168.1.16/28) and both network have their instances. Instances can ping the gateway of another network
but instance can not ping another instance in that network.
for example Network one: 192.168.1.0/28 gateway is 192.168.1.1 and Instance ip 192.168.1.2
network two: 192.168.1.16/28 gateway is 192.168.1.17 and instance ip is 192.168.1.18
now 192.168.1.18 machine can ping 192.168.1.1 but not 192.168.1.2
please tell me the exact problem of it.

The two networks (subnets, actually) should be connected via a single router for instances on the networks to reach each other.
And as #Brenne mentioned, ICMP packets (ping) have to be explicitly enabled in the security group. By default, they are not allowed.

Related

How to identify which network interface is used for a given route?

I am on a Windows 10 machine. I have got the below routes configured in my machine.
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.5 1
10.1.0.0 255.255.0.0 192.168.2.1 192.168.2.5 1
10.2.0.0 255.255.0.0 192.168.3.1 192.168.3.5 1
When ping IP 10.1.1.1, I want to determine which network interface will be used to route the traffic.
Is there any network utility that can help me find the correct route based on the destination IP?
If you ping 10.1.1.1, it will use the interface with the IP 192.168.2.5 looking at your route table.
You can also use tracert 10.1.1.1 to see what route your network traffic will take.

How to ping instance's internal network from Host on Devstack

I am running Devstack on my machine and i would like to know if it is possible to ping an instance from Host. The default external network of Devstack is 172.24.4.0/24 and br-ex on Host has the IP 172.24.4.1. I launch an instance using the internal network of Devstack (192.168.233.0/24) and the instance gets the IP 192.168.233.100. My Host's IP is 192.168.1.10. Is there a way to ping 192.168.233.100 from my Host? Another thing i thought is to boot up a VM directly to the external network (172.24.4.0/24) but the VM does not boot up correctly. I can only use that network for associating floating IP's.
I have edited the security group and i have allowed ICMP and SSH, so this is not a problem.

Bridged networking - VMs ping issue

I'm working with KVM/VirtualBox and OVS. I have two bridges on a host machine, br0 and br1. A VM is connected to br0. The VM is able to ping br0 but it is also able to ping br1, to which it is not connected. Also, I made an iperf server on the VM and a client on the host machine and when I gave the ip of br0 a connection was made and data was transferred but when I gave the ip of br1 a connection was made but no data was able to transfer. All ips are contained in the same subnet. Can someone explain what is happening?
I can explain on "why br1 address is pingable". This is because in linux when packet is treated as "local-delivery" packet it is received in common point, where source interface is not important. So packet to ANY local interface may be received from any network interface.

CentOS - Wrong automatic ifconfig broadcast address

Running a Centos 5.11 machine with two network cards.
One is facing the internal network (private IP), the other the Internet (public IP).
Because we had some issues lately with it (ARP collision - but that's not the point here!), I started verifying its config. And I find out the broadcast set for the public IP is wrong.
IP is xxx.xxx.xxx.25
Subnet is 255.255.255.240
So basically we should have:
Network xxx.xxx.xxx.16
First IP xxx.xxx.xxx.17
Last IP xxx.xxx.xxx.30
Broadcast xxx.xxx.xxx.31
But the broadcast is automatically set to last host xxx.xxx.xxx.30
If I change it using command line, it is reseted back to the same IP once I do a service network restart...
I had to edit /etc/sysconfig/network-scripts/ifcfg-eth0 for the broadcast to stick to what I wanted.

How to setup a bridge connection with vbox/vmware using a second wan ip on a dedicated server

I am using a dedicated server with a certain wan ip / netmask / gateway / nameservers.
I got a second wan ip to use with virtualbox i installed on the server.
I want to use bridge connection in virtualbox because i use some "servers" in it and want them to be able to be seen from internet .
I created a virtual network interface on the server and assigned the second ip to it.
It works , meaning i can ping that ip from outside.I setup virtualbox to bridge to that interface but i am stuck at what settings i have to set up in the virtual guest so everything will work.
Second ip has netmask 255.255.255.255 so i assume its a single ip situation and probably using gateway and nameservers of the server because i was given none of them with it.
I have to mention that first ip and second ip are not in the same subnet , nor is the gateway (e.g. XX.YY.ZZ.WW , ZZ is different between first , second and gateway ip)
Thanks in advance.
You have to unbind TCP and all other protocols and services on the hosts NIC that you want to use in VBox. After that, you can configure a bridged network connection using that interface. After that, you can set the IP and network settings in your virtual system. This has also been addressed in this post: https://serverfault.com/questions/136969/dedicate-a-nic-to-a-virtualbox-vm

Resources