Leases for fixed-address hosts not written to lease file?

[Eddie Quek]

Hi Steve

I am reading your script with interest. I hope you can shared with me
how I can make use of your script to implement in my planning. I am
totally new and need advise.

My plan was:
- to reserve a fixed range of addresses for my resources
- use the dynamic range for VPN and for guest that visited my site

As the log is huge and find it difficult to track whether the fixed
addresses are been used?
Can the script be used to track my plan?

Thanks
EddieQuek

On 5/24/07, Steve van der Burg <steve.vanderburg at lhsc.on.ca> wrote:
> >>> Emmanuel Halbwachs <Emmanuel.Halbwachs at obspm.fr> wrote:
> > Hello,
> >
> > Steve van der Burg a écrit (Tue, May 22, 2007 at 01:45:49PM -0400) :
> >> doesn't show up in the leases file.  I can see that the lease is
> >> fine (by checking what the client gets), and all of my "normal"
> >> (ie. no fixed address, just regular dynamic address assignment)
> >> leases are logged just fine.
> >
> > As a DHCP newbie, I was about to ask the very same question (didn't
> > RTFM much I admit), so I watch carefully the answers.
> >
> > For the moment, I use this workaround to have roughly an idea of
> what
> > machine is a currently DHCP client :
> >
> >
> >     REGEXP="DHCPACK on 145.238"  (my prefix)
> >     LOGFILE=/var/log/all.log
> >
> >     grep -i "$REGEXP" $LOGFILE \
> >         | awk '{print $8}' \
> >         | sort -u \
> >         | sort -t . -n -k1,1 -k2,2 -k3,3 -k4,4 \
> >         > $FILE
> >
> > And then some aggregation.
> >
>
> Thanks to everyone for your suggestions.  It looks like hacking the
> server may not be the easiest way to get the job done, I can't really go
> to 3.1.0 for production, so I think I'll stick with log-scraping, which
> I'm already doing for a couple of other reasons anyway.
>
> In case anyone is interested, I've posted my log-scraping code here:
>
>    http://www.fileden.com/files/2007/5/24/1107964/scrape-messages.txt
>
> It is run via cron once a minute, and keeps track of the timestamp of
> the last log line that it processed, so it doesn't needlessly scan huge
> chunks of the logs that it has already seen.  It currently builds a
> little perl data structure for new or renewed leases that it sees
> logged, and sends them to another machine to be stuffed into a database.
>  Here's a sample of that file:
>
>    http://www.fileden.com/files/2007/5/24/1107964/llldata.txt
>
> ...Steve
>
>
>