Change Details

Similar to T5623, but my case is Clash, a VPN alternative, tun mode, wiki here but need a translator https://wiki.metacubex.one/config/inbound/tun/ On UBNT, I created a deb package, installing cfg mode nodes and other config templates and scripts under /config. I use config tree to store: * interface name so that PBR and firewall can be configured * disable status * subscription url and other config. Wiki here: https://github.com/sskaje/ubnt-clash/wiki/02.-%E9%85%8D%E7%BD%AE%E8%AF%B4%E6%98%8E The most important part is the interface name and making the interface be part of the PBR destination. During my recent works on WireGuard, I see VyOS uses XML for cfg/op nodes, to add a new node I have to add/edit current XMLs and rebuild whole vyos-1x, the cache update script doesn't work without xml and It's hard to edit the cached nodes. Here is my question or feature request: 1. Is there any way I can add custom node using a plugin liked deb instead of submit code to vyos-1x? 2. Can I just add a type of interfaces, maybe `set interfaces utunnel utunX` with only `address`, `description`, `disable` but do nothing? (The external program will create interfaces by itself, maybe add a `control-mode` = `external` to declare such behaviors)

Similar to T5623, but my case is Clash, a VPN alternative, tun mode, wiki here but need a translator https://wiki.metacubex.one/config/inbound/tun/ On UBNT, I created a deb package, installing cfg mode nodes and other config templates and scripts under /config. I use config tree to store: * interface name so that PBR and firewall can be configured * disable status * subscription url and other config. Wiki here: https://github.com/sskaje/ubnt-clash/wiki/02.-%E9%85%8D%E7%BD%AE%E8%AF%B4%E6%98%8E (I turned the repo to private mode for around 1 year because of possible law issues, I'll update some config I used in comments) The most important part is the interface name and making the interface be part of the PBR destination. During my recent works on WireGuard, I see VyOS uses XML for cfg/op nodes, to add a new node I have to add/edit current XMLs and rebuild whole vyos-1x, the cache update script doesn't work without xml and It's hard to edit the cached nodes. Here is my question or feature request: 1. Is there any way I can add custom node using a plugin liked deb instead of submit code to vyos-1x? 2. Can I just add a type of interfaces, maybe `set interfaces utunnel utunX` with only `address`, `description`, `disable` but do nothing? (The external program will create interfaces by itself, maybe add a `control-mode` = `external` to declare such behaviors)

Similar to T5623, but my case is Clash, a VPN alternative, tun mode, wiki here but need a translator https://wiki.metacubex.one/config/inbound/tun/ On UBNT, I created a deb package, installing cfg mode nodes and other config templates and scripts under /config. I use config tree to store: * interface name so that PBR and firewall can be configured * disable status * subscription url and other config. Wiki here: https://github.com/sskaje/ubnt-clash/wiki/02.-%E9%85%8D%E7%BD%AE%E8%AF%B4%E6%98%8E (I turned the repo to private mode for around 1 year because of possible law issues, I'll update some config I used in comments) The most important part is the interface name and making the interface be part of the PBR destination. During my recent works on WireGuard, I see VyOS uses XML for cfg/op nodes, to add a new node I have to add/edit current XMLs and rebuild whole vyos-1x, the cache update script doesn't work without xml and It's hard to edit the cached nodes. Here is my question or feature request: 1. Is there any way I can add custom node using a plugin liked deb instead of submit code to vyos-1x? 2. Can I just add a type of interfaces, maybe `set interfaces utunnel utunX` with only `address`, `description`, `disable` but do nothing? (The external program will create interfaces by itself, maybe add a `control-mode` = `external` to declare such behaviors)