Config dependency using subdirectories.

[phoenixxl]

Hello.

First for a description of my current setup to make some context: My regular network setup for most computers is a 2 nic setup . one nic where file transfers and the bulk of network traffic runs over , and a second nic where low latency low bandwidth stuff runs over . For a few computers a few floors down I can only use 1 nic , so I have a second virtual nic on those using openvpn to connect to the second network. On all those computers I also have a third network (openvpn) that comprises all the computers in our whole extended family , that way the 3 computer literate family members we have can help out aunts uncles etc , we also have shared photo albums and the likes on there. On top of that , I personally use a vpn service to connect to BBC Iplayer and a few other services abroad which also uses openvpn.

Ok , now for the actual request.

Would it be feasable to change openvpn so it starts and stop it's connections using a dependency tree that's based on directories?

Example of what I mean.

Let's say I have a connection to the internet that's using an openvpn tap device called InetConn and gets started with inetconn.conf that's located in /etc/openvpn/config . I also have a connection to my workplace on a tun called workConn. And I also have a small vpn server running on my desktop at work so only 1 port would need to be open on said desktop instead of leaving multiple ports open on the computer's firewall (security).
In this situation , using what I describe above , openvpn would have a config dir looking like this:

/etc/openvpn/config/InetConn.conf (file)
/etc/openvpn/config/InetConn (directory)
/etc/openvpn/config/InetConn/workConn.conf (file)
/etc/openvpn/config/InetConn/workConn (directory)
/etc/openvpn/config/InetConn/workConn/workdesktopConn.conf (file)

When openvpn starts , it would try and start Inetconn. Only if inetconn is connected and running , the content of the inetconn directory would be read , checked for conf files and only then a connection to workConn would try and be made. Once connected there workdesktopconn would be tried.

Then when a branch gets disconnected , the connected branches would automatically close their connections as well. dependent connections would not needlessly keep trying to make connections if the dependent connection isn't active.

Would making a hierarchy like this be feasible ?
Is this something inherently flawed with a structure like this?
Any musings or discussion regarding this or any other setup that's dependency based welcome.

Friendly Regards
Phoenixxl

[phoenixxl]

It's been over a year since I posted this ..
Is this forum really the right place to approach these matters ?

Regards.