I will consider this, I can probably just build in an automatic check for IPv6 being enabled. Additionally, I will look into a post-fix function that will delete IPv6 queried IPs if IPv6 is not enabled from the policy files.
This may be something I could collaborate with @Viktor Jaep on as his tool is geared more towards VPN Monitoring while this tool is specifically geared towards Domain / VPN routing.
Happy to look at this to determine its viability? Would you be able to share the contents of one of these .conf files? I need to understand what's going on... And why do you have to manually change to a different VPN? Reasoning?
Essentially Viktor, the policy is created with a specific OVPN Client assigned to it and if there is an issue with that client, the created IP Rules / Routes don't have a recreation or failover to another VPN Client, this is the functionality being requested.
Wouldn't you be able to just create a policy for each VPN client? Then if one turns off, the other turns on, the policy is there ready to go? Forgive my ignorance, but I don't have any familiarity with how this works. LOL
There is an edit policy function to change the used interface which will change the routes on the fly but there is no automated method of this, essentially because that would involve performing VPN Monitoring / failover.
There is only a single .conf file called domain_vpn_routing.conf:
Have you tried using the edit policy function? It will update the routing instantly.
Yes, of course, it works manually just fine. Not complaining there, but as I said, just clicking on VPN director really should work hand-in-hand (I hope)
Since VPNMON-R2 isn't really part of the picture here, I would probably suggest coming up with a little script in the openvpn-event file that updates that conf file, and populates the right ovpnc# in there? I think that would do the trick? Then, each time the VPN slot changes, it writes the correct # to the file? Thoughts @Ranger802004?
I agree, actually now that I think about this more, this will only solve MY issue. Others maybe using this script to route different traffic over different interfaces so it may break for them. Maybe a toggle on/off for "Dynamic Interface Detection" YES/NO. Yes will work for me and no will work for others who do multi interface routing? Just a thought. Thank you both to what you are doing here. I love this script so far.
Thank you! I don't use the ipv6 and after updating and restarting the script, the ipv6 addresses were removed. Everything works, nothing broke!
Here's a little Proof-of-concept... but you get the idea. This needs to be placed in your "/jffs/scripts/openvpn-event" file... You would need to edit the path to your .conf file so that it's correct... but then "theoretically", each time your VPN slot changes and the route comes up, it will modify your "domain_vpn_routing.conf" file to reflect the correct ovpnc#. Not quite sure if the vpn routing script needs a kickstart after this... but hopefully this gets you a little closer.
#!/bin/sh
confpath="/jffs/scripts/domain_vpn_routing.conf"
[ "${dev:0:4}" = 'tun1' ] && vpn_id=${dev:4:1} && [ "$script_type" = 'route-up' ] && sed -i "s/ovpnc./ovpnc$vpn_id/" "$confpath" &
#PoC
#vpn_id=2
#sed -i "s/ovpnc./ovpnc$vpn_id/" "$confpath"I would recommend to leave both, all they do is execute query policies and make sure cron job is scheduled if an event occurs. With the lock file only one instance will run if they are both triggered.
You know, you were actually onto something, I think a 2nd policy with the other interface will work. It will just have lower priority than the higher interface in the IP Rules but if the main one is down then it will work.
