[CentOS] IPv6 range provisioning question

Fri Jun 12 15:40:54 UTC 2009
David V <davevc at annapoliswireless.me>

Vadtec wrote:

> Yes, I know about IPV6ADDR_SECONDARIES. My goal was to provision an entire range
> automatically. I will handle the issue with a PHP CLI script run from rc.local
> to provision the IPs as needed.
> 
> Thanks for all the help.
> 
> Vadtec
> vadtec at vadtec.net

Hey I think I found exactly what you need. You simply can replace the 
ifup-ipv6 and network-functions-ipv6 script with ones that serves your 
needs.
I found them available at:
http://cvs.deepspace6.net/view/*checkout*/initscripts-ipv6/common/etc/sysconfig/network-scripts/network-functions-ipv6
and
http://cvs.deepspace6.net/view/*checkout*/initscripts-ipv6/common/etc/sysconfig/network-scripts/ifup-ipv6

I didn't check exactly what is changed in those files, but they do have 
the necessary functions to add a range and it did add a range when 
specified like:
IPV6ADDR_SECONDARIES="2001:4830:1128:4200::2/64 
2001:4830:1128:4200::3/64 2001:4830:1128:4200::4-90/64"

eth0      Link encap:Ethernet  HWaddr 00:30:18:B0:C0:91
           inet addr:10.8.9.248  Bcast:10.8.31.255  Mask:255.255.224.0
           inet6 addr: 2001:4830:1128:4200::88/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::77/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::66/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::55/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::44/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::33/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::22/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::11/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::89/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::76/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::67/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::54/64 Scope:Global
           inet6 addr: 2001:4830:1128:4200::45/64 Scope:Global
etc....

Those replacement files did not appear to cause any new issues on my 
CentOS 5.3 server.