@@ -44,7 +44,7 @@ void iplink_types_usage(void)
" ip6erspan | ip6gre | ip6gretap | ip6tnl |\n"
" ipip | ipoib | ipvlan | ipvtap |\n"
" macsec | macvlan | macvtap | netdevsim |\n"
- " netkit | nlmon | rmnet | sit | team | team_slave |\n"
+ " netkit | nlmon | pfcp | rmnet | sit | team | team_slave |\n"
" vcan | veth | vlan | vrf | vti | vxcan | vxlan | wwan |\n"
" xfrm | virt_wifi }\n");
}
@@ -249,6 +249,7 @@ ip-link \- network device configuration
.BR netdevsim " |"
.BR netkit " |"
.BR nlmon " |"
+.BR pfcp " |"
.BR rmnet " |"
.BR sit " |"
.BR vcan " | "
@@ -391,6 +392,9 @@ Link types:
.BR nlmon
- Netlink monitoring device
.sp
+.BR pfcp
+- Packet Forwarding Control Protocol device
+.sp
.BR rmnet
- Qualcomm rmnet device
.sp
@@ -2124,6 +2128,12 @@ the following additional arguments are supported:
.BI restart_count " RESTART_COUNT "
- GTP instance restart counter
+.TP
+PFCP Type Support
+For a link of type
+.I PFCP
+no additional arguments are supported
+
.in -8
.SS ip link delete - delete virtual link
Packet Forwarding Control Protocol is a 3GPP Protocol defined in TS 29.244 [1]. Add support for PFCP device type in ip link. It is capable of receiving PFCP messages and extracting its metadata (session ID). Its only purpose is to be used together with tc flower to create SW/HW filters. PFCP module does not take any netlink attributes so there is no need to parse any args. Add new sections to the man to let the user know about new device type. [1] https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3111 Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com> --- ip/iplink.c | 2 +- man/man8/ip-link.8.in | 10 ++++++++++ 2 files changed, 11 insertions(+), 1 deletion(-)