On 10/31/2012 09:50 PM, Laine Stump wrote:
On 10/31/2012 03:11 PM, Gene Czarcinski wrote:
On 10/31/2012 11:53 AM, Laine Stump wrote:
That's just a safeguard to enforce the ipv4-only status of dhcp in the
current libvirt. Just remove that restriction from the function
virNetworkDefUpdateIP() as
On 10/31/2012 09:42 PM, Laine Stump wrote:
On 10/30/2012 05:35 PM, Gene Czarcinski wrote:
About being compatible with old code. I see the dhcp6 patches and
this potential patch as being based on v1.0.0 and not being
back-ported. So I am not sure I see a potential conflict.
Being able to
On 11/01/2012 05:25 AM, Gene Czarcinski wrote:
You want to be able to a specific adaptation/configuration of
libvirt-1.0.0 on RHEL6/CentOS6 but not insist that their dnsmasq be
updated.
Yes, there are people that do that. In other words, we like for libvirt
to work out of the box on
On Thu, Nov 01, 2012 at 07:25:45AM -0400, Gene Czarcinski wrote:
Doing some looking, it appears that RHEL6.3 uses libvirt-0.8.7 and
CentOS6.3 uses libvirt-0.9.10. I can see some group wanting to
Just for the record, RHEL6.3 uses libvirt-0.9.10.
Dave
--
libvir-list mailing list
On 11/01/2012 06:53 AM, Gene Czarcinski wrote:
On 10/31/2012 09:50 PM, Laine Stump wrote:
On 10/31/2012 03:11 PM, Gene Czarcinski wrote:
On 10/31/2012 11:53 AM, Laine Stump wrote:
That's just a safeguard to enforce the ipv4-only status of dhcp in the
current libvirt. Just remove that
On 11/01/2012 10:08 AM, Dave Allan wrote:
On Thu, Nov 01, 2012 at 07:25:45AM -0400, Gene Czarcinski wrote:
Doing some looking, it appears that RHEL6.3 uses libvirt-0.8.7 and
CentOS6.3 uses libvirt-0.9.10. I can see some group wanting to
Just for the record, RHEL6.3 uses libvirt-0.9.10.
OK,
On 10/30/2012 02:28 PM, Laine Stump wrote:
I now realize that I am going to need to get into virsh net-update
since I am adding things to the xml specification and net-update will
need to differentiate between dhcp4 and dhcp6 changes.
Another thought that occurs to me is whether there has any
On 10/31/2012 10:24 AM, Gene Czarcinski wrote:
On 10/30/2012 02:28 PM, Laine Stump wrote:
I now realize that I am going to need to get into virsh net-update
since I am adding things to the xml specification and net-update will
need to differentiate between dhcp4 and dhcp6 changes.
Another
On 10/31/2012 11:53 AM, Laine Stump wrote:
That's just a safeguard to enforce the ipv4-only status of dhcp in the
current libvirt. Just remove that restriction from the function
virNetworkDefUpdateIP() as a part of your patch adding ipv6 dhcp support.
OK, removing the ipv4 test has net-update
On 10/30/2012 05:35 PM, Gene Czarcinski wrote:
About being compatible with old code. I see the dhcp6 patches and
this potential patch as being based on v1.0.0 and not being
back-ported. So I am not sure I see a potential conflict.
Being able to backport patches to older libvirt releases is
On 10/31/2012 03:11 PM, Gene Czarcinski wrote:
On 10/31/2012 11:53 AM, Laine Stump wrote:
That's just a safeguard to enforce the ipv4-only status of dhcp in the
current libvirt. Just remove that restriction from the function
virNetworkDefUpdateIP() as a part of your patch adding ipv6 dhcp
On 10/29/2012 04:08 PM, Laine Stump wrote:
On 10/29/2012 08:26 AM, Gene Czarcinski wrote:
On 10/27/2012 03:18 PM, Gene Czarcinski wrote:
OK, I have the basic implementation for libvirt support of dhcp6. Let
me say again that 98% of the work was already done. There is still a
bunch of work
On 10/30/2012 11:58 AM, Gene Czarcinski wrote:
On 10/29/2012 04:08 PM, Laine Stump wrote:
On 10/29/2012 08:26 AM, Gene Czarcinski wrote:
On 10/27/2012 03:18 PM, Gene Czarcinski wrote:
OK, I have the basic implementation for libvirt support of dhcp6. Let
me say again that 98% of the work was
On 10/30/2012 02:28 PM, Laine Stump wrote:
On 10/30/2012 11:58 AM, Gene Czarcinski wrote:
Well, ff02::1:2 does have some meaning in dhcp6.
From what I have seen by well behaved clients is that the client
always uses port 546 and the server always uses port 547. But,
dnsmasq have some
On Tue, 30 Oct 2012, Gene Czarcinski wrote:
1. dhcpv6 solicit: from=fe80::client:546 to=ff02::1:2:547
2. dhcpv6 advertise: from=fe80::server:547 to=fe80::client:546
3. dhcpv6 request: from=fe80::client:546 to=ff02::1:2:547
4. dhcpv6 reply: from=fe80::server:547 to=fe80::client:546
I
On 10/30/2012 06:45 PM, R P Herrold wrote:
I think the rules you want are these (we use the symbolic names for
the packet sub-type as it makes things clearer)
# /etc/sysconfig/ip6tables
# ... -A INPUT -p ipv6-icmp --icmpv6-type router-advertisement
-s $IP6SERVER -j ACCEPT
-A INPUT -p
On 10/27/2012 03:18 PM, Gene Czarcinski wrote:
OK, I have the basic implementation for libvirt support of dhcp6. Let
me say again that 98% of the work was already done. There is still a
bunch of work today which includes writing some tests, understanding
how things such as bootp, dhcp-host,
On 10/29/2012 08:26 AM, Gene Czarcinski wrote:
On 10/27/2012 03:18 PM, Gene Czarcinski wrote:
OK, I have the basic implementation for libvirt support of dhcp6. Let
me say again that 98% of the work was already done. There is still a
bunch of work today which includes writing some tests,
18 matches
Mail list logo
