Re: [pve-devel] dhcp server

2014-07-26 Thread Dietmar Maurer
> >>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
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Dietmar Maurer
 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. 

ok, looks good to me.


___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Alexandre DERUMIER
>>That sounds good (no changes needed) ;-)

I have done some tests, it's working fine with ipv4, no regression.

I'll do more tests.


- Mail original - 

De: "Dietmar Maurer"  
À: "Michael Rasmussen" , pve-devel@pve.proxmox.com 
Envoyé: Samedi 26 Juillet 2014 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;-) 

That sounds good (no changes needed) ;-) 

___ 
pve-devel mailing list 
pve-devel@pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Alexandre DERUMIER
>>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/ 
>>
>>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. Stateful 
>>DHCPv6 as we know from DHCPv4 is a bastard specification anyway since 
>>it is not able to provide default routers so SLAAC will be required 
>>anyway. 

I'm totally newbie with ipv6, but this seem good :)


- Mail original - 

De: "Michael Rasmussen"  
À: "Dietmar Maurer"  
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  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 forgot to mention: 50% of the code is generic and provided we 
only need to provide DNS et al the required code for this will only 
raise the lines of code by 10-15%. 

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/ 

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. Stateful 
DHCPv6 as we know from DHCPv4 is a bastard specification anyway since 
it is not able to provide default routers so SLAAC will be required 
anyway. 

-- 
Hilsen/Regards 
Michael Rasmussen 

Get my public GnuPG keys: 
michael  rasmussen  cc 
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E 
mir  datanom  net 
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C 
mir  miras  org 
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 
-- 
/usr/games/fortune -es says: 
Marriage is the triumph of imagination over intelligence. Second 
marriage is the triumph of hope over experience. 

___ 
pve-devel mailing list 
pve-devel@pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Michael Rasmussen
On Sat, 26 Jul 2014 11:13:00 +
Dietmar Maurer  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 forgot to mention: 50% of the code is generic and provided we
only need to provide DNS et al the required code for this will only
raise the lines of code by 10-15%.

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/

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. Stateful
DHCPv6 as we know from DHCPv4 is a bastard specification anyway since
it is not able to provide default routers so SLAAC will be required
anyway.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--
/usr/games/fortune -es says:
Marriage is the triumph of imagination over intelligence.  Second
marriage is the triumph of hope over experience.


signature.asc
Description: PGP signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Dietmar Maurer
> 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
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Michael Rasmussen
On Sat, 26 Jul 2014 09:35:59 +
Dietmar Maurer  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 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. 

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--
/usr/games/fortune -es says:
There is no TRUTH.  There is no REALITY.  There is no CONSISTENCY.
There are no ABSOLUTE STATEMENTS.   I'm very probably wrong.


signature.asc
Description: PGP signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Michael Rasmussen
On Sat, 26 Jul 2014 09:34:40 +
Dietmar Maurer  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  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--
/usr/games/fortune -es says:
There is no TRUTH.  There is no REALITY.  There is no CONSISTENCY.
There are no ABSOLUTE STATEMENTS.   I'm very probably wrong.


signature.asc
Description: PGP signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Dietmar Maurer
> 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
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Dietmar Maurer
> > 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) ;-)

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Michael Rasmussen
On Sat, 26 Jul 2014 08:46:38 +0200 (CEST)
Alexandre DERUMIER  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, but it's planned for 2015-2016, as our ipv4 /20 
> will be full soon)
> 
> 
> I found some intestesting openstack slides:
> 
> http://fr.slideshare.net/shixiongshang1/openstack-havana-over-ipv6
> 
> 
Seems that openstack will start with ND and SLAAC only for a the next
major release. The slides mentioned Icehouse release and studying the
Icehouse release notes you will find no mentioning of IPv6. So I guess
IPv6 didn't make it in Icehouse after all.

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--
/usr/games/fortune -es says:
[Babe] Ruth made a big mistake when he gave up pitching.
-- Tris Speaker, 1921


signature.asc
Description: PGP signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Michael Rasmussen
On Sat, 26 Jul 2014 07:01:42 +
Dietmar Maurer  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 complexity and lines of code.

> I am a bit afraid how many LOC you write for that DHCP server? 
> 
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;-) 

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--
/usr/games/fortune -es says:
Don't comment bad code - rewrite it.
- The Elements of Programming Style (Kernighan & Plaugher)


signature.asc
Description: PGP signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Michael Rasmussen
On Sat, 26 Jul 2014 10:45:24 +0200 (CEST)
Alexandre DERUMIER  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 ?
> 
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;-)

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--
/usr/games/fortune -es says:
Hodie natus est radici frater.

[ Unto the root is born a brother ]


signature.asc
Description: PGP signature
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Alexandre DERUMIER
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 ?


- Mail original - 

De: "Dietmar Maurer"  
À: "Alexandre DERUMIER" , "Stefan Priebe" 
 
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 to guest, but not neighbor 
> discovery ? 

I recently added a IPv6 router to our network (for tresting ipv6). I had 
IPv6 ND enabled, and guess what happened? All our windows servers and 
workstation switched to ipv6 automatically and immediately using ND! 
Unfortunately, there was no DHCPv6 server, so name resolution stopped to work 
immediately ... 
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Dietmar Maurer
> >>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 recently added a IPv6 router to our network (for tresting ipv6). I had
IPv6 ND enabled, and guess what happened? All our windows servers and
workstation switched to ipv6 automatically and immediately using ND!
Unfortunately, there was no DHCPv6 server, so name resolution stopped to work 
immediately ...

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Alexandre DERUMIER
Some infos about openstack dhcpv6 implementation (with dnsmasq)

https://github.com/openstack/neutron-specs/commit/7bbfecf12cc2826b0ce8bc3836c3bc4f0e62c464
- Mail original - 

De: "Dietmar Maurer"  
À: "Michael Rasmussen" , pve-devel@pve.proxmox.com 
Envoyé: Samedi 26 Juillet 2014 09:01:42 
Objet: Re: [pve-devel] dhcp server 

> > 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 on proxmox? 

AFAIK IPv6 Neighbor Discovery cannot even handle basic things like passing DNS 
server. 
So you need DHCPv6. 

I am a bit afraid how many LOC you write for that DHCP server? 

___ 
pve-devel mailing list 
pve-devel@pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


Re: [pve-devel] dhcp server

2014-07-26 Thread Dietmar Maurer
> > 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 on proxmox?

AFAIK IPv6 Neighbor Discovery cannot even handle basic things like passing DNS 
server.
So you need DHCPv6.

I am a bit afraid how many LOC you write for that DHCP server? 

___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel