, with
communications between deamon)
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: Michael Rasmussen m...@datanom.net, pve-devel@pve.proxmox.com
Envoyé: Samedi 26 Juillet 2014 15:53:58
Objet: RE: [pve-devel] dhcp server
That sounds good
...@odiso.com
À: Dietmar Maurer diet...@proxmox.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Dimanche 27 Juillet 2014 10:12:01
Objet: Re: [pve-devel] dhcp server
That listens on both addresses (ipv4 and ipv6)?
Michael said me that for listen on both ipv4 and ipv6 at the same time, we need
Is DHCPv6 really in use? I thought everybody will use IPv6 Neighbor
Discovery.
This is also what I suspect since no module is available from CPAN but if
proxmox is to appear as a boundary router for private nets will IPv6 Neighbor
Discovery be sufficient from the clients to the interface
aderum...@odiso.com, Stefan Priebe
s.pri...@profihost.ag
Cc: pve-devel@pve.proxmox.com
Envoyé: Samedi 26 Juillet 2014 10:41:07
Objet: RE: [pve-devel] dhcp server
Is DHCPv6 really in use? I thought everybody will use IPv6 Neighbor
Discovery.
I think dhcpv6 can assign hostname,dns servers
On Sat, 26 Jul 2014 10:45:24 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
By the way, about ipv6, pveproxy don't work currently because of
IO::Socket::INET not compatible with ipv6
I see that a new IO::Socket::IP support both ipv4 and ipv6, do you known if
it's works fine
On Sat, 26 Jul 2014 07:01:42 +
Dietmar Maurer diet...@proxmox.com wrote:
AFAIK IPv6 Neighbor Discovery cannot even handle basic things like passing
DNS server.
So you need DHCPv6.
Yes, I know that but if the DHCPv6 part should only handle such things
it will greatly reduce the
On Sat, 26 Jul 2014 08:46:38 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
Is DHCPv6 really in use? I thought everybody will use IPv6 Neighbor
Discovery.
I think dhcpv6 can assign hostname,dns servers to guest, but not neighbor
discovery ?
(I don't use ipv6 currently,
I see that a new IO::Socket::IP support both ipv4 and ipv6, do you known if
it's
works fine ?
In my dhcp server I use IO::Socket::IP. It works extremely well and is a
drop-in
replacement for IO::Socket::INET. No code needs any changes;-)
That sounds good (no changes needed) ;-)
Well, pveproxy, which is likely the same in complexity, sports 1372 lines off
code
so I don't consider 1181 lines of code frightening compared to that;-)
But this is ipv4 only?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
On Sat, 26 Jul 2014 09:34:40 +
Dietmar Maurer diet...@proxmox.com wrote:
That sounds good (no changes needed) ;-)
To have full support for socket helper IPv6 functions you need to use
Socket6 as well.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael at rasmussen
On Sat, 26 Jul 2014 09:35:59 +
Dietmar Maurer diet...@proxmox.com wrote:
Well, pveproxy, which is likely the same in complexity, sports 1372 lines
off code
so I don't consider 1181 lines of code frightening compared to that;-)
But this is ipv4 only?
Yes, but if we leave IP
Yes, but if we leave IP discovery to ND and SLAAC which is the intended way we
will only need to provide DNS et al. Gateway, broadcast and IP will be
handled by
ND and SLAAC.
Ok, sound reasonable.
___
pve-devel mailing list
On Sat, 26 Jul 2014 11:13:00 +
Dietmar Maurer diet...@proxmox.com wrote:
Yes, but if we leave IP discovery to ND and SLAAC which is the intended way
we
will only need to provide DNS et al. Gateway, broadcast and IP will be
handled by
ND and SLAAC.
Ok, sound reasonable.
And I
Cc: pve-devel@pve.proxmox.com
Envoyé: Samedi 26 Juillet 2014 13:31:13
Objet: Re: [pve-devel] dhcp server
On Sat, 26 Jul 2014 11:13:00 +
Dietmar Maurer diet...@proxmox.com wrote:
Yes, but if we leave IP discovery to ND and SLAAC which is the intended way
we
will only need to provide
11:34:40
Objet: Re: [pve-devel] dhcp server
I see that a new IO::Socket::IP support both ipv4 and ipv6, do you known if
it's
works fine ?
In my dhcp server I use IO::Socket::IP. It works extremely well and is a
drop-in
replacement for IO::Socket::INET. No code needs any changes
My intended way of doing it as IPv6 stateless DHCPv6. Read more here:
http://blog.geoff.co.uk/2011/08/02/ipv6-automated-network-configuration/
Thanks for the link.
When SLAAC with RDNSS is widely accepted this will be the way to go and this
will be easy provided we use IPv6 stateless DHCPv6.
That sounds good (no changes needed) ;-)
I have done some tests, it's working fine with ipv4, no regression.
That listens on both addresses (ipv4 and ipv6)?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
Hi all,
The dhcp server is completed with the following limitations:
1) A monitor for changing binding state for expired leases is missing
2) No IPv6 functionality yet since no module is available for IPv6.
IPv6 dhcp seems to be completely different from IPv4 dhcp which
requires a lot of reading.
Is DHCPv6 really in use? I thought everybody will use IPv6 Neighbor
Discovery.
Stefan
Am 25.07.2014 21:45, schrieb Michael Rasmussen:
Hi all,
The dhcp server is completed with the following limitations:
1) A monitor for changing binding state for expired leases is missing
2) No IPv6
On Fri, 25 Jul 2014 21:53:43 +0200
Stefan Priebe s.pri...@profihost.ag wrote:
Is DHCPv6 really in use? I thought everybody will use IPv6 Neighbor Discovery.
This is also what I suspect since no module is available from CPAN but
if proxmox is to appear as a boundary router for private nets
:)
- Mail original -
De: Michael Rasmussen m...@datanom.net
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com
Envoyé: Dimanche 20 Juillet 2014 15:13:18
Objet: Re: [pve-devel] DHCP server
On Sun, 20 Jul 2014 15:04:29 +0200
original -
De: Michael Rasmussen m...@datanom.net
À: Dietmar Maurer diet...@proxmox.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Samedi 19 Juillet 2014 18:53:34
Objet: Re: [pve-devel] DHCP server
On Sat, 19 Jul 2014 16:38:02 +
Dietmar Maurer diet...@proxmox.com wrote:
just lock
On Sun, 20 Jul 2014 15:04:29 +0200 (CEST)
Alexandre DERUMIER aderum...@odiso.com wrote:
Hi, Isn't it possible to filter dhcp request with iptables, on the host
outside interface ?
Like this, each host have a dhcp server which respond only to vms hosted on
the host.
It should not be
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
30 matches
Mail list logo
