It seemed like a good idea at the time.
Using IP Cloud to resolve to currently used Dynamic WANIP.
However, IP Cloud address, is no longer accessed once the resolving occurs and thus when the IP address changes, the netwatch rule is invalid.
Has anyone else noted this issue or did I configure incorrectly??
Does the same hold true for Firewall Address Lists where one can put in IP cloud for vice an IP address?
Re: NETWATCH & IP CLOUD
To quote a master of this forum: viewtopic.php?f=13&t=173857#p850834
Also please move your local IP Address from ether2 to BRIDGE!! IT IS WRONG TO KEEP IT ON ETHER2!!!
lol.
Now, ontopic, Tool/Netwatch holds IP Addresses in the host field, if you try to add a hostname from CLI, you'll get this:
However, if you try that from WinBox, the host you enter will be resolved ONCE, and the resulting IP will get added to the netwatch entry in the host field, that's it, no further resolving. Unless you use a script to update it.
Now, Firewall Address Lists can also keep hostnames, hostnames will be resolved again and again when the TTL of those hostnames expire, as it should.
Also please move your local IP Address from ether2 to BRIDGE!! IT IS WRONG TO KEEP IT ON ETHER2!!!
lol.
Now, ontopic, Tool/Netwatch holds IP Addresses in the host field, if you try to add a hostname from CLI, you'll get this:
Code: Select all
invalid value for argument host:
invalid value for argument ip-address
invalid value for argument ipv6-address
Now, Firewall Address Lists can also keep hostnames, hostnames will be resolved again and again when the TTL of those hostnames expire, as it should.
Re: NETWATCH & IP CLOUD
Kk as I though netwatch is incompatible with ip cloud thanks!
Who is online
Users browsing this forum: JesusMarino, RBrogen and 141 guests