not sure about that, why do you need this?

hacki

hi there,

standing in front of the same issue.
has already someone a working solution?

greets

hi there,

standing in front of the same issue with dynamic ip adresses and ipsec.
has already someone running such a scenario?

greets

HI, I don't have ppp in my ROS. ppp is configured in my router. I have a static IP in my ROS eth0 like 192.168.1.x. If this parameter is not specified, the best IP address the server can determine will be used (some proxy configurations pass the IP in a header, and that is detected by the server). ...

glad to hear!

to complete it, i added the script to the wiki.

I'm not sure, but i think dynDNS will ban you for some time if you update so often. try to input the following commands in your terminal and poste the output /ip route find dst-address=0.0.0.0/0 active=yes /ip route get <your ppp Interface> routing-mark /ip route get <your ppp interface interface /i...

sry, not sure for that

the http mode won't support user authentification in your version.
your fetch just can auth over ftp

it seems your fetch version won't support usernames in http-mode.
you could try the fetch command with the url tag instead of the address tag.

the address tag was added in version 3.23, so you have to update your box

i set the entry in the gui without \r\n and the script wasn't executed. after adding them it worked so i thought, could be helpful too

please make "/system scheduler export" and paste it here. the execute command should be with "" like "/system script run dynDNS\r\n" you have a whitespace between S and \r, perhaps this is your issue. you can add the following line on top of the script in order to check...

have you added the scheduler job in gui or commandline?

it's important to add the \r\n characters, otherwise the command is not executed

these are the only variables.
what happens if you run the script manually: /system script run dynDNS
have you set the scheduler?

do you have a firewall rule?
a nat rule doesn't have an action like accept or deny.

something like this could help
add action=accept chain=input comment="Access" disabled=no dst-port=\
22 in-interface=pppoe-out1 protocol=tcp

source NAT translates the source address (e.g. a private lan wants internet access, the private - source address has to be translated to an public address) destination nat translates the destination address (e.g. you have a server with a private ip behind a wan connection, you have to forward(transl...

in order to support dyndns i took some parts from the changeip script and made it work for. 1) add a script called dynDNS: # Define User Variables :global ddnsuser "DYNDNSUSER" :global ddnspass "DYNDNSPASS" :global ddnshost "DYNDNSHOST" # Define Global Variables :global...

you could add nat in the changeip script. e.g. like this: :if ($ddnsip != $ddnslastip) do={ :log info "DDNS: Sending UPDATE!" :log info [ :put [/tool dns-update name=$ddnshost address=[:pick $ddnsip 0 [:find $ddnsip "/"] ] key-name=$ddnsuser key=$ddnspass ] ] /ip firewall nat set...