Send dhcp-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Out of Office. (was: Out of Office. (was: DHCP Leases
Parser)) (Steve Clark)
2. Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: DHCP Leases Parser))))))))))))))) (Steve Clark)
3. Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: DHCP Leases Parser))))))))))))))) (Steve Clark)
4. Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: DHCP Leases Parser))))))))))))))) (Steve Clark)
5. Re: DHCP Leases Parser (Jos? Queiroz)
6. Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: DHCP Leases Parser))))))))))))))))
(Steve Clark)
----------------------------------------------------------------------
Message: 1
Date: Wed, 13 Apr 2016 11:16:09 -0400
From: Steve Clark <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Out of Office. (was: Out of Office. (was: DHCP Leases
Parser))
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160413/8a06e75a/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 13 Apr 2016 11:16:10 -0400
From: Steve Clark <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office. (was:
Out of Office. (was: Out of Office. (was: Out of Office. (was: Out of
Office. (was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: DHCP Leases
Parser)))))))))))))))
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160413/96aa95a6/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 13 Apr 2016 11:16:09 -0400
From: Steve Clark <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office. (was:
Out of Office. (was: Out of Office. (was: Out of Office. (was: Out of
Office. (was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: DHCP Leases
Parser)))))))))))))))
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160413/4360fc83/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 13 Apr 2016 11:16:09 -0400
From: Steve Clark <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office. (was:
Out of Office. (was: Out of Office. (was: Out of Office. (was: Out of
Office. (was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: DHCP Leases
Parser)))))))))))))))
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160413/a2775d21/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 13 Apr 2016 12:16:50 -0300
From: Jos? Queiroz <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: DHCP Leases Parser
Message-ID:
<CADeaZRzfbQHp4twGUBKoP-jq58OH8hFd7J=mpayaaddrzjc...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I believe that what you're trying to do is partly implemented with storing
leases on MySQL databases.
2016-04-13 12:11 GMT-03:00 Ryan Gray <[email protected]>:
> Thanks for your input Patrick. I'll look into what might be helpful
> information from the ISC folks. I am going to put some time in up front on
> something that might help obfuscate leases data while keeping
> same-data-points randomized to the same strings (if that makes sense). As
> much as I would like to skip this step for the sake of diving into the
> development of the parser itself, I cannot make a case for sending this
> data out without this step or some mitigating actions to remove the risk.
>
> Thank you.
>
>
> Regards,
> Ryan Gray
>
> On Wed, Apr 13, 2016 at 9:48 AM, Patrick Trapp <[email protected]>
> wrote:
>
>> It would be interesting to see if the ISC folks can provide some
>> insight/aid to you even if they as an organization have not prioritized
>> building the project themselves.
>>
>> We have a pretty simplistic analysis that I might be able to share with
>> you, but I think your PHP classes are probably what our developers are
>> using.
>>
>> I have a pretty busy leases file, I think, but I would want to obfuscate
>> things before I gave it to "some dude on the Internet" as you so eloquently
>> put it.
>>
>> Patrick
>>
>> ------------------------------
>> *From:* [email protected] [
>> [email protected]] on behalf of Ryan Gray [
>> [email protected]]
>> *Sent:* Wednesday, April 13, 2016 9:36 AM
>> *To:* Users of ISC DHCP
>> *Subject:* DHCP Leases Parser
>>
>> Greetings everyone,
>>
>> This is one part poll, one part request. I am working on a project that
>> necessitates analyzing the dhcpd.leases "database". For many years I have
>> struggled with getting usable information out of the leases database in a
>> sane fashion. While there have been some very helpful utilities, (command
>> line scripts, dhcpstatus.cgi, dhcpd-pools anyone?), none of them have been
>> exactly what I was looking for and all of them are quite antiquated in
>> regards to what they are built with. I've had it with cobbling together
>> nearly unacceptable solutions and am going to build an application to solve
>> this, at the very least for myself. I've got a good start with some super
>> helpful PHP classes that I've been working on.
>>
>> Poll:
>> If there were a service that allowed you to upload, or otherwise sync,
>> your leases file and would give you status, statistics, and historical
>> information, would you be interested in using it? I am not talking about
>> anything that is actively part of the DHCP traffic, purely a leases
>> analyzer. Is there interest in a web based utility like this?
>>
>> Request:
>> If there is interest in a service like this, it will be imperative that I
>> gather as many example dhcpd.leases files as possible during development. I
>> can only generate so much data locally and I want to account for as many
>> variables as possible. My request is that if you are interested in
>> something like this and are able to send me any dhcpd.leases files, that
>> would be extremely helpful. I realize that leases information might be
>> considered too sensitive to just send to some dude on the internet, so if
>> anyone is interested and finds this a hurdle, I would be happy to come up
>> with a way for us to mitigate that risk. ....perhaps a script that you can
>> run locally to obscure sensitive data.
>>
>> Just putting out the feelers here. This is getting built regardless, but
>> if there is community interest in the topic, I would be excited to work
>> with you and to give back to a community that has done so much for so many
>> for so long.
>>
>>
>> Regards,
>> Ryan Gray
>>
>> _______________________________________________
>> dhcp-users mailing list
>> [email protected]
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>
>
> _______________________________________________
> dhcp-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160413/41608f79/attachment-0001.html>
------------------------------
Message: 6
Date: Wed, 13 Apr 2016 11:18:09 -0400
From: Steve Clark <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office. (was:
Out of Office. (was: Out of Office. (was: Out of Office. (was: Out of
Office. (was: Out of Office. (was: Out of Office. (was: Out of Office.
(was: Out of Office. (was: Out of Office. (was: Out of Office. (was:
DHCP Leases Parser))))))))))))))))
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160413/69631230/attachment.html>
------------------------------
_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
End of dhcp-users Digest, Vol 90, Issue 17
******************************************
