[leaf-user] NTP not working (webconf)

2005-12-01 Thread Darcy Parker (Home)
Good day all,

Quick question re ntpdate.lrp package.  When monitoring from webconf
I see it is always stopped.  When I hit the start button I get the
following error

Daemon Status
  Running start command ...
Running ntpdate to synchronize clock.

The command failed.  Usually this is due to an
error in the configuration file.

ntpdate is: stopped   

Here is the configurations file. (/etc/default/ntpdate)
# servers to check.   (Separate multiple servers with spaces.)
NTPSERVERS=timelord.uregina.ca
#
# additional options for ntpdate
#NTPOPTIONS=-v
NTPOPTIONS=-u

Here is what I get when I run ntpdate from the command line.
imagerocfw# ntpdate -u timelord.uregina.ca
 1 Dec 20:02:19 ntpdate[30561]: adjust time server 142.3.100.15 offset
-0.069286 sec

Which seems to work.
Am I missing something?

Darcy Parker





---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click

leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/


[leaf-user] Microtik Routerboard 500

2005-06-09 Thread Darcy Parker (Home)
Good day all,

I am considering replacing a bunch of old dual floppy machines with
the microtik routerboard 500 (http://www.routerboard.com/).  These
boards have a CF card slot and can be configured to boot off of them.  I
believe the units has a MIPS 79RC32434 processor.

I am currently running Leaf Bering uClibC 2.0 but will migrate to
2.2.  I use these for IPSEC connections between several remote offices.

Has anyone ported Leaf bering to the routerboard or can anyone give me
some starting pointers?  My concerns are how to get from my two floppies
to the CF card, and if the existing code will work with the MIPS processor.

Darcy


---
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61 plasma display: http://www.necitguy.com/?r=20

leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/


[leaf-user] Re: dhcp (pump) fails or acquire address

2005-03-07 Thread Darcy Parker (Home)
Good day all,
   I had a similar problem with Leaf bering 1.1 and 1.2.  I have since 
upgraded to uClibC 2.2.2.  I did find a fix for the older system when I 
was using it, I replaced PUMP with DHCPD which solved the problem.

Darcy Parker
Message: 2
Date: Sun, 06 Mar 2005 21:41:17 -0500
From: Gene Smith [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: leaf-user@lists.sourceforge.net
Subject: Re: [leaf-user] dhcp (pump) fails or acquire address after network
(cable) outage
Jon Clausen wrote, On 02/13/2005 03:27 AM:
 

On Sat, 12 Feb, 2005 at 18:00:05 -0500, Gene Smith wrote:
   

I am running a bering-leaf system with 2.4.18 kernel that I setup about 
two years ago (not sure of exact version). It has been working fine 
except for one problem. When the cable goes down and eventually comes 
back up the bering-leaf system never recovers (clients can't access 
internet). I tried restarting services (shorewall, networking, 
ifup/down) to no avail. Usually I just reboot. However I discovered that 
if I kill and re-run pump (/sbin/pump -i eth1) it then recovers and 
acquires its IP address. Could I have something configured wrong that 
prevents a automatic recovery?
 

I have been having similar (if not identical) problems lately: Link goes
down, lease expires, link comes up again, pump fails to renew.
AFAICT there's a bug which makes pump exit, when no dhcp-server can be
reached after N retries. I'm not absolutely sure this is what actually
happens, but some googling turned up links to that effect. (Sorry I can't
reproduce the search ATM)
Working on the *assumption* that pump indeed dies, I threw this together:
# cat /sbin/repump
#!/bin/sh
if [ -z `/sbin/pidof pump` ] ;then
   /usr/bin/logger Repump: pump looks dead, attempting resurrection;
   /sbin/pump
#else
#/usr/bin/logger Repump: pump lives, pid `pidof pump`
fi
and added:
# keeping pump alive:
*/10 *  * * *   root/sbin/repump
to /etc/crontab.
Basically a crude workaround.
(Un)fortunately the ISP seems to have gotten their act together, at about
the same time as I did the above. Hence I don't know whether or not it works
as desired... :P
HTH
/Jon
   

On my system I have verified that pump *does not* die. It just seem to
quit doing its thing. I have to kill it and restart it to get my ip addr
back. Also, I see no indication in /var/log/syslog that there was a
problem other than the lack of the typical slew of messages pump
generates when it does a periodic renew. Not even sure ISP was down
since syslog indicated that shorewall was rejecting stuff during the
time my lease was expired and pump did not run (if that is possible?).
Question: How is pump normally started on boot? I am unable to figure
out how it starts up after looking through the various files. I see
indications that it is somehow tied in with ifup or possibly shorewall
startup.
-gene

--__--__--
___
leaf-user mailing list
leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
End of leaf-user Digest
 


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click

leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html