<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
</head>
<body>
Thank you for the help.<br>
<br>
发送自 Outlook
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>发件人:</b> Ben Pfaff <blp@ovn.org><br>
<b>发送时间:</b> 2019年3月19日 4:32:22<br>
<b>收件人:</b> pei Jikui<br>
<b>抄送:</b> ovs-discuss@openvswitch.org<br>
<b>主题:</b> Re: 回复: [ovs-discuss] a question regarding to tap internal interface</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">I think that "tap" is just the name of the interface in that case. I<br>
don't know why it is named "tap".<br>
<br>
On Sat, Mar 16, 2019 at 11:27:21PM +0000, pei Jikui wrote:<br>
> Ben,<br>
> <br>
> Thanks much for your reply.<br>
> <br>
> My confusion comes from the openstack's official document of <a href="https://docs.openstack.org/liberty/networking-guide/scenario-classic-ovs.html">
https://docs.openstack.org/liberty/networking-guide/scenario-classic-ovs.html</a><br>
> <br>
> As illustrated in the picture, we can see that the interface used to connect ovs and dhcp-netns is a tap interface. While from the output of "ovs-vsctl show", it indicates that the type of interface is internal. That confuses me much.<br>
> <br>
> I am thinking that the tap interface is for the name of the interface instead of the type of the interface?<br>
> <br>
> Thanks<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> 发送自 Outlook<<a href="http://aka.ms/weboutlook">http://aka.ms/weboutlook</a>><br>
> <br>
> ________________________________<br>
> 发件人: Ben Pfaff <blp@ovn.org><br>
> 发送时间: 2019年3月17日 1:44<br>
> 收件人: pei Jikui<br>
> 抄送: ovs-discuss@openvswitch.org<br>
> 主题: Re: [ovs-discuss] a question regarding to tap internal interface<br>
> <br>
> On Sat, Mar 16, 2019 at 11:24:34AM +0000, pei Jikui wrote:<br>
> > hi,<br>
> ><br>
> > 1) From the openstack documents, we know that for the tenant's dhcp functionality, the usage is to connect a dhcp netns to the ovs using a tap interface.<br>
> > At the same time, the ovs-vsctl show that the tap interface is a type of internal interface for OVS.<br>
> <br>
> This is wrong. Tap and internal are different kinds of interfaces.<br>
> What does ovs-vsctl show that makes you confuse the two?<br>
> <br>
> > While I could not add a tap type interface to ovs as an internal type of interface for OVS.<br>
> ><br>
> > The commands I used,<br>
> > a) ip tuntap add dev tap0 mode tap.<br>
> > b) ovs-vsctl add-port ovs0 tap0 -- set inteface tap0 type=internal<br>
> <br>
> These commands are wrong. If you create a tap interface, you must not<br>
> tell ovs-vsctl that it is an internal interface.<br>
> <br>
> What led you to believe that these commands were correct?<br>
> <br>
> > error: "could not add network device tap12 to ofproto (No such device)"<br>
> ><br>
> > 2) My questions are ,<br>
> > a) how to add a tap interface to OVS and set it as internal type of interface of OVS?<br>
> <br>
> You cannot. That is not possible.<br>
<br>
<br>
</div>
</span></font></div>
</body>
</html>