[ovs-discuss] 回复: a question about the interface type change

Ben Pfaff blp at ovn.org
Fri Mar 15 02:01:45 UTC 2019


Please don't drop the mailing list.

OVS supports changing interface types, but it's not going to delete an
existing tap device for the purpose of creating an internal device with
the same name.

On Fri, Mar 15, 2019 at 12:17:26AM +0000, pei Jikui wrote:
> Thanks for your help.
> 
> When I tried to change a system interface to internal type, the following result occurs. Does that mean that we could not change an interface's type in OVS?
> 
> 1) There is no error hint in cli.
>     "ovs-vsctl set interface tap11 type=internal".
> 
> 2) The interface tap11 could not be list in the output of "ovs-dpctl show" anymore.
> 
> 3) output of "ovs-vsctl show" indicates there is something wrong with the interface tap11.
>     [root at localhost ~]# ovs-vsctl show
> 9d6ac6bb-ea06-489f-b7f6-b681cd617b1e
>     Bridge "ovs0"
>         Port "tap11"
>             Interface "tap11"
>                 type: internal
>                 error: "could not add network device tap11 to ofproto (No such device)"
>         Port "ovs0"
>             Interface "ovs0"
>                 type: system
>     ovs_version: "2.10.1"
> 
> 
> 
> 
> 发送自 Outlook<http://aka.ms/weboutlook>
> 
> ________________________________
> 发件人: Ben Pfaff <blp at ovn.org>
> 发送时间: 2019年3月15日 0:46
> 收件人: pei Jikui
> 抄送: ovs-discuss at openvswitch.org
> 主题: Re: [ovs-discuss] a question about the interface type change
> 
> On Thu, Mar 14, 2019 at 03:12:03PM +0000, pei Jikui wrote:
> > I have a question regarding to the ovs' interface type.
> >
> > For example, we have added an port tap1 into the ovs bridge as the default type of interface, system as designed.
> > The command line is " ovs-vsctl add-port br0 tap1"
> > If we change the interface tap1's type to internal via the command link "ovs-vsctl set interface tap1 type=internal".
> 
> This will try to create a system internal device called tap1.  It won't
> work properly because there's already a system tap device named "tap1"
> and will thus cause a name conflict.  Thus, it's a bad idea and unlikely
> to do anything useful.


More information about the discuss mailing list