On Sat, 19 Jul 2014 14:27:14 +
Dietmar Maurer diet...@proxmox.com wrote:
Please coordinate this with Alexandre. But I think a prototype would be
interesting, because using perl gives use most flexibility.
As I recall it Alexandre were opting for dnsmasq so I don't think our
efforts will
On Sat, 19 Jul 2014 05:07:58 +
Dietmar Maurer diet...@proxmox.com wrote:
Thanks for that link. But I have no idea how stable that is. And is
it feature complete? ipv6 support?
I found the answer to ipv6:
As of perl 5.14 all needed to support ipv6 is to replace any instance
of
Thanks for that link. But I have no idea how stable that is. And is it
feature complete? ipv6 support?
I found the answer to ipv6:
As of perl 5.14 all needed to support ipv6 is to replace any instance of
Perl is not the problem. I talk about DHCP features/extension for v6?
On Sat, 19 Jul 2014 16:38:02 +
Dietmar Maurer diet...@proxmox.com wrote:
just lock the file before you write (or what is the question?)
I was thinking of these scenarios:
1a) Client broadcast request for IP
2a) Each nodes listen so each could give a reply simultaneously!
1b) Several
On Sat, 19 Jul 2014 16:41:02 +
Dietmar Maurer diet...@proxmox.com wrote:
Thanks for that link. But I have no idea how stable that is. And is it
feature complete? ipv6 support?
I found the answer to ipv6:
As of perl 5.14 all needed to support ipv6 is to replace any instance of
On Sat, 19 Jul 2014 05:07:58 +
Dietmar Maurer diet...@proxmox.com wrote:
Thanks for that link. But I have no idea how stable that is. And is
it feature complete? ipv6 support?
I have done a number of tests with the client part of Net::DHCP which
is very promissing.
Test has been made
I was thinking of these scenarios:
1a) Client broadcast request for IP
2a) Each nodes listen so each could give a reply simultaneously!
We know the MAC address of our VMs, so only the node where the VM resides
can answer.
1b) Several clients request for an IP simultaneously
2b) Each