[ previous ] [ next ] [ threads ]
 From:  Joey Morin <jmorin at icomm dot ca>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  m0n0 on a slow pc
 Date:  Fri, 27 Aug 2004 14:39:37 -0400 (EDT)
i have a friend set up with m0n0 1.1b16 on a 486DX2/66 with 32MB RAM.
works just great (yes, i know, "anything less than 64MB and you're on your
own).  one slight problem right now, not critical... just curious...

i have him set up with dynamic ip through dyndns.org, so i can do remote
admin for him without having to know his IP, and it works fine, except for
right after a reboot.  looking at the logs, i see that the ez-ipupdate
tries twice at boot time to perform the update, and fails both times.  it
then tries again 10 minutes later and succeeds.

a further examination of the logs shows that during the frist two
boot-time attempts, dnsmasq has not yet completed its own boot-time
duties, therefore i postulate that this is the reason ez-ipupdate fails:
it can't yet resolve members.dyndns.org

i figure this is becuase:
	a) some boot-time operations are backgrounded, in this case
	   specifically dnsmasq
	b) a 486DX2/66 with 32MB RAM is too slow to allow dnsmasq to
	   complete it's boot-time duties before ez-ipupdate is started

as i said, this doesn't seem to be a problem since ez-ipupdate sleeps for
10 minutes after the boot-time failures and tries again, succeeding.

just curious, am i right about a) above?  and if i am, is there a reason
to do it this way?  would it break things to serialize the boot tasks?  i
guess it might slow things down, but it may also allow m0n0 to run more
reliably on older hardware.  that's one of the big reasons i like it to
begin with...