Hi,
According to 3gpp 29.281, TEIDs used in a GTPU tunnel could be different in
"up" and "down" direction. At EMnify we depend on this feature.
We developed a patch but it changes API in incompatible ways, excerpt:
@@ -38,8 +39,9 @@ define gtpu_add_del_tunnel
vl_api_interface_index_t mcast_sw_if_index;
u32 encap_vrf_id;
u32 decap_next_index;
- u32 teid;
- option vat_help = "src <ip-addr> { dst <ip-addr> | group <mcast-ip-addr> {
<intfc> | mcast_sw_if_index <nn> } } teid <teid> [encap-vrf-id <nn>]
[decap-next <l2|nn>] [del]";
+ u32 src_teid;
+ u32 dst_teid;
+ option vat_help = "src <ip-addr> { dst <ip-addr> | group <mcast-ip-addr> {
<intfc> | mcast_sw_if_index <nn> } } src-teid <teid> dst-teid <teid>
[encap-vrf-id <nn>] [decap-next <l2|nn>] [del]";
};
Prior to submitting the patch I'd like to find out if it affects other people
using GTPU and what would be the preferred way forward.
Best,
Nick
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15561): https://lists.fd.io/g/vpp-dev/message/15561
Mute This Topic: https://lists.fd.io/mt/71569677/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
