From: Don Gould <don@bowenvale.co.nz>
To: lartc@vger.kernel.org
Subject: [LARTC] HOWTO: Hello New MAC / DHCP Request - How to spot the
Date: Mon, 31 Jul 2006 11:49:18 +0000 [thread overview]
Message-ID: <44CDEE3E.3000606@bowenvale.co.nz> (raw)
Sheldon Hearn wrote:
> I'm sure you could engineer something really impressive, but you could
> probably get away with a lot less effort by simply tailing whatever
> dhcpd logs to (possibly /var/log/messages).
Yes, that discussion has been had some where...
Some research in to dnsmasq and a few emails to the guy who wrote it
showed up the answer...
> You may not need to make any source changes at all: dnsmasq will call a custom script whenever a DHCP lease is created or destroyed: see the --dhcp-script flag in the manpage for details. The MAC address and IP address and name of the host are passed to the script.
--
Don Gould
www.thinkdesignprint.co.nz - www.tcn.bowenvale.co.nz -
www.bowenvale.co.nz - www.hearingbooks.co.nz - SkypeMe: ThinkDesignPrint
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2006-07-31 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44CDEE3E.3000606@bowenvale.co.nz \
--to=don@bowenvale.co.nz \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox