[ovs-discuss] GRE over IPv6 configuration

Eli Britstein elibr at mellanox.com
Tue Jun 18 05:45:44 UTC 2019


On 6/18/2019 1:22 AM, Gregory Rose wrote:
>
> On 6/12/2019 2:20 AM, Eli Britstein wrote:
>> Could you please have a look (and even better try?) still need to 
>> tidy up
>>
>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Felibr-mellanox%2Flinux%2Ftree%2Fovs-ipv6-gre&data=02%7C01%7Celibr%40mellanox.com%7C25425e700b58418b19fa08d6f37253ae%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636964069686971905&sdata=Ki55ZQGwQKNNDkB4PZ1zpk9aqC42TXbt5WT%2F86SDauo%3D&reserved=0 
>>
>>
>>
>
> Hi Eli,
>
> I finally managed to getting around and building your kernel.  At 
> least it does do away with the protocol error message but
> I haven't gotten it working yet.  Stay tuned and I'll provide feedback.

Hi Greg,

I think William was right pointing out the comment from Pravin. I agree 
with them that if we can avoid changing the kernel, and support it via 
lib/dpif-netlink-rtnl.c, it is the way to go, and we should abandon the 
kernel changes.

I haven't deep dived into it yet to see how ip6erspan works (at least no 
creation error, didn't run traffic though) and ip6gre doesn't.

Furthermore, I think the following is missing, as there is no ip6gretap, 
only ip6gre:

diff --git a/lib/dpif-netlink-rtnl.c b/lib/dpif-netlink-rtnl.c
index 2e23a8c14..08084abb7 100644
--- a/lib/dpif-netlink-rtnl.c
+++ b/lib/dpif-netlink-rtnl.c
@@ -104,7 +104,13 @@ vport_type_to_kind(enum ovs_vport_type type,
      case OVS_VPORT_TYPE_IP6ERSPAN:
          return "ip6erspan";
      case OVS_VPORT_TYPE_IP6GRE:
-        return "ip6gre";
+        if (tnl_cfg->pt_mode == NETDEV_PT_LEGACY_L3) {
+            return "ip6gre";
+        } else if (tnl_cfg->pt_mode == NETDEV_PT_LEGACY_L2) {
+            return "ip6gretap";
+        } else {
+            return NULL;
+        }

>
> And thanks for realizing this gap in tunneling coverage for ip6 gre.  
> Slipped the cracks it did.
Thank you for investing more of your time with it.
>
> - Greg
>


More information about the discuss mailing list