<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.m-8016192397370997854m-1031823028067138837hoenzb
{mso-style-name:m_-8016192397370997854m-1031823028067138837hoenzb;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Following along with Scott’s thoughts, I have a Vagrant project at <a href="https://github.com/rburkholder/vagrant">https://github.com/rburkholder/vagrant</a> which I use for testing various kernels, openvswitch versions, and configurations.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The OVN test setup provides the ability to configure and connect multiple guests, much like mininet does. And with Vagrant’s snapshot ability, it is easy to rollback and redo tests.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>So…. if you run out of luck on getting what you want in mininet, there is that alternate mechanism in VirtualBox and you don’t have to re-invent the wheel to get started.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> ovs-discuss-bounces@openvswitch.org [mailto:ovs-discuss-bounces@openvswitch.org] <b>On Behalf Of </b>Michael Ben-Ami via discuss<br><b>Sent:</b> Friday, January 13, 2017 12:21<br><b>To:</b> O'Reilly, Darragh <darragh.oreilly@hpe.com><br><b>Cc:</b> ovs-discuss@openvswitch.org<br><b>Subject:</b> {Disarmed} Re: [ovs-discuss] VXLAN support in OVS 2.5.0<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>I'm in a very similar boat as Shravan. The utility for me is to be able to test flow sets on arbitrary mininet topologies that simulate real world topologies that may or may not use VXLAN. The root cause as I see it is that mininet must put all OVS bridges in the same namespace. This is probably an OVS limitation not mininet. Has been discussed a little here: <a href="https://mail.openvswitch.org/pipermail/ovs-discuss/2015-September/038543.html">https://mail.openvswitch.org/pipermail/ovs-discuss/2015-September/038543.html</a><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Of course you could start mininet itself in different namespaces, but that defeats a lot of the purpose of building topologies within a mininet.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Shravan, if you find a workable solution please let me know.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thanks,<o:p></o:p></p></div><div><p class=MsoNormal>Michael<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Fri, Jan 13, 2017 at 7:07 AM, O'Reilly, Darragh <<a href="mailto:darragh.oreilly@hpe.com" target="_blank">darragh.oreilly@hpe.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Not sure what you are trying to do. But if you just want to connect two bridges on the same host, then you can use patches or veths.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>But if you really want to use vxlan, then maybe the loopback (lo <a href="http://127.0.0.1/8" target="_blank"><font color="red"><b>MailScanner has detected a possible fraud attempt from "127.0.0.1" claiming to be</b></font> <b><span style='color:red'>MailScanner warning: numerical links are often malicious:</span></b> 127.0.0.1/8</a>) can be used, something like this:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>ovs-vsctl add-br br0</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>ovs-vsctl add-port br0 vxlan0 -- set interface vxlan0 type=vxlan options:local_ip=127.1.1.1 options:remote_ip=127.2.2.2</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>ovs-vsctl add-br br1</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>ovs-vsctl add-port br1 vxlan1 -- set interface vxlan1 type=vxlan options:local_ip=127.2.2.2 options:remote_ip=127.1.1.1</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span><o:p></o:p></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> <a href="mailto:ovs-discuss-bounces@openvswitch.org" target="_blank">ovs-discuss-bounces@openvswitch.org</a> [mailto:<a href="mailto:ovs-discuss-bounces@openvswitch.org" target="_blank">ovs-discuss-bounces@openvswitch.org</a>] <b>On Behalf Of </b>Shravan S K<br><b>Sent:</b> 13 January 2017 10:21</span><o:p></o:p></p><div><div><p class=MsoNormal><br><b>To:</b> Scott Lowe <<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>><br><b>Cc:</b> <a href="mailto:ovs-discuss@openvswitch.org" target="_blank">ovs-discuss@openvswitch.org</a><br><b>Subject:</b> Re: [ovs-discuss] VXLAN support in OVS 2.5.0<o:p></o:p></p></div></div></div></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>My motive is to simulate VXLAN functionality on a bigger topology using mininet.<br>My plan - As Mininet uses OVS bridges to simulate vswitch functionality, we can use ovs-vsctl to configure VXLAN functionality on the bridges. I thought let me try for a simple topology without using Mininet and just using OVS on a single host and 2 VMs. If it works, then I can make a similar configuration for a bigger topology using mininet. <o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>OVS on a single host and 2 VMs : vm1-----br1-------br2-----vm2 <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I am confused on how to perform the vxlan config for the above setup. <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>If the above one works, I could try on the mininet topologies. <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>For the mininet topology ( --topo=linear,2 )<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>h1 ----- s1 ------ s2 -------- h2 (h1,h2 are hosts, s1,s2 are switches - actually ovs bridges)<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><b>$ ovs-vsctl show </b><br>ad172f01-511d-46fe-9022-d23de31e06e2<br> Bridge "s2"<br> Controller "ptcp:6635"<br> fail_mode: standalone<br> Port "s2-eth2"<br> Interface "s2-eth2"<br> Port "s2"<br> Interface "s2"<br> type: internal<br> Port "s2-eth1"<br> Interface "s2-eth1"<br> Bridge "s1"<br> Controller "ptcp:6634"<br> fail_mode: standalone<br> Port "s1-eth2"<br> Interface "s1-eth2"<br> Port "s1"<br> Interface "s1"<br> type: internal<br> Port "s1-eth1"<br> Interface "s1-eth1"<br> ovs_version: "2.5.0"<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>In the mininet console,<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><b>mininet>net</b><br>h1 h1-eth0:s1-eth1<br>h2 h2-eth0:s2-eth1<br>s1 lo: s1-eth1:h1-eth0 s1-eth2:s2-eth2<br>s2 lo: s2-eth1:h2-eth0 s2-eth2:s1-eth2<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>As the vxlan configuration part is related to OVS, I am asking in this forum, rather than the mininet forum. <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks. <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br clear=all><o:p></o:p></p><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Shravan<o:p></o:p></p></div></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On 13 January 2017 at 11:08, Scott Lowe <<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I would still echo Raymond's suggestion: use VirtualBox to create two "hosts" running OVS and connect them via a VXLAN tunnel over standard VBox networking. You can use network namespaces (as Justin suggested) on the VMs running OVS to simulate connecting to OVS since VBox doesn't support nested virtualization.<o:p></o:p></p></div><div id="m_-8016192397370997854m_-1031823028067138837AppleMailSignature"><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div><div id="m_-8016192397370997854m_-1031823028067138837AppleMailSignature"><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>You can take a look at <<a href="https://github.com/lowescott/learning-tools" target="_blank">https://github.com/lowescott/learning-tools</a>> to see if there is a Vagrant environment I've already created that might help you in this situation.<o:p></o:p></p></div><div id="m_-8016192397370997854m_-1031823028067138837AppleMailSignature"><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#888888'><br>-- </span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#888888'>Scott</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#888888'> </span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#888888'>Sent from my mobile device</span><o:p></o:p></p></div></div><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><br>On Jan 12, 2017, at 9:46 PM, Shravan S K <<a href="mailto:sra9449@gmail.com" target="_blank">sra9449@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>I know that. But I wanted to experiment with OVS bridges first, and then if it worked I wanted to re-create the config for a larger topology using Mininet(which uses OVS bridges(for switches) using OVS).<o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br clear=all><o:p></o:p></p><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Shravan<o:p></o:p></p></div></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On 13 January 2017 at 08:06, Raymond Burkholder <<a href="mailto:ray@oneunified.net" target="_blank">ray@oneunified.net</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Try running VirtualBox, and build two guests with shared networking. That will get you an appropriate simulation of computer to computer vxlan mechanisms.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> </span><o:p></o:p></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> <a href="mailto:ovs-discuss-bounces@openvswitch.org" target="_blank">ovs-discuss-bounces@openvswitch.org</a> [mailto:<a href="mailto:ovs-discuss-bounces@openvswitch.org" target="_blank">ovs-discuss-bounces@openvswitch.org</a>] <b>On Behalf Of </b>Shravan S K<br><b>Sent:</b> Thursday, January 12, 2017 22:34<br><b>To:</b> Scott Lowe <<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>><br><b>Cc:</b> <a href="mailto:ovs-discuss@openvswitch.org" target="_blank">ovs-discuss@openvswitch.org</a><br><b>Subject:</b> Re: [ovs-discuss] VXLAN support in OVS 2.5.0</span><o:p></o:p></p></div></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p>Because of lack of hardware, I'm trying a vxlan setup on a single computer. <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On 13-Jan-2017 04:47, "Scott Lowe" <<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'>Please don't drop the list.<br><br>Before we go down that path, can you help me understand what you're<br>trying to achieve by building a VXLAN tunnel between two VMs on the same<br>host?<br><br><br><br>On 01/12/2017 10:15 AM, Shravan S K wrote:<br>> I am not sure how to do the config for what you said.<br>> Can you please explain how to configure the setup that you're suggesting ?<br>><br>> Shravan<br>><br>> On 12 January 2017 at 02:17, Scott Lowe <<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a><br>> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>>> wrote:<br>><br>> On 01/11/2017 03:54 AM, Shravan S K wrote:<br>> > Like this?<br>> > vm01-------------------|<br>> > |------------------vm03<br>> ><br>> > br1(vxlanport1)------------br-int1=================br-int2----------(vxlanport2)br2<br>> > vm02-------------------|<br>> > |-------------------vm04<br>> ><br>> > What is the need for the bridges br-int1 and br-int2? Why is it not<br>> > possible without them(as the topology shown earlier in this thread)?<br>><br>><br>> [SL] No, I don't think this is the configuration you'd want to use. The<br>> "br-int" bridges aren't strictly required; you could use br1 and br2.<br>> The trick here---as you're trying to create a VXLAN tunnel within a<br>> host---would be that you'll need 2 IP endpoints (one for each end of the<br>> tunnel), and you'd need each bridge with a VXLAN port to be associated<br>> with one of those IP endpoints.<br>><br>> As I said, though, I haven't tested a configuration like this. Further,<br>> to be honest, I'm not really sure what you're trying to accomplish with<br>> such a configuration.<br>><br>><br>> > Shravan<br>> ><br>> > On 11 January 2017 at 11:59, Scott Lowe <<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>><br>> > <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>>>> wrote:<br>> ><br>> > Please see my response inline, prefixed with [SL].<br>> ><br>> ><br>> > On 01/10/2017 09:50 PM, Shravan S K wrote:<br>> >> I am asking if that can be done on a single physical host having<br>> >> OVS. Say, as mininet creates bridges which act as switches. Can<br>> >> vxlan be setup using Mininet?<br>> ><br>> ><br>> > [SL] I don't know if it's possible for Mininet to set up VXLAN;<br>> > that's a question best asked on a Mininet-related forum.<br>> ><br>> > As for whether it can be done on a single host, I suppose if you were<br>> > to use 2 separate bridges for physical connectivity along with 2<br>> > separate bridges for the tunnels, it might work. I've never tried it,<br>> > though, so this is just conjecture.<br>> ><br>> ><br>> >> Shravan<br>> >><br>> >> On 10 January 2017 at 23:33, Scott Lowe <<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>><br>> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>>><br>> >> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a><br>> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a><br>> <mailto:<a href="mailto:scott.lowe@scottlowe.org" target="_blank">scott.lowe@scottlowe.org</a>>>>> wrote:<br>> >><br>> >> Please see my response below.<br>> >><br>> >><br>> >> On 01/10/2017 02:26 AM, Shravan S K wrote:<br>> >>> Is it possible to create a VXLAN setup using just bridges created<br>> >>> by OVS? (using ovs-vsctl to create these bridges,ports and vxlan<br>> >>> config)<br>> >>><br>> >>> vm01-------------------| |------------------vm03<br>> >>> br1-------br2<br>> >>> vm02-------------------| |-------------------vm04<br>> >><br>> >><br>> >> Yes, this is possible. On each hypervisor where OVS is running and<br>> >> where you have VMs you'd like to connect over VXLAN tunnels, create<br>> >> a bridge ("br-tun", for example). Create and configure a VXLAN port<br>> >> appropriately on br-tun on each hypervisor, and then connect your<br>> >> VMs. You should be good to go. My website has an example of doing<br>> >> this with GRE; VXLAN should be nearly identical.<br>> >><br>> >> Hope this helps,<br>><br>><br>> --<br>> Scott<br>><br>><br>><o:p></o:p></p></blockquote></div></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#888888'><br>-- <br>This message has been scanned for viruses and <br>dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is <br>believed to be clean. </span><o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:#888888'><br><span class=m-8016192397370997854m-1031823028067138837hoenzb>-- </span><br><span class=m-8016192397370997854m-1031823028067138837hoenzb>This message has been scanned for viruses and </span><br><span class=m-8016192397370997854m-1031823028067138837hoenzb>dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is </span><br><span class=m-8016192397370997854m-1031823028067138837hoenzb>believed to be clean. </span></span><o:p></o:p></p></div></blockquote></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div></blockquote></div></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>_______________________________________________<br>discuss mailing list<br><a href="mailto:discuss@openvswitch.org" target="_blank">discuss@openvswitch.org</a><br><a href="https://mail.openvswitch.org/mailman/listinfo/ovs-discuss" target="_blank">https://mail.openvswitch.org/mailman/listinfo/ovs-discuss</a><o:p></o:p></p></div></blockquote></div></blockquote></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p></div></div></div></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>discuss mailing list<br><a href="mailto:discuss@openvswitch.org">discuss@openvswitch.org</a><br><a href="https://mail.openvswitch.org/mailman/listinfo/ovs-discuss" target="_blank">https://mail.openvswitch.org/mailman/listinfo/ovs-discuss</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><br>-- <br>This message has been scanned for viruses and <br>dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is <br>believed to be clean. <o:p></o:p></p></div></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>