There is a default check around 1h01 am, for an IP change ?
/usr/bin/nice -n20 /etc/rc.dyndns.update
Why is this there, and can I safely remove it ?
I do a pppoerestart around 4AM, and have rescheduled the above rule
around 4h04... but this seems to give me no advantage (instead an
entry in the logfile that the IP address hasn't changed (guess doing a
pppoerestart initiates the dyndns.update itself).
In my case, might it be a better choice to do an update around 1PM
instead ?
Today I had an issue using dyndns, it couldn't reach
"members.dyndns.org" - and only the pfsense boxes were affected
somehow ??
Was there an issue today with dyndns ? Can I install a dyndns server
myself ??
It seems that I have again a DYNDNS problem... I now have scheduled a
1PM resync, but the VPN won't come up now (until 1PM has passed I guess).
I know you get kicked off, of Dyndns if you refresh the ip too many...
but now I have to wait for about 1,5 hours until 1PM passes.
Is there another solution available ??
Would OpenVPN be better for my dynamic IP !?
If I read the book, I'm not sure on what to go for... OpenVPN or IPSEC...
I used IPSEC a lot, because of the commercial routers being used in the
"mix"... but now being equipped with multiple pfSense's... I'm guessing
on trying OpenVPN instead.
What are your recommendations ?
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
