tap device will have the type of empty string. This was nothing wrong.
If you really want to try vxlan feature, try ip netns for vm creation.

On Nov 21, 2014 12:41 AM, Ben Pfaff <[email protected]> wrote:

On Thu, Nov 20, 2014 at 03:58:18PM +0800, zhangwqh wrote:
> I met a problem. I want to firstly create a tap device. I used the
> tool tunctl to create the tap device, After that, I attached the
> interface to openvswitch bridge. When check the type, the type is
> empty string.

That's fine and expected.

> From the man 5 ovs-vswitchd.conf.db,
>
>
>  type: string
>               The interface type, one of:
>
>
>               system An  ordinary  network  device,  e.g.  eth0  on Linux.  Sometimes referred to as ''external interfaces'' since they are generally connected to hardware
>                      external to that on which the Open vSwitch is running.  The empty string is a synonym for system.

Note the final sentence above.

>  it seems that after attaching to bridge, the type is system
>  type. Usually the physical ethernet port is system type. When I want
>  to send the packets to vxlan device from the tap device I created
>  using tunctl(I have set a flow entry from tap device to vxlan
>  device), I found that the tap device dropped all of the packets. Can
>  anybody give me some advices why this happens?

I don't know, because I don't have enough information, but the interface
type is not what you should focus on.
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to