Hi Stefan,
just because you asked...
On Thu, Jul 26, 2012 at 11:14:14PM +0200, Stefan Baur wrote:
Am 26.07.2012 22:45, schrieb Frank:
...
- if you *update* dyndns manually (curl, fetch, wget, whatever) every
10m - does /that/ work?
... because just using checkip does not give any
Am 27.07.2012 12:54, schrieb Frank:
- does ist still works, if you call /etc/rc.dyndns.update manually ?
Main difference between /etc/rc.dyndns.update and wget -O- ... is
that rc.dyndns.update uses the system config.
So: wget working and rc.dyndns.update not would indicate a config error.
But
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.
My only guess is that they're
On Thu, Jul 26, 2012 at 1:09 AM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
Still no luck. :-( Old IP shows up as red after the nightly IP change.
Crud, sorry to hear but unsurprised.
You mentioned a cron job for updating; are you hijacking pfSense built-in
functions for that or did
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
On Fri, Jul 27, 2012 at 2:44 AM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
Am 26.07.2012 22:45, schrieb Frank:
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.
Are
Am 26.07.2012 23:53, schrieb Nishant Sharma:
Are you running dual WAN setup with gateway failover by any chance?
Nope, single WAN, but in private IP space, as there is another router
above it.
-Stefan
___
List mailing list
List@lists.pfsense.org
Am 27.07.2012 01:16, schrieb Jeppe Øland:
On Thu, Jul 26, 2012 at 2:14 PM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
- 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,
On Thu, Jul 26, 2012 at 4:25 PM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
There's got to be more in the log than just that!
Nope, there isn't... but...
Exactly from there:
Do me a favor and see if you maybe by accidend checked the disable
And GH, it seems that I hit that disable
Hi Stefan,
you are in Germany - right?
i suggest:
most DSL-Providers spend you a firm IP-Address if you ask.
Most times it will cost you just the phone call. some will bill you 5 €.
So no more dynamic dns needed. no hussle, no troubles.
HTH
greetings
m.
2012/7/25 Stefan Baur
Am 25.07.2012 18:02, schrieb Michael Schuh:
Hi Stefan,
you are in Germany - right?
i suggest:
most DSL-Providers spend you a firm IP-Address if you ask.
Most times it will cost you just the phone call. some will bill you 5 €.
So no more dynamic dns needed. no hussle, no troubles.
HTH
Sadly,
On Wed, Jul 25, 2012 at 9:55 AM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
*/5 * * * * root/usr/bin/nice -n20
/etc/rc.dyndns.update
would solve my issues. However, it does not work (any more?).
When I log in to the GUI, I see the IP displayed in red,
On Wed, Jul 25, 2012 at 10:19 AM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
I thought there was a maximum allowable frequency (e.g. 10 minutes)
for hitting checkip.dyndns.org, but can't currently find documentation
of that.
The limit is for hitting the update server, not for hitting
Am 25.07.2012 18:24, schrieb RB:
On Wed, Jul 25, 2012 at 10:19 AM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
I thought there was a maximum allowable frequency (e.g. 10 minutes)
for hitting checkip.dyndns.org, but can't currently find documentation
of that.
The limit is for hitting
On Wed, Jul 25, 2012 at 10:32 AM, Stefan Baur
newsgroups.ma...@stefanbaur.de wrote:
Okay, indeed it says so there (and I've updated my crontab accordingly).
Thanks for pointing that out.
Not a problem, the problem you outline is of interest to me because I
even see DDNS update issues having a
Am 25.07.2012 23:30, schrieb Fuchs, Martin:
I also had many problems and since I use noip now, the problems have gone...
It's still the case that dyndns updates sometimes work and sometimes not :-(
I *am* using no-ip, however, pfSense uses the checkip.dyndns.org server
to check for the
16 matches
Mail list logo
