On 01/27/2014 01:47 AM, Nehal J Wani wrote:
Introduce helper program to catch events from dnsmasq and maintain a custom
lease file per network. It supports dhcpv4 and dhcpv6. The file is saved as
interface-name.status.
Each lease contains the following info:
expiry-time (epoch time) mac
On Mon, Jan 27, 2014 at 2:17 PM, Nehal J Wani nehaljw.k...@gmail.com wrote:
Introduce helper program to catch events from dnsmasq and maintain a custom
lease file per network. It supports dhcpv4 and dhcpv6. The file is saved as
interface-name.status.
Each lease contains the following info:
I feel like I'm bikesheding but is it the best idea to have a custom file
format? I know our string handling code makes this really easy to do but it
just has a slight code smell to make our own format. We link to stuff like
yajl and libxml for JSON/XML support and its really simple to do
Introduce helper program to catch events from dnsmasq and maintain a custom
lease file per network. It supports dhcpv4 and dhcpv6. The file is saved as
interface-name.status.
Each lease contains the following info:
expiry-time (epoch time) mac iaid ip-address hostname clientid
Example of custom
On Thu, Jan 16, 2014 at 9:07 AM, Doug Goldstein car...@cardoe.com wrote:
On Jan 14, 2014, at 2:09 PM, Nehal J Wani nehaljw.k...@gmail.com wrote:
Introduce helper program to catch events from dnsmasq and maintain a custom
lease file per network. It supports DHCPv4 and DHCPv6. The file is saved
On Jan 14, 2014, at 2:09 PM, Nehal J Wani nehaljw.k...@gmail.com wrote:
Introduce helper program to catch events from dnsmasq and maintain a custom
lease file per network. It supports DHCPv4 and DHCPv6. The file is saved as
interface-name.status.
The format of each lease is:
expiry-time
Introduce helper program to catch events from dnsmasq and maintain a custom
lease file per network. It supports DHCPv4 and DHCPv6. The file is saved as
interface-name.status.
The format of each lease is:
expiry-time (epoch time) mac iaid ip-address hostname clientid
Example of custom leases file
