Cobbler Dev's,
Does cobbler support ipv6 network configuration and if not what changes would be required to make that possible?
I'm writing a django app to track my hosts and some of the challenges I ran into while trying to model the network information was that in order to support ipv6 network configurations I had to allow for the case where an interface name such as eth0 could have multiple ip addresses assigned. For instance you can have an interface with an ipv4 ip, and many other ipv6 ip addresses or combinations of that. I believe Redhat calls the additional ip addresses "ipv6 secondaries". Looking at the code:
self.name = None self.cidr = None self.address = None self.gateway = None self.broadcast = None self.name_servers = [] self.reserved = [] self.used_addresses = {} self.free_addresses = [] self.comment = "" self.ctime = 0 self.mtime = 0 self.owners = self.settings.default_ownership
If the ip address fields were containers perhaps they could store more than a single ip address. The RedHat network config stanzas use different names to configure the interfaces and network settings such as:
/etc/sysconfig/network
NOZEROCONF=yes NETWORKING_IPV6=yes IPV6_AUTOCONF=no IPV6_DEFAULTDEV=eth0
/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0 BOOTPROTO=static HWADDR=00:43:86:03:h0:45 ONBOOT=yes IPADDR=192.168.1.1 NETMASK=255.255.255.240 ETHTOOL_OPTS="speed 100 duplex full autoneg off" IPV6INIT=yes IPV6ADDR=2001:12f8:1::10/64 IPV6ADDR_SECONDARIES=FE80::3 IPV6_DEFAULTGW=FE80::1
So maybe you would just give them separate names? I would like to try to manage my systems network configuration with cobbler and build fully configured (ipv4 and ipv6) interfaces. If more than just myself are interested in having this functionality added what do you think the best way to go about it would be?
I was also wondering about configuring /etc/sysconfig/static-routes-ipv6.
Thanks,
Jonathan
Jon Sabo wrote:
Cobbler Dev's,
Does cobbler support ipv6 network configuration and if not what changes would be required to make that possible?
We are mostly using python-netaddr for input validation, though there's likely that more has to change.
I'm writing a django app to track my hosts and some of the challenges I ran into while trying to model the network information was that in order to support ipv6 network configurations I had to allow for the case where an interface name such as eth0 could have multiple ip addresses assigned. For instance you can have an interface with an ipv4 ip, and many other ipv6 ip addresses or combinations of that. I believe Redhat calls the additional ip addresses "ipv6 secondaries". Looking at the code:
Yes, I recall someone mentioning this ... this is one thing we'd have to be able to do, store those internally as lists, not scalars, and have cobbler migrate folks automatically. This may require some changes in various templates.
self.name <http://self.name> = None self.cidr = None self.address = None self.gateway = None self.broadcast = None self.name_servers = [] self.reserved = [] self.used_addresses = {} self.free_addresses = [] self.comment = "" self.ctime = 0 self.mtime = 0 self.owners = self.settings.default_ownership
If the ip address fields were containers perhaps they could store more than a single ip address. The RedHat network config stanzas use different names to configure the interfaces and network settings such as:
/etc/sysconfig/network
NOZEROCONF=yes NETWORKING_IPV6=yes IPV6_AUTOCONF=no IPV6_DEFAULTDEV=eth0
/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0 BOOTPROTO=static HWADDR=00:43:86:03:h0:45 ONBOOT=yes IPADDR=192.168.1.1 NETMASK=255.255.255.240 ETHTOOL_OPTS="speed 100 duplex full autoneg off" IPV6INIT=yes IPV6ADDR=2001:12f8:1::10/64 IPV6ADDR_SECONDARIES=FE80::3 IPV6_DEFAULTGW=FE80::1
So maybe you would just give them separate names? I would like to try to manage my systems network configuration with cobbler and build fully configured (ipv4 and ipv6) interfaces. If more than just myself are interested in having this functionality added what do you think the best way to go about it would be?
This might also work, though may also be less intuitive, anyone else have thoughts?
Would we store ipv6 addresses and ipv4 addresses in the same list if it was all one list?
I was also wondering about configuring /etc/sysconfig/static-routes-ipv6.
Right, that's not modelled right now. I'm not sure if we end up creating a --static-routes-ipv6 or not... seems like yes.
Anyway, I welcome any and all patches to support this. It hasn't been requested much up until this point but I'm all in favor of things being comprehensive.
cobbler-devel@lists.fedorahosted.org