On Thu, Jun 20, 2019 at 12:23 PM Eli Britstein <[email protected]> wrote: > > > On 6/20/2019 9:19 PM, William Tu wrote: > >> I'll be working on clarifying the documentation. And we need to clarify > >> that we will not be supporting ip6gre because it > >> requires ARPHRD_IP6GRE. OVS only works with ARPHRD_ETHER so it can only > >> support ip6gretap. > >> > >>> Alternatively, we can maybe detect the options:remote_ip to be an > >>> IPv4/IPv6 address in type=gre and do the proper adjustments behind the > >>> scenes. > >>> > >>> What do you think? > > But when users set type=gre, and underneath we might created gre or > > ip6gretap. > > I think it better makes it clear using ip6gretap or gre. > > In gre we use "gre" for both "gre" or "gretap", so we should maybe use > "ip6gre" and not "ip6gretap", though "ip6gre" is not supported but only > "ip6gretap". BTW, can't OVS be updated to support it as well in the future?
Yes, we can do that. First we need to upstream to netdev to add ARPHRD_IP6GRE support in ovs_netdev_link() at net/openvswitch/vport-netdev.c. Then we backport to OVS compat kernel module. For this patch, let's fix the ip6gretap first. > > In any case, I think documentation should be updated in the same commit. > Agree, I will update the vswitchd/vswitch.xml in next version Thanks! William _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
