What would you say if in future ROS releases the developers added pre-up= pre-down= for wireguard and for /ppp/profile/add on-up= on-down=
In Wireguard, by default, the configuration file already has the ability to use scripts using PreUp, PostUp, PreDown, PostDown.
This would expand the functionality and capabilities, for example, the L2TP/IPSec client would execute the port-knocking script before connecting to the server in pre-up and, accordingly, its IP would be included in a special address list on the server, which would allow connecting to the VPN server.
This functionality is very much lacking and it suggests itself.
Similar to this request is to add to the Wireguard “Peer” configuration a new parameter of “metric”. Currently, when configuring a Wireguard tunnel, one dynamic route is created. And this route entry has everytime a metric of 0. This could be a problem in case we’ve configured multiple tunnels, and we want to assign different metric for each one. In other devices (i.e. OpenWRT) this option exists. The only change is that optionally the user could add the metric value and this value will be used when creating the route entry.
I really need to configure the METRIC value of the Wireguard tunnels. We need it to maintain multiple tunnels using different pathes. And we want to prioritize some pathes over others. Therefore, any idea to support this?