Re: [Openstack] network problem

2013-01-03 Thread Ivan Kolodyazhny
Hi, What version of OpenStack do you use? Quantum or Nova Network? Regards, Ivan Kolodyazhny, Web Developer, http://blog.e0ne.info/, http://notacash.com/, http://kharkivpy.org.ua/ On Thu, Jan 3, 2013 at 9:11 AM, Umar Draz unix...@gmail.com wrote: Hi here is my setup 1) controller -

Re: [Openstack] network problem

2013-01-03 Thread Vishvananda Ishaya
Need a little more info: a) what does your nova.config look like? Specifically what is the setting for flat_interface? b) what command did you use to create your network? c) what is the output of brctl show? d) what is the output of ip addr show? Vish On Jan 2, 2013, at 11:11 PM, Umar Draz

Re: [Openstack] network problem

2013-01-03 Thread Umar Draz
Hi Vish Here is . Controller (nova.conf) network_manager=nova.network.manager.FlatDHCPManager force_dhcp_release=True dhcpbridge_flagfile=/etc/nova/nova.conf firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver my_ip=63.55.xx.x2 public_interface=eth0 vlan_interface=eth1

Re: [Openstack] network problem

2013-01-03 Thread Vishvananda Ishaya
Based on the below it could be : a) eth1 is not plugged in or b) eth1 is plugged into a switch that is filtering traffic in the 10.10.10.0/24 range or c) br100 is not bridged into eth1 (this would appear in brctl show which you didn't send) Vish On Jan 3, 2013, at 9:23 AM, Umar Draz

Re: [Openstack] network problem

2013-01-03 Thread Umar Draz
Hi Vish Here is the ifconfig output of *compute node* br100 Link encap:Ethernet HWaddr 00:50:56:b2:01:5f inet addr:10.10.10.3 Bcast:10.10.10.255 Mask:255.255.255.0 inet6 addr: fe80::c895:59ff:fe29:f708/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500

Re: [Openstack] network problem

2013-01-03 Thread Vishvananda Ishaya
You won't be able to ping the nodes from the controller since it has no ip address on the guest network. It looks like eth1 is bridged in properly on the compute node you showed, although I don't see it showing up in the interface list. It looks like maybe eth1 is not up? Try: ifconfig eth1

Re: [Openstack] network problem

2013-01-03 Thread Umar Draz
Hi Vish Here is updated output. root@compute1:~# ifconfig br100 Link encap:Ethernet HWaddr 00:50:56:b2:01:5f inet addr:10.10.10.3 Bcast:10.10.10.255 Mask:255.255.255.0 inet6 addr: fe80::30b0:a8ff:fefe:5a32/64 Scope:Link UP BROADCAST RUNNING MULTICAST

Re: [Openstack] network problem

2013-01-03 Thread Vishvananda Ishaya
Either your switch is dropping the packets or they are getting blocked by security group rules. You will have to do some tcpdump on various interfaces to figure out where the packets are getting dropped. Vish On Jan 3, 2013, at 11:07 AM, Umar Draz unix...@gmail.com wrote: Hi Vish Here is

Re: [Openstack] Network problem: Instances from non-nova-network can't reach outside

2011-12-28 Thread Alisson Soares Limeira Pontes
I am not sure why, but sharing the same Network Interface means these three subnets share the same range. Using the same subnet for Management and Storage network is common place and should not be an issue, but sharing the Public network subnet can be tricky.

Re: [Openstack] Network problem: Instances from non-nova-network can't reach outside

2011-12-28 Thread Vishvananda Ishaya
In some cases when everything is on one interface you need to set your main bridge to promisc mode to get it to forward properly. Try: ip link set promisc on br100 Vish On Dec 28, 2011, at 2:39 AM, Lucio Cossio wrote: Hello Guys, I'm testing a dual node installation of OpenStack Nova with