It is actually supported for LWT-based tunnels since commit:
2fd3d5eda508 ("dpif-netlink-rtnl: Support layer3 GRE")
We even have system tests for it in system-layer3-tunnels.at.
The commit in the 'Fixes' tag only made sense for the non-LWT
implementation in vport-gre module, but failed to express that in the
documentation. Since it's not the way to configure tunnels for a very
long time now, there is no point in clarifying the documentation, it's
easier to just remove the claim.
Fixes: 0277582178a1 ("vswitchd: Update documentation for legacy_l3 type
packets")
Signed-off-by: Ilya Maximets <[email protected]>
---
vswitchd/vswitch.xml | 6 ------
1 file changed, 6 deletions(-)
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index b7a5afc0a..9f60b90dc 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -3165,12 +3165,6 @@
represented as Ethernet frames for compatibility with legacy
OpenFlow controllers that expect this behavior.
</li>
- <li>
- The <code>legacy_l3</code> option is only available via the
- user space datapath. The OVS kernel datapath does not support
- devices of type ARPHRD_IPGRE which is the requirement for
- <code>legacy_l3</code> type packets.
- </li>
<li>
If this option is <code>ptap</code>, the tunnel sends and
receives any kind of packet. Open vSwitch represents packets in
--
2.53.0
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
