Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tabbed-router configs addition Mikrotik #449

Conversation

abclution
Copy link

@abclution abclution commented Dec 31, 2019

Added script for Mikrotik routers, works with ipv4/ipv6

@abclution
Copy link
Author

Not sure I'm doing this correctly. Be gentle, I'm a noob

} else={
:log info "IPv6 address doesn't match for $DDNSHostname , updating..." ;
:put "IPv6 address doesn't match for $DDNSHostname, updating..." ;
/tool fetch url="https://$DDNSHostname:$DDNSSecret@ipv6.nsupdate.info/nic/update" keep-result=no ;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you need to evaluate the http return code of this and switch local state as needed. please have a look at the dyndns "standard" about this.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haven't had time to work on this again, its on my todo.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you fix this meanwhile?

I think it would be nice if we showed a config for microtik, but evaluation of the return code as defined by the standard is a requirement (needed so update client does not DoS the dyndns service in case something is going wrong / is misconfigured).

@ThomasWaldmann
Copy link
Member

Looks like this does not get updated to correctly implemented the dyndns standard (which includes reasonable reaction to return http error codes).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants