On Sat, Nov 17, 2012 at 11:20 AM, Jeppe Øland <[email protected]> wrote:
> > Normally you should have rc.newwanip kick in here that does all the > magic. > > Either you did not leave enough time to the script to execute(iirc needs > ~10secs to kick in) or > > something happened preventing rc.newwanip from running. > > It's the usual story for me ... it just never works. > 2 weeks ago, I reinstalled 2.0.1 from scratch and manually created the > configuration. > > In this case, 6 minutes passed after WAN IP was obtained until I manually > restarted the monitoring. > The DynDNS update check didn't run either ... it ran via cron at 1:01, but > the automatic system just doesn't work for me. > > What in my config causes the problem? > Could it be because I use a VLAN for the WAN connection? > Could it be because I rename WAN to WAN1? > Nothing of your guesses. Normally the kick is performed during the dhclient-script run. There are two problems that may arise here: 1- check_reload_status was not running at the time(would be visible on logs that it is restarting since it has protection against that) 2- dhclient script did something wrong and exited before sending the notification. Normally 2- should be visible on logs afaik. > Regards, > -Jeppe > > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list > >
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
