Using a powerful dns name for a VPN server

I’ve had a few periods where I’ve desired to create a protected tube between 2 destinations but have only had relationships with powerful IP details to perform with.

Sure it’s simple enough to create a powerful dns program for each wireless router, but how about getting one to hook up again to the other on its new IP address?

This little program can be used for just that.

1	:local "vpn-interface-name" "pptp-interface"

2	:local "vpn-dns-name" "your_dynamic_address"

3	:local "new-vpn-ip" [:resolve $"vpn-dns-name"]

4	:local "current-vpn-ip" [/interface pptp-client get $"vpn-interface-name" connect-to]

5	:if ($"current-vpn-ip" != $"new-vpn-ip") do={ /interface pptp-client set [find name=$"vpn-interface-name"] connect-to=$"new-vpn-ip"}

How it works

First of all you need to

1. Make this as a new program, name it and installation a scheduler entrance for how often you want it to run. I discover 10 moments performs excellent for me.

2. Modify the factors in the program to match (your_dynamic_address = the dns name for the distant wireless router, pptp-interface = your pptp customer program name)

Thoughts

This kind of program performs for more than just a pptp relationship.
The same concept can be used to EoIP channels, IPSec channels, etc etc.

The program will then examine if the present IP for the dns name suits up with the IP you have set on the pptp customer program.

If it does go with the program prevents without doing anything (leaving the pptp relationship intact)

If it does not go with the program will upgrade the program to go to the new IP deal with.

Posted by Unknown on Minggu, 25 Maret 2012 - Rating: 4.5

Title : Using a powerful dns name for a VPN server
Description : I’ve had a few periods where I’ve desired to create a protected tube between 2 destinations but have only had relationships with powerful IP...

Tweet