<div dir="ltr"><div><div>Hello, Amir.<br><br></div>I have had exactly the same problem some time ago. Please see a description and possible solution at <a href="https://ask.openstack.org/en/question/68671/centos7-rdo-vxlan-tcp-segment-losses/" target="_blank">https://ask.openstack.org/en/question/68671/centos7-rdo-vxlan-tcp-segment-losses/</a> (you should check statistics at L2 and L3 interfaces using ethtool -S and ip -s commands before applying proposed WA).<br><br></div>BR, Alexey Stupnikov.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 12, 2015 at 12:00 PM, Amir Huskić <span dir="ltr"><<a href="mailto:amir.huskic@gmail.com" target="_blank">amir.huskic@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>vxlan/gre port is not created in br-tun Kilo. I'm using PC with two NICs, running Ubuntu 14.04 LTS and Devstack skript for Kilo installation (single node setup). </div><div><br></div><div><div>My goal is to enable L2 connectivity between VMs (vxlan/gre network) on Kilo and external Linux host. </div><div>Eth0 is used for br-ex and LAN connectivity. That part is fine. I can ping and ssh to VMs using their floating IP. </div><div>Eth1 should be used for vxlan/gre tunnel connection between Kilo node and Linux external node that have vxlan/gre interfaces.</div></div><div><br></div><div>eth0: 192.168.123.1</div><div>eth1: 192.168.100.254</div><div>VMs internal: 192.168.10.x</div><div>Linux external host vxlan/gre tunnel: 192.168.10.10, eth0 192.168.50.10 </div><div><br></div><div><div>amir@openstack:~/devstack$ sudo ovs-vsctl show</div><div>c2020516-3b76-4b8c-8fa6-110fcb4fd5e3</div><div> Bridge br-tun</div><div> fail_mode: secure</div><div> Port patch-int</div><div> Interface patch-int</div><div> type: patch</div><div> options: {peer=patch-tun}</div><div> Port br-tun</div><div> Interface br-tun</div><div> type: internal</div><div> Bridge br-int</div><div> fail_mode: secure</div></div><div><br></div><div>When I try to ping from VMs to external Linux host using L2 network segment (192.168.10.5 -> 192.168.10.10) I can see using tcpdump that packets are coming only to br-int. When I try to ping from Linux external host to VMs using L2 network segment (192.168.10.10 -> 192.168.10.5) ping packets are coming to eth1 but not also to br-tun.<br></div><div><br></div><div>I can add vxlan/gre port to OVS manually but nothing change and also tried with vxlan and gre but result is the same. </div><div><br></div><div>Here are my configuration files and CLI output (ifconfig, ip a, OVS bridges/ports status, etc): <a href="https://dl.dropboxusercontent.com/u/4298410/Openstack_vxlan.zip" target="_blank">https://dl.dropboxusercontent.com/u/4298410/Openstack_vxlan.zip</a></div><div><br></div><div>What I'm doing wrong? </div><div><br></div><div>Thank you.</div><div>Regards,</div><div>Amir</div><div><br></div></div>
<br>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">BR, Alexey Stupnikov.<br></div></div>
</div>