[ovs-dev] Question about gretap0 and erspan0 and ip6tnl0 creation

Gregory Rose gvrose8192 at gmail.com
Thu Oct 4 20:09:11 UTC 2018


On 10/4/2018 11:16 AM, Jin, Liang via dev wrote:
> Hi ovs-dev,
> After we upgrade ovs 2.10, we found some interface created, why they are created even in bridge scenario?   is it possible not to create them when upgrading?  Is this a bug in ovs 2.10?
>
> 24: gretap0 at NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN mode DEFAULT group default qlen 1000
>      link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 25: erspan0 at NONE: <BROADCAST,MULTICAST> mtu 1446 qdisc noop state DOWN mode DEFAULT group default qlen 1000
>      link/ether 12:0e:f1:ea:1d:e0 brd ff:ff:ff:ff:ff:ff
> 26: gre0 at NONE: <NOARP> mtu 1476 qdisc noop state DOWN mode DEFAULT group default qlen 1
>      link/gre 0.0.0.0 brd 0.0.0.0
> 27: ip6gre0 at NONE: <NOARP> mtu 1448 qdisc noop state DOWN mode DEFAULT group default qlen 1
>      link/gre6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
> 28: ip6tnl0 at NONE: <NOARP> mtu 1452 qdisc noop state DOWN mode DEFAULT group default qlen 1
> link/tunnel6 :: brd ::

This is not a bug - it is intended operation.   They're required as the 
FB devices for the newly added ipv6 gre tunneling and  ipv4/ipv6 ERSPAN 
features.

Why do you not want them created?

- Greg

>
>
> Thanks
> L.J.
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev



More information about the dev mailing list