Mr. Caryl Whitlatch wrote, On 19-01-2007 16:11:
Config tree needs to be recompiled: File /usr/local/nav/cricket/cricket-config/switches/Defaults is newer than the compiled version
This warning appears if the cricket-configuration has been changed without cricket-compile having been run. Normally, cricket-compile is run if necessary at the start of each collection run - which is at least every 5 minutes. You might be seeing this error because of file permission problems. Makecricketconfig.pl prior to NAV 3.2 used to unnecessarily set restrictive umasks before creating new Cricket configuration files. Please make sure that every file and directory below /usr/local/nav/cricket/cricket-config/ is writable by the navcron user, and readable by everyone (or the user who runs the Apache process - the point being that Cricket's web interface must be able to read the config). I also recommend upgrading to NAV 3.2, of course :) -- mvh Morten Brekkevold UNINETT
From morten.brekkevold at uninett.no Fri Feb 2 14:36:11 2007 From: morten.brekkevold at uninett.no (Morten Brekkevold) Date: Fri Feb 2 14:36:30 2007 Subject: [Nav-users] cricket 2 In-Reply-To: <004201c73bdc$4ca5b2c0$4732a8c0@cwhitlatch> References: <004201c73bdc$4ca5b2c0$4732a8c0@cwhitlatch> Message-ID: <45C33E4B.4030103@uninett.no>
Mr. Caryl Whitlatch wrote, On 19-01-2007 16:12:
Anything I should be concerned with here? [output from makecricketconfig snipped]
No, everything looks normal (except for the fact that makecricketconfig in NAV 3.1.1 has known bugs). -- mvh Morten Brekkevold UNINETT
From morten.brekkevold at uninett.no Fri Feb 2 14:38:17 2007 From: morten.brekkevold at uninett.no (Morten Brekkevold) Date: Fri Feb 2 14:38:30 2007 Subject: [Nav-users] Announcement: NAV 3.2.0 released In-Reply-To: <1170419636.12236.1.camel@myh> References: <45C32599.4070207@uninett.no> <1170419636.12236.1.camel@myh> Message-ID: <45C33EC9.3030606@uninett.no>
Stein Magnus Jodal wrote, On 02-02-2007 13:33:
Err. Morten meant 3.2.0. He blames the day of the week ;-)
That, and lack of strong coffee :P
"When in doubt, read the subject!" -Morten
Yes, truth is in the headers. -- mvh Morten Brekkevold UNINETT
From oetting at usgs.gov Mon Feb 5 11:28:28 2007 From: oetting at usgs.gov (Dan Oetting) Date: Mon Feb 5 19:28:35 2007 Subject: [Nav-users] Need to make a sms-Alert when a mac-address enter the network In-Reply-To: <45B0C184.3657.00CE.0@hivolda.no> References: <45B0C184.3657.00CE.0@hivolda.no> Message-ID: <78035348-7938-499C-9093-9E9F2D9E73DF@usgs.gov>
On Jan 19, 2007, at 5:02 AM, Peder Magne Sefland wrote:
We use DHCP and I would like to get an sms-message when this mac-address enter the network. Can this be done today?
On a small scale such as having only 1 MAC address that you need to catch, you could configure your DHCP servers to assign this MAC a specific IP. With the suspect confined to a known set of IP addresses you could also setup a sniffer on the external routes to capture all traffic from those IPs to see for yourself if there is abuse. I am surprised that switches can't generate an SNMP trap whenever a new MAC address is added to it's routing tables. -- Dan O.