ip-tunnel connection types should allow custom device name
When bringing up an ip-tunnel
type connection on the command line the command is something to the effect of:
ip tunnel add mytunnel mode sit ...
With NetworkManager if the ip-tunnel
device for mode sit
isn't named sitN
, the interface name is rejected if it doesn't already exist. It appears that validate_activation_request
only looks for _connection_is_vpn
to allow devices that don't exist. It seems that 'VPN-like' connections that have virtual interfaces should allow their interface names to be more descriptive than sit1
, sit2
, etc.