kabadisha / host-based-vpn-routing Goto Github PK

when adding the domains does it do filtering such as *.bamgrid.com or do you have to put analytics.clients.bamgrid.com in the rules file? Great script btw. Love the flexibility for my Merlin powered Asus router.?

Sorry not a question. Hopefully you will give an answer and I am not bothering you too much.

Some domains (like netflix.com) use DNS based load-balancing and so return different IPs each time you do a lookup.
This causes two issues:

1. That nslookup always gets different IPs and so the script will always think that IPs have changed.
2. That the IPs in VPN Director rules will be different to those in use by client devices that are using cached DNS lookups.

I'm not sure how to fix this right now. I'm experimenting with using the dig command instead of nslookup, but dig is not installed by default and so requiring it would make entware a prerequisite.

If you are worried about wearing out JFFS try using symlink and writing to ram. This will allow you constantly update websites that load balance for changes without worry about JFFS writes.

script_name=$(basename "$0")
ram_file_path="/var/vpndirector_rulelist"
jffs_path="/jffs/openvpn/vpndirector_rulelist"

if [ ! -L $jffs_path ]
then
  logger "$script_name: $jffs_path is not a symlink moving file to $ram_file_path and linking"
  mv $jffs_path $ram_file_path 
  ln -s $ram_file_path $jffs_path
elif [ $(readlink -f $jffs_path) != $ram_file_path ]
then
  logger "$script_name: remaking $jffs_path symlink to point to $ram_file_path"
  rm $jffs_path
  ln -s $ram_file_path $jffs_path
else
  logger "$script_name: no symlink change $jffs_path already points to $ram_file_path"
fi