I have been having trouble getting dyndns working on a new m0n0wall I'm trying to deploy. I've searched the mailing lists and google in general, and I've found some similarities between my problem and some others, but I've found no answers. I'm hoping I can find some help here.
---------begin-novel-------------
I have two other m0n0walls deployed, and they have some dyndns weirdness, but in both cases it works. Here are edited excerpts from the logs of these two m0n0walls:
1st m0n0wall:
-------------
Apr 13 19:07:04 /kernel: CPU: i486 DX2 (486-class CPU)
Apr 13 19:07:04 /kernel: Origin = "GenuineIntel" Id = 0x435 Stepping = 5
Apr 13 19:07:04 /kernel: real memory = 67108864 (65536K bytes)
Apr 13 19:07:04 /kernel: avail memory = 48742400 (47600K bytes)
Apr 13 19:07:08 /usr/local/bin/ez-ipupdate[108]: ez-ipupdate Version 3.0.11b8, Copyright (C) 1998-2001 Angus Mackay.
Apr 13 19:07:08 /usr/local/bin/ez-ipupdate[108]: /usr/local/bin/ez-ipupdate started for interface ng0 host xxxxxxxx.homeip.net using server members.dyndns.org and service dyndns
Apr 13 19:07:08 /usr/local/bin/ez-ipupdate[108]: got last update xx.xx.xx.xx on 2007/04/10 22:58 from cache file
Apr 13 19:07:09 /usr/local/bin/ez-ipupdate[108]: failure to update ng0->xx.xx.xx.xx (xxxxxxxx.homeip.net)
Apr 13 19:07:59 /usr/local/bin/ez-ipupdate[108]: SIGHUP recieved, re-reading config file
Apr 13 19:07:59 /usr/local/bin/ez-ipupdate[108]: failure to update ng0->xx.xx.xx.xx (xxxxxxxx.homeip.net)
Apr 13 19:18:15 /usr/local/bin/ez-ipupdate[108]: successful update for ng0->xx.xx.xx.xx (xxxxxxxx.homeip.net)
2nd m0n0wall:
-------------
Apr 17 16:52:27 /kernel: CPU: Pentium II/Pentium II Xeon/Celeron (300.69-MHz 686-class CPU)
Apr 17 16:52:27 /kernel: Origin = "GenuineIntel" Id = 0x660 Stepping = 0
Apr 17 16:52:27 /kernel: real memory = 134152192 (131008K bytes)
Apr 17 16:52:27 /kernel: avail memory = 113905664 (111236K bytes)
Apr 17 16:52:28 /usr/local/bin/ez-ipupdate[95]: ez-ipupdate Version 3.0.11b8, Copyright (C) 1998-2001 Angus Mackay.
Apr 17 16:52:28 /usr/local/bin/ez-ipupdate[95]: /usr/local/bin/ez-ipupdate started for interface ng0 host xxxxxxxx.homeip.net using server members.dyndns.org and service dyndns
Apr 17 16:52:28 /usr/local/bin/ez-ipupdate[95]: got last update xx.xx.xx.xx on 2007/04/10 20:10 from cache file
Apr 17 16:52:28 /usr/local/bin/ez-ipupdate[95]: (xxxxxxxx.homeip.net) unable to resolve interface ng0
Apr 17 16:52:31 /usr/local/bin/ez-ipupdate[95]: SIGHUP recieved, re-reading config file
Apr 17 16:52:31 /usr/local/bin/ez-ipupdate[95]: failure to update ng0->xx.xx.xx.xx (xxxxxxxx.homeip.net)
Apr 17 16:57:31 /usr/local/bin/ez-ipupdate[95]: successful update for ng0->xx.xx.xx.xx (xxxxxxxx.homeip.net)
Note that in both cases, the first attempt to perform a dyndns update fails, but after one or more retries the update succeeds. Note also that the hardware is very different in each case. The 1st is a 486/DX66, the second is a 300MHz celeron.
I had experienced this problem with the 1st m0n0wall more than two years ago when I first deployed it. I noticed that it took more than 10 minutes after a reboot before I could reach the machine using the dyndns domain. I had posted the problem on the m0n0wall mailing list, and was told it was due to the fact that the start-up scripts run in parallel, and what was likely happening on my very slow 486 was that the ez-ipupdate process was running before my pppoe connection was establised. Without a simple solution (like imposing a short wait-time before ez-ipupdate runs on boot), I let it slide.
Strangely, my newly deployed 300MHz celeron runs into the same problem. Perhaps because it uses the cdrom boot image and a (slow) floppy for the config.xml file...?
Now, however, on a new m0n0wall deployment, I have a similar problem. Here's the log file:
3rd m0n0wall:
-------------
Apr 17 15:56:14 /kernel: CPU: Pentium/P54C (121.71-MHz 586-class CPU)
Apr 17 15:56:14 /kernel: Origin = "GenuineIntel" Id = 0x526 Stepping = 6
Apr 17 15:56:14 /kernel: real memory = 67108864 (65536K bytes)
Apr 17 15:56:14 /kernel: avail memory = 48746496 (47604K bytes)
Apr 17 15:56:14 /usr/local/bin/ez-ipupdate[94]: ez-ipupdate Version 3.0.11b8, Copyright (C) 1998-2001 Angus Mackay.
Apr 17 15:56:14 /usr/local/bin/ez-ipupdate[94]: /usr/local/bin/ez-ipupdate started for interface ng0 host xxxxxxxx.dyndns.org using server members.dyndns.org and service dyndns
Apr 17 15:56:14 /usr/local/bin/ez-ipupdate[94]: got last update xx.xx.xx.xx on 2007/04/17 15:09 from cache file
Apr 17 15:56:14 /usr/local/bin/ez-ipupdate[94]: (xxxxxxxx.dyndns.org) unable to resolve interface ng0
Apr 17 15:56:19 /usr/local/bin/ez-ipupdate[94]: SIGHUP recieved, re-reading config file
Apr 17 15:56:19 /usr/local/bin/ez-ipupdate[94]: failure to update ng0->xx.xx.xx.xx (xxxxxxxx.dyndns.org)
Apr 17 16:01:20 /usr/local/bin/ez-ipupdate[94]: failure to update ng0->xx.xx.xx.xx (xxxxxxxx.dyndns.org)
Apr 17 16:11:20 /usr/local/bin/ez-ipupdate[94]: failure to update ng0->xx.xx.xx.xx (xxxxxxxx.dyndns.org)
Apr 17 16:31:20 /usr/local/bin/ez-ipupdate[94]: failure to update ng0->xx.xx.xx.xx (xxxxxxxx.dyndns.org)
Apr 17 16:47:20 /usr/local/bin/ez-ipupdate[94]: received SIGQUIT, shutting down
Apr 17 16:47:22 /usr/local/bin/ez-ipupdate[224]: ez-ipupdate Version 3.0.11b8, Copyright (C) 1998-2001 Angus Mackay.
Apr 17 16:47:22 /usr/local/bin/ez-ipupdate[224]: /usr/local/bin/ez-ipupdate started for interface ng0 host xxxxxxxx.dyndns.org using server members.dyndns.org and service dyndns
Apr 17 16:47:22 /usr/local/bin/ez-ipupdate[224]: malformed cache file: /var/db/ez-ipupdate.cache
Apr 17 16:47:22 /usr/local/bin/ez-ipupdate[224]: successful update for ng0->xx.xx.xx.xx (xxxxxxxx.dyndns.org)
Note that the eventual success was due to my intervention in the GUI. I simply went to the dyndns services page and clicked save without making any changes. Without that intervention, I would see an endless string of 'failure to update' log entries.
As far as I can tell, there is nothing unique about the above log. At first I noticed '(xxxxxxxx.dyndns.org) unable to resolve interface ng0' and 'SIGHUP recieved, re-reading config file.' I did some googling and there was a hint that ez-ipupdate requires a SIGQUIT instead of SIGHUP. But the 2nd m0n0wall log above seems to refute that.
One thing seems clear however the SIGQUIT issued by manually click save on the dyndns services page leads to a success.
All three machines have been updated to 1.231
Any ideas? Anyone?
cheers,
jj
--------------end-novel-----------
|
Topic: more ez-ipupdate woes