Am 26.07.2012 22:45, schrieb Frank:
Hi Stefan,
On Thu, Jul 26, 2012 at 09:09:35AM +0200, Stefan Baur wrote:
Am 25.07.2012 18:36, schrieb RB:
However, repeatedly firing off
fetch -q -o - http://checkip.dyndns.org | sed 's/^.*Current IP Address:
\(.*\)<\/body>.*$/\1/'
within the same minute doesn't error out, so it doesn't look like a limit
that's enforced by dyndns.
Just some thoughts:
- what does your log say about dyndns?
Nothing that would look helpful:
check_reload_status: Updating all dyndns
is the only message containing the string "dyn", and it only appears
once during startup.
- are there messages about cron-errors in the logs
(maybe invisable special character, ..)
Nope. Would be hard to mess that up, anyways, when using the built-in vi
to change that single line (it's not like I'm using Microsoft Word to
edit the crontab...).
- if you *update* dyndns manually (curl, fetch, wget, whatever) every
10m - does /that/ work?
... because just using checkip does not give any information
about if or if not the *update* works when periodically executed
I'm not getting what you're trying to prove or disprove with that. Care
to explain? Fact is, triggering the update by refreshing the DynDNS
page in the WebGUI works.
- does ist still works, if you call /etc/rc.dyndns.update manually ?
Depends on what you mean with "works". I can call the script and it
doesn't error out, *but*, it does *not* update the IP. My guess is that
it is trying to check whether or not the WAN IP has changed using its
local means (comparing the current interface IP with a previously stored
value) and *not* using checkip.dyndns.org. However, I don't know which
part of the code is responsible for that. Pointers greatly appreciated.
I'm too much of a sysadmin and not enough of a coder to figure that
out on my own.
- do some brute-force debugging :)
- replace /etc/rc.dyndns.update by an own script. See if it's called
Rather than doing that, I just added some log code to the existing
script. It shows up in the System Log every 10 minutes, as scheduled.
- tcpdump the connection with the dyndns Server, analyze dump
pfSense is said to use checkip.dyndns.org for IP checking even when
using no-ip as the dynamic DNS provider. Which one should I be looking
for, the attempt to communicate with checkip.dyndns.org or the attempt
to update the record with no-ip?
-Stefan
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list
