Re: [ovs-discuss] network problem with vxlan

2014-05-23 Thread t22330033
ated between controller node and > compute node, VM on compute node is not getting DHCP traffic from > controller node, which means the tunnel is not passing any traffic yet. > > > > Dennis Qin > > > > *From:* discuss [mailto:discuss-boun...@openvswitch.org] *On Behalf Of *

Re: [ovs-discuss] network problem with vxlan

2014-05-21 Thread t22330033
2014-05-22 10:20 GMT+08:00 t22330033 : > > 2014-05-21 0:25 GMT+08:00 Qin, Xiaohong : > > Can you session into dhcp namespace to run tcpdump on that tap interface >> to see if the dhcp traffic is been exchanged between dns process and VM? >> >> > tcpdump in the d

Re: [ovs-discuss] network problem with vxlan

2014-05-21 Thread t22330033
ed by neutron are all set to secure. it that the root cause? > > > Dennis > > > > *From:* discuss [mailto:discuss-boun...@openvswitch.org] *On Behalf Of * > t22330033 > *Sent:* Tuesday, May 20, 2014 12:20 AM > *To:* discuss@openvswitch.org > *Subject:* Re: [ovs-disc

Re: [ovs-discuss] network problem with vxlan

2014-05-20 Thread t22330033
2014-05-19 23:58 GMT+08:00 Qin, Xiaohong : > You have to start with the dhcp problem first in your case. “ip netns” on > your controller node should list a dhcp name space, > > > > ip netns > > qdhcp-3fc234e5-335f-463d-ba1d-bcf1bdd8f479 > > qrouter-6df76d30-17fc-4024-8d01-4cfe007ab531 > > > > then

[ovs-discuss] network problem with vxlan

2014-05-19 Thread t22330033
I set up openstack with one control node and one compute node with vxlan. my problem is that the instance in compute node always failed to get IP address by DHCP. I checked ovs flows and cannot figure out what the problem is. here is what I saw $ovs-vsctl show Manager "tcp:172.22.11.43:6640"