MikroTik

ros code

/ interface pppoe-client {
	:global ExternalIP
	:local clientip
	:local clientstatus
	:while (1 < 2) do={
		monitor pppoe-out1 once do={:set clientip $"local-address"; :set clientstatus $status}
		:if ($clientstatus="connected" and $ExternalIP!=$clientip) do={
			:delay 1  
			:log info "UpdateDuckDNS: IP change detected - $ExternalIP to $clientip. Updating Duck DNS."
			/tool fetch mode=https url="https://www.duckdns.org/update?domains= ... =$clientip" dst-path=duckdns.txt;
			:delay 1
			:local result [/file get duckdns.txt contents]
			:log info "UpdateDuckDNS: Duck DNS update result: $result";
			:set ExternalIP $clientip
		}
		:delay 5
		}
}

...when you have debugged "all the problem" and the program is near vital to you...

...when you have debugged "all the problem" and the program is near vital to you...

7 days I agree is too soon to allow users to transition, but if the service is "vital", then it is probably worth paying for. Just remember that what they are providing does cost them money.

Yes, ok, cost money, but is no reasonable only 7 days for migration of 40 machine.
This is a ransom....

Yes, ok, cost money, but is no reasonable only 7 days for migration of 40 machine.
This is a ransom....

40 machines? If you are saying there are 40 different hostnames then you are violating the DynDNS free account terms anyway. You are only permitted to have 1 free account, and each account only allows 1 or 2 hostnames I believe.

This script runs differently to almost all other Mikrotik dynamic DNS update scripts I have found on the Net. The usual method is to have the script run at intervals. Whereas my script runs all the time, monitors the WAN connection, and detects if the IP address changes. Not saying this is a better way, it is just the way I have done it.
So therefore, when setting it up in the Mikrotik scheduler, set it to run at startup only.

This script will only work with a PPPoE connection. If you have the energy, please make a script that works with ethernet.

Thanks

The logging facility is added in complete version.

This is the complete script, without the interruption to explain what's happen:

This is the complete script, without the interruption to explain what's happen:

Code: Select all

:global actualIP value=[/ip address get [find where interface=MATRIX] value-name=address];
:global actualIP value=[:pick $actualIP -1 [:find $actualIP "/" -1] ];
:if ([:len [/file find where name=ipstore.txt]] < 1 ) do={
 /file print file=ipstore.txt where name=ipstore.txt;
 /delay delay-time=2;
 /file set ipstore.txt contents="0.0.0.0";
};
:global previousIP value=[/file get [find where name=ipstore.txt ] value-name=contents];
:if ($previousIP != $actualIP) do={
 :log info message=("Try to Update DuckDNS with actual IP ".$actualIP." -  Previous IP are ".$previousIP);
 /tool fetch mode=https keep-result=yes dst-path=duckdns-result.txt address=[:resolve www.duckdns.org] port=443 host=www.duckdns.org src-path=("/update?domains=ww.matrix.it&token=65843E27-A491-429F-84A0-30A947E20F92&ip=".$actualIP);
 /delay delay-time=5;
 :global lastChange value=[/file get [find where name=duckdns-result.txt ] value-name=contents];
 :global previousIP value=$actualIP;
 /file set ipstore.txt contents=$actualIP;
 :if ($lastChange = "OK") do={:log warning message=("DuckDNS update successfull with IP ".$actualIP);};
 :if ($lastChange = "KO") do={:log error message=("Fail to update DuckDNS with new IP ".$actualIP);};
};

Remember to add Karma if you find this info useful...
Thanks..

Hi - when I try to use this, it appears that there is another private address between the my Mikrotik router and the internet. So it returns a private address. Any other way I can do this?

/tool fetch mode=http http-method=get url=http://icanhazip.com/ dst-path=myip.txt

Hi - when I try to use this, it appears that there is another private address between the my Mikrotik router and the internet. So it returns a private address. Any other way I can do this?

You could get your Ip this way:

Code: Select all

/tool fetch mode=http http-method=get url=http://icanhazip.com/ dst-path=myip.txt

But honestly, does it make sense to register duckdns when your router is behind a NAT?
-Chris

:local resolvedIP [:resolve "{{ domain }}.duckdns.org"];
:local currentIP [/ip address get [find interface="{{ interface }}"] address];
:local currentIP [:pick $currentIP 0 [:find $currentIP "/"]];

:if ($resolvedIP != $currentIP) do={
    :log info ("Trying to update DuckDNS with actual IP ".$currentIP.", resolved IP is ".$resolvedIP);
    :local response [/tool fetch url=("https://www.duckdns.org/update?domains={{ domain }}&token={{ token }}&ip=".$currentIP) check-certificate=yes as-value output=user];
    :if ($response->"status" = "finished") do={
        :if ($response->"data" = "OK") do={
            :log info ("Successfully updated DuckDNS with new IP ".$currentIP);
        } else={
            :log error ("Failed to update DuckDNS with new IP ".$currentIP);
        }
    }
}

• replace the variables in double curly braces
• make the root certificate used to sign DuckDNS's certificate chain available in the certificate store either by downloading it from here or using Mozilla's list of trusted root certificates from here. The certfile should be downloaded on a trusted computer and uploaded to the router from there. It can be imported in Winbox under System > Certificates or using the
  Code: Select all

  /certificate import file-name={{ certfile }} passphrase=""

  command. Once the certificate store is bootstrapped, it can be periodically updated with the following script:
  
  Code: Select all

  /tool fetch url=https://mkcert.org/generate/ check-certificate=yes dst-path=cacert.pem;
  /certificate import file-name=cacert.pem passphrase="";
  

  This step could be skipped by omitting
  Code: Select all

  check-certificate=yes

  from the fetch command, but I discourage it as it makes the connection less secure.

Code: Select all

:local resolvedIP [:resolve "{{ domain }}.duckdns.org"];
:local currentIP [/ip address get [find interface="{{ interface }}"] address];
:local currentIP [:pick $currentIP 0 [:find $currentIP "/"]];

:if ($resolvedIP != $currentIP) do={
    :log info ("Trying to update DuckDNS with actual IP ".$currentIP.", resolved IP is ".$resolvedIP);
    :local response [/tool fetch url=("https://www.duckdns.org/update?domains={{ domain }}&token={{ token }}&ip=".$currentIP) check-certificate=yes as-value output=user];
    :if ($response->"status" = "finished") do={
        :if ($response->"data" = "OK") do={
            :log info ("Successfully updated DuckDNS with new IP ".$currentIP);
        } else={
            :log error ("Failed to update DuckDNS with new IP ".$currentIP);
        }
    }
}