If you remove an L2TPv3 interface, commit shows an iproute2 error but succeeds.
vyos@vyos# delete interfaces l2tpv3
[edit]
vyos@vyos# commit
[ interfaces l2tpv3 l2tpeth0 ]
Unknown command: 11
Usage: ip l2tp add tunnel
remote ADDR local ADDR
tunnel_id ID peer_tunnel_id ID
[ encap { ip | udp } ]
[ udp_sport PORT ] [ udp_dport PORT ]
Usage: ip l2tp add session [ name NAME ]
tunnel_id ID
session_id ID peer_session_id ID
[ cookie HEXSTR ] [ peer_cookie HEXSTR ]
[ offset OFFSET ] [ peer_offset OFFSET ]
[ l2spec_type L2SPEC ]
ip l2tp del tunnel tunnel_id ID
ip l2tp del session tunnel_id ID session_id ID
ip l2tp show tunnel [ tunnel_id ID ]
ip l2tp show session [ tunnel_id ID ] [ session_id ID ]
Where: NAME := STRING
ADDR := { IP_ADDRESS | any }
PORT := { 0..65535 }
ID := { 1..4294967295 }
HEXSTR := { 8 or 16 hex digits (4 / 8 bytes) }
L2SPEC := { none | default }Despite the threatening message, the bug is purely cosmetic since L2TPv3 interface actually gets successfully deleted.
The root cause is missing tunnel_id keyword in ip l2tp del command in the script.
delete:
ip link set $VAR(@) down
if [ -n "$VAR(./tunnel-id/@)" ] && [ -n "$VAR(./session-id/@)" ]; then
ip l2tp del session tunnel_id $VAR(./tunnel-id/@) session_id $VAR(./session-id/@)
fi
if [ -n "$VAR(./tunnel-id/@)" ]; then
ip l2tp del tunnel tunnel_id $VAR(./tunnel-id/@)
fiThe command inside the second conditional does its job fine, which raises a question whether the first part is redundant. The idea clearly was to remove sessions associated with tunnel before removing the tunnel, but I'm not sure if it really was ever needed. Perhaps L2TPv3 behaviour was different in 1.0.x times.