Subject: RE: dhcp and new machines
From: Barsalou (barjunk@attglobal.net)
Date: Mon Sep 22 2003 - 11:50:25 AKDT
Thing is...it could be anything...Mac, Win32, Linux. That's why I
thought we would just identify the machine and just show up where it is
plugged in....Big Brother is watching <hehehe>
Ideally, people would figure out after a while that they should have the
machine scanned before they put it on the net.
We could also organize it so that all the current machines, although
served by dhcp, got the same address...any mac address that isn't in the
database, doesn't get an IP. That doesn't stop someone from using a
static address, but it means they have to be a little bit smarter to get
on the network, and hopefully are doing more with virus protection.
Mike
On Mon, 2003-09-22 at 11:06, Leif Sawyer wrote:
> Mike B wrote:
>
> > I am working on a way to notify the administrator when a new machine
> > comes on to the network. One of the problems I hope to resolve is that
> > when a new machine comes onto the network (most likely a guest/foreign
> > machine) I can immediately get it scanned for viruses.
> >
> > I was considering using some sort of mechanism that watches the DHCP
> > server, when it hands out a NEW lease (instead of a renew).
> >
> > Any ideas out there?
>
> Well, you might try something like logwatch to follow the dhcp.leases
> file.
>
> You might also want your program to keep a database of the mac addresses
> that it discovers, so that when you see a new mac address, you can send
> off the notification for the virus scan.
>
> You didn't say what the client end mechanism is -- if it's a win32
> environment, and you're connecting to a domain, then the domain startup
> script should take care of that -- of course that doesn't help before
> you connect to the domain.
-- Barsalou <barjunk@attglobal.net>--------- To unsubscribe, send email to <aklug-request@aklug.org> with 'unsubscribe' in the message body.
This archive was generated by hypermail 2a23 : Mon Sep 22 2003 - 11:46:16 AKDT