-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A few months back, I tried to use the network scripts to provision an IPv6 range like can be done with IPv4. I was using CentOS 5.2 at the time and was informed that 5.2 was broken in this regard. I have upgraded to CentOS 5.3 now and I am trying to get IPv6 to provision an entire range of IPs, but I am still getting the old behavior and no IPs are being provisioned.
I have been following the docs provided by the link in the /etc/sysconfig/network-scripts/ifup-ipv6 at http://www.deepspace6.net/projects/initscripts-ipv6.html#id2801589 and using the following configs:
/etc/sysconfig/network NETWORKING=yes GATEWAY=***.***.***.*** GATEWAYDEV=eth0 HOSTNAME=vadtec
NETWORKING_IPV6=yes IPV6FORWARDING=no IPV6_AUTOCONF=no IPV6_AUTOTUNNEL=no IPV6_DEFAULTDEV=eth0:1 IPV6_DEFAULTGW=2001:0470:0103:001A::1
/etc/sysconfig/network-scripts/ifcfg-eth0-1 DEVICE=eth0:1 IPV6INIT=yes IPV6ADDR=2001:0470:0103:001A:0001:0000:0000:0000:/96 IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no ONBOOT=no
When I run service network restart, it doesn't even provision the default IPv6 GW on eth0:1, nor does eth0:1 even show up.
If I run tail /var/log/boot.log, boot.log is empty. If I run tail /var/log/messages, I see varying amounts of:
Jun 10 11:42:14 localhost kernel: [208192.884652] eth0: duplicate address detected!
I see no other errors or messages saying anything is wrong or otherwise.
This is becoming very tiresome. It would be really nice to be able to provision IPv6 ranges as needed instead of having to place scripts in rc.local to manually provision the IPs that are needed, one by one. Any help is greatly appreciated.
Vadtec vadtec@vadtec.net
On Wed, 2009-06-10 at 13:08 -0500, Vadtec wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A few months back, I tried to use the network scripts to provision an IPv6 range like can be done with IPv4. I was using CentOS 5.2 at the time and was informed that 5.2 was broken in this regard. I have upgraded to CentOS 5.3 now and I am trying to get IPv6 to provision an entire range of IPs, but I am still getting the old behavior and no IPs are being provisioned.
I have been following the docs provided by the link in the /etc/sysconfig/network-scripts/ifup-ipv6 at http://www.deepspace6.net/projects/initscripts-ipv6.html#id2801589 and using the following configs:
/etc/sysconfig/network NETWORKING=yes GATEWAY=***.***.***.*** GATEWAYDEV=eth0 HOSTNAME=vadtec
NETWORKING_IPV6=yes IPV6FORWARDING=no IPV6_AUTOCONF=no IPV6_AUTOTUNNEL=no IPV6_DEFAULTDEV=eth0:1 IPV6_DEFAULTGW=2001:0470:0103:001A::1
/etc/sysconfig/network-scripts/ifcfg-eth0-1
Why do you need an alias device here? Put the ipv6 config on the eth0 device,and add the configuration to the ifcfg-eth0 file
DEVICE=eth0:1 IPV6INIT=yes IPV6ADDR=2001:0470:0103:001A:0001:0000:0000:0000:/96
You are allocating a /96 with all 0 in the last 32 bits. So you are not allocating an address. Why a /96? Using a /64 is pretty much the standard for ipv6.
IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no ONBOOT=no
When I run service network restart, it doesn't even provision the default IPv6 GW on eth0:1, nor does eth0:1 even show up.
I must admit I never tried an v6 address on an alias, so I have no clue whether it works or not. But you can have both v4 and v6 addresses next to each other on the eth0 device
If I run tail /var/log/boot.log, boot.log is empty. If I run tail /var/log/messages, I see varying amounts of:
Jun 10 11:42:14 localhost kernel: [208192.884652] eth0: duplicate address detected!
Probably due to the all 0 in the part AFTER the /96
I see no other errors or messages saying anything is wrong or otherwise.
Autoconfiguration is the way to go if you want to make it easy. On my server I set the addresses manually like DEVICE=eth0.159 ONBOOT=yes BOOTPROTO=none NETMASK=255.255.255.0 HWADDR=00:1a:92:d6:99:91 IPADDR=192.168.159.1 #GATEWAY=192.168.178.1 TYPE=Ethernet USERCTL=no IPV6INIT=yes IPV6FORWARDING="yes" # v6 address changed to protect the innocent IPV6ADDR="2001:888:118e:18a2::1/64" PEERDNS=no VLAN=yes Please not that I am using vlans, hence the .159 on the eth0. Normally you do not need that and you leave the VLAN=yes off. Please note the ::1 at the end of the address. I use radvd on that machine (so here I need to set fixed v6 addresses), but the clients do not neede that:
DEVICE=eth0 BOOTPROTO=none DNS1=192.168.159.1 IPADDR=192.168.159.3 NETMASK=255.255.255.0 HWADDR=00:11:d8:be:98:fa ONBOOT=yes SEARCH="pheasant" USERCTL=no PEERDNS=no IPV6INIT=yes NM_CONTROLLED=yes GATEWAY=192.168.159.1 TYPE=Ethernet
Here the address is set depending on the (/64) prefix received from the radvd server.....
kind regards, Louis
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Louis Lagendijk wrote:
On Wed, 2009-06-10 at 13:08 -0500, Vadtec wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A few months back, I tried to use the network scripts to provision an IPv6 range like can be done with IPv4. I was using CentOS 5.2 at the time and was informed that 5.2 was broken in this regard. I have upgraded to CentOS 5.3 now and I am trying to get IPv6 to provision an entire range of IPs, but I am still getting the old behavior and no IPs are being provisioned.
I have been following the docs provided by the link in the /etc/sysconfig/network-scripts/ifup-ipv6 at http://www.deepspace6.net/projects/initscripts-ipv6.html#id2801589 and using the following configs:
/etc/sysconfig/network NETWORKING=yes GATEWAY=***.***.***.*** GATEWAYDEV=eth0 HOSTNAME=vadtec
NETWORKING_IPV6=yes IPV6FORWARDING=no IPV6_AUTOCONF=no IPV6_AUTOTUNNEL=no IPV6_DEFAULTDEV=eth0:1 IPV6_DEFAULTGW=2001:0470:0103:001A::1
/etc/sysconfig/network-scripts/ifcfg-eth0-1
Why do you need an alias device here? Put the ipv6 config on the eth0 device,and add the configuration to the ifcfg-eth0 file
DEVICE=eth0:1 IPV6INIT=yes IPV6ADDR=2001:0470:0103:001A:0001:0000:0000:0000:/96
You are allocating a /96 with all 0 in the last 32 bits. So you are not allocating an address. Why a /96? Using a /64 is pretty much the standard for ipv6.
IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no ONBOOT=no
When I run service network restart, it doesn't even provision the default IPv6 GW on eth0:1, nor does eth0:1 even show up.
I must admit I never tried an v6 address on an alias, so I have no clue whether it works or not. But you can have both v4 and v6 addresses next to each other on the eth0 device
If I run tail /var/log/boot.log, boot.log is empty. If I run tail /var/log/messages, I see varying amounts of:
Jun 10 11:42:14 localhost kernel: [208192.884652] eth0: duplicate address detected!
Probably due to the all 0 in the part AFTER the /96
I see no other errors or messages saying anything is wrong or otherwise.
Autoconfiguration is the way to go if you want to make it easy. On my server I set the addresses manually like DEVICE=eth0.159 ONBOOT=yes BOOTPROTO=none NETMASK=255.255.255.0 HWADDR=00:1a:92:d6:99:91 IPADDR=192.168.159.1 #GATEWAY=192.168.178.1 TYPE=Ethernet USERCTL=no IPV6INIT=yes IPV6FORWARDING="yes" # v6 address changed to protect the innocent IPV6ADDR="2001:888:118e:18a2::1/64" PEERDNS=no VLAN=yes Please not that I am using vlans, hence the .159 on the eth0. Normally you do not need that and you leave the VLAN=yes off. Please note the ::1 at the end of the address. I use radvd on that machine (so here I need to set fixed v6 addresses), but the clients do not neede that:
DEVICE=eth0 BOOTPROTO=none DNS1=192.168.159.1 IPADDR=192.168.159.3 NETMASK=255.255.255.0 HWADDR=00:11:d8:be:98:fa ONBOOT=yes SEARCH="pheasant" USERCTL=no PEERDNS=no IPV6INIT=yes NM_CONTROLLED=yes GATEWAY=192.168.159.1 TYPE=Ethernet
Here the address is set depending on the (/64) prefix received from the radvd server.....
kind regards, Louis
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Thanks for the tip about having all zeros at the end of the IP. I figured the script would go ahead and provision the IPs anyways. The reason I was using a /96 is because the machine happens to be a VPS with only 128MB of RAM, so I figured the less IPs I provision the less memory it will take up, which is limitted anyways. I also do not want to use radvd or auto configuration because I do not need to broadcast or forward ipv6 on this vps.
As per your suggestions, I removed the extra zeros and changed the prefix to /64.
I am now using the following configs:
/etc/sysconfig/network: NETWORKING=yes GATEWAY=67.202.107.1 GATEWAYDEV=eth0 HOSTNAME=vadtec
NETWORKING_IPV6=yes IPV6FORWARDING=no IPV6_AUTOCONF=no IPV6_AUTOTUNNEL=no IPV6_DEFAULTDEV=eth0 IPV6_DEFAULTGW="2001:0470:0103:001A::1"
/etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 IPADDR=***.***.***.*** NETMASK=255.255.255.0 BROADCAST=***.***.***.*** ONBOOT=yes
IPV6INIT=yes IPV6ADDR="2001:0470:0103:001A::2/64" IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no PEERDNS=no VLAN=no
However, this is not provisioning an entire range as follows:
eth0 Link encap:Ethernet HWaddr 00:16:3E:70:FC:96 inet addr:***.***.***.*** Bcast:***.***.***.*** Mask:255.255.255.0 inet6 addr: 2001:470:103:1a::2/64 Scope:Global inet6 addr: fe80::216:3eff:fe70:fc96/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:70 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6738 (6.5 KiB) TX bytes:2050 (2.0 KiB)
I also have a large number of "unreachable" routes shown on the local loopback when I do ip -6 route show: unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
I assume those are something to do with how IPv6 works, but I'm not sure.
So, back to my original question, I have it provisioning *one* IP, how do I get it to provision a *range* of IPs. As I said above, this is a VPS that does not need to broadcast any of its IPs or forward IPv6. I just need to be able to provision a range of IPv6.
Thanks for the help so far!
Vadtec vadtec@vadtec.net
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
So can anyone offer any insight into this? See my reply at the bottom of the message.
Vadtec vadtec@vadtec.net
Vadtec wrote:
Louis Lagendijk wrote:
On Wed, 2009-06-10 at 13:08 -0500, Vadtec wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
A few months back, I tried to use the network scripts to provision an IPv6 range like can be done with IPv4. I was using CentOS 5.2 at the time and was informed that 5.2 was broken in this regard. I have upgraded to CentOS 5.3 now and I am trying to get IPv6 to provision an entire range of IPs, but I am still getting the old behavior and no IPs are being provisioned.
I have been following the docs provided by the link in the /etc/sysconfig/network-scripts/ifup-ipv6 at http://www.deepspace6.net/projects/initscripts-ipv6.html#id2801589 and using the following configs:
/etc/sysconfig/network NETWORKING=yes GATEWAY=***.***.***.*** GATEWAYDEV=eth0 HOSTNAME=vadtec
NETWORKING_IPV6=yes IPV6FORWARDING=no IPV6_AUTOCONF=no IPV6_AUTOTUNNEL=no IPV6_DEFAULTDEV=eth0:1 IPV6_DEFAULTGW=2001:0470:0103:001A::1
/etc/sysconfig/network-scripts/ifcfg-eth0-1
Why do you need an alias device here? Put the ipv6 config on the eth0 device,and add the configuration to the ifcfg-eth0 file
DEVICE=eth0:1 IPV6INIT=yes IPV6ADDR=2001:0470:0103:001A:0001:0000:0000:0000:/96
You are allocating a /96 with all 0 in the last 32 bits. So you are not allocating an address. Why a /96? Using a /64 is pretty much the standard for ipv6.
IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no ONBOOT=no
When I run service network restart, it doesn't even provision the default IPv6 GW on eth0:1, nor does eth0:1 even show up.
I must admit I never tried an v6 address on an alias, so I have no clue whether it works or not. But you can have both v4 and v6 addresses next to each other on the eth0 device
If I run tail /var/log/boot.log, boot.log is empty. If I run tail /var/log/messages, I see varying amounts of:
Jun 10 11:42:14 localhost kernel: [208192.884652] eth0: duplicate address detected!
Probably due to the all 0 in the part AFTER the /96
I see no other errors or messages saying anything is wrong or otherwise.
Autoconfiguration is the way to go if you want to make it easy. On my server I set the addresses manually like DEVICE=eth0.159 ONBOOT=yes BOOTPROTO=none NETMASK=255.255.255.0 HWADDR=00:1a:92:d6:99:91 IPADDR=192.168.159.1 #GATEWAY=192.168.178.1 TYPE=Ethernet USERCTL=no IPV6INIT=yes IPV6FORWARDING="yes" # v6 address changed to protect the innocent IPV6ADDR="2001:888:118e:18a2::1/64" PEERDNS=no VLAN=yes Please not that I am using vlans, hence the .159 on the eth0. Normally you do not need that and you leave the VLAN=yes off. Please note the ::1 at the end of the address. I use radvd on that machine (so here I need to set fixed v6 addresses), but the clients do not neede that:
DEVICE=eth0 BOOTPROTO=none DNS1=192.168.159.1 IPADDR=192.168.159.3 NETMASK=255.255.255.0 HWADDR=00:11:d8:be:98:fa ONBOOT=yes SEARCH="pheasant" USERCTL=no PEERDNS=no IPV6INIT=yes NM_CONTROLLED=yes GATEWAY=192.168.159.1 TYPE=Ethernet
Here the address is set depending on the (/64) prefix received from the radvd server.....
kind regards, Louis
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Thanks for the tip about having all zeros at the end of the IP. I figured the script would go ahead and provision the IPs anyways. The reason I was using a /96 is because the machine happens to be a VPS with only 128MB of RAM, so I figured the less IPs I provision the less memory it will take up, which is limitted anyways. I also do not want to use radvd or auto configuration because I do not need to broadcast or forward ipv6 on this vps.
As per your suggestions, I removed the extra zeros and changed the prefix to /64.
I am now using the following configs:
/etc/sysconfig/network: NETWORKING=yes GATEWAY=67.202.107.1 GATEWAYDEV=eth0 HOSTNAME=vadtec
NETWORKING_IPV6=yes IPV6FORWARDING=no IPV6_AUTOCONF=no IPV6_AUTOTUNNEL=no IPV6_DEFAULTDEV=eth0 IPV6_DEFAULTGW="2001:0470:0103:001A::1"
/etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 IPADDR=***.***.***.*** NETMASK=255.255.255.0 BROADCAST=***.***.***.*** ONBOOT=yes
IPV6INIT=yes IPV6ADDR="2001:0470:0103:001A::2/64" IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no PEERDNS=no VLAN=no
However, this is not provisioning an entire range as follows:
eth0 Link encap:Ethernet HWaddr 00:16:3E:70:FC:96 inet addr:***.***.***.*** Bcast:***.***.***.*** Mask:255.255.255.0 inet6 addr: 2001:470:103:1a::2/64 Scope:Global inet6 addr: fe80::216:3eff:fe70:fc96/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:70 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6738 (6.5 KiB) TX bytes:2050 (2.0 KiB)
I also have a large number of "unreachable" routes shown on the local loopback when I do ip -6 route show: unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
I assume those are something to do with how IPv6 works, but I'm not sure.
So, back to my original question, I have it provisioning *one* IP, how do I get it to provision a *range* of IPs. As I said above, this is a VPS that does not need to broadcast any of its IPs or forward IPv6. I just need to be able to provision a range of IPv6.
Thanks for the help so far!
Vadtec vadtec@vadtec.net
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2009-06-11 at 10:49 -0500, Vadtec wrote:
A few months back, I tried to use the network scripts to provision an IPv6 range like can be done with IPv4. I was using CentOS 5.2 at the time and was informed that 5.2 was broken in this regard. I have upgraded to CentOS 5.3 now and I am trying to get IPv6 to provision an entire range of IPs, but I am still getting the old behavior and no IPs are being provisioned.
I am really confused on what you want to do here. When you talk about a RANGE what do you mean? Allocate more than one IPv6 address to a single interface? If so, have a look at the IPV6ADDR_SECONDARIES clause in the link you included. I am not sure that you can use alias interfaces for IPv6. Put that in the ifcfg-ethx file, not in the config for the aliases (ifcfgx:y)
When I run service network restart, it doesn't even provision the default IPv6 GW on eth0:1, nor does eth0:1 even show up.
I don't think you can use alias interfaces for IPv6. It at least did not work on my other (Fedora) box IPV6ADDR_SECONDARIES on the device DOES work on Centos 5.3
However, this is not provisioning an entire range as follows:
eth0 Link encap:Ethernet HWaddr 00:16:3E:70:FC:96 inet addr:***.***.***.*** Bcast:***.***.***.*** Mask:255.255.255.0 inet6 addr: 2001:470:103:1a::2/64 Scope:Global inet6 addr: fe80::216:3eff:fe70:fc96/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:70 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6738 (6.5 KiB) TX bytes:2050 (2.0 KiB)
You have a single address provsioned indeed 2001:470:103:1a::2/64 with a network part of 64 bits.
I also have a large number of "unreachable" routes shown on the local loopback when I do ip -6 route show: unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
Nothing to worry abouot. I have that too:
[root@nest network-scripts]# ip -r ro sh 192.168.178.0/24 dev eth0.178 proto kernel scope link src 192.168.178.2 192.168.160.0/24 dev eth0.160 proto kernel scope link src 192.168.160.1 192.168.1.0/24 dev eth0.1 proto kernel scope link src 192.168.1.1 192.168.159.0/24 dev eth0.159 proto kernel scope link src 192.168.159.1 192.168.158.0/24 dev eth0.158 proto kernel scope link src 192.168.158.1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 169.254.0.0/16 dev eth0.178 scope link default via fritz.pheasant dev eth0.178 [root@nest network-scripts]# ip -6 ro sh ::/96 via :: dev sit0 metric 256 mtu 1480 advmss 1420 hoplimit 4294967295 unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 2001:888:10:18e::/64 via :: dev sit1 proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 4294967295 2001:888:118e:18e1::/64 dev eth0.158 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2001:888:118e:18e2::/64 dev eth0.159 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2001:888:118e:18e3::/64 dev eth0.160 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2001:888:118e:18e4::/64 dev eth0.178 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 2000::/3 dev sit1 metric 1 mtu 1480 advmss 1420 hoplimit 4294967295 fe80::/64 dev virbr0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 via :: dev sit1 proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 4294967295 fe80::/64 dev eth0.1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0.158 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0.159 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0.160 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0.178 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 default dev sit1 metric 1 mtu 1480 advmss 1420 hoplimit 4294967295
Louis
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ok, firstly, I have dropped using the alias notation and am now working solely on eth0.
Secondly, yes, I am talking about provisioning more than *one* IP at a time as being a "range".
As for IPV6ADDR_SECONDARIES, when I use the following config: /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 IPADDR=***.***.***.*** NETMASK=255.255.255.0 BROADCAST=***.***.***.*** ONBOOT=yes
IPV6INIT=yes IPV6ADDR="2001:0470:0103:001A::2/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::3-2001:0470:0103:001A::FFFF" IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no PEERDNS=no VLAN=no
I get the following error:
Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: ERROR : [ipv6_test_ipv6_addr_valid] Given IPv6 address '2001:0470:0103:001A::3-FFFF' is not valid WARN : [ipv6_add_route] 'No route to host' adding route '::/0' via gateway '2001:0470:0103:001A::1' through device 'eth0' [ OK ] eth0 Link encap:Ethernet HWaddr 00:16:3E:70:FC:96 inet addr:***.***.***.*** Bcast:***.***.***.*** Mask:255.255.255.0 inet6 addr: fe80::216:3eff:fe70:fc96/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:31 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2270 (2.2 KiB) TX bytes:406 (406.0 b)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:141521 errors:0 dropped:0 overruns:0 frame:0 TX packets:141521 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:23702410 (22.6 MiB) TX bytes:23702410 (22.6 MiB)
I also tried the following config: /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 IPADDR=***.***.***.*** NETMASK=255.255.255.0 BROADCAST=***.***.***.*** ONBOOT=yes
IPV6INIT=yes IPV6ADDR="2001:0470:0103:001A::2/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::3-2001:0470:0103:001A::FFFF" IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no PEERDNS=no VLAN=no
And receive the following error: Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: ERROR : [ipv6_test_ipv6_addr_valid] Given IPv6 address '2001:0470:0103:001A::3-2001:0470:0103:001A::FFFF' is not valid [ OK ] eth0 Link encap:Ethernet HWaddr 00:16:3E:70:FC:96 inet addr:***.***.***.*** Bcast:***.***.***.*** Mask:255.255.255.0 inet6 addr: 2001:470:103:1a::2/64 Scope:Global inet6 addr: fe80::216:3eff:fe70:fc96/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2643 (2.5 KiB) TX bytes:516 (516.0 b)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:141716 errors:0 dropped:0 overruns:0 frame:0 TX packets:141716 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:23744895 (22.6 MiB) TX bytes:23744895 (22.6 MiB)
After doing some digging in the ifup-ipv6 and network-functions-ipv6 scripts, it doesn't appear that IPV6ADDR_SECONDARIES actually supports the X-Y notation in the current release. I see no where that the hyphen is removed and a range is generated. I'm not the most powerful bash scripter in the world, so I could be wrong.
Can anyone else weigh in on the subject and provide some more insight? It would be really nice to provision an entire range of IPv6 and not have to add them one by one.
Vadtec vadtec@vadtec.net
Louis Lagendijk wrote:
On Thu, 2009-06-11 at 10:49 -0500, Vadtec wrote:
A few months back, I tried to use the network scripts to provision an IPv6 range like can be done with IPv4. I was using CentOS 5.2 at the time and was informed that 5.2 was broken in this regard. I have upgraded to CentOS 5.3 now and I am trying to get IPv6 to provision an entire range of IPs, but I am still getting the old behavior and no IPs are being provisioned.
I am really confused on what you want to do here. When you talk about a RANGE what do you mean? Allocate more than one IPv6 address to a single interface? If so, have a look at the IPV6ADDR_SECONDARIES clause in the link you included. I am not sure that you can use alias interfaces for IPv6. Put that in the ifcfg-ethx file, not in the config for the aliases (ifcfgx:y)
When I run service network restart, it doesn't even provision the default IPv6 GW on eth0:1, nor does eth0:1 even show up.
I don't think you can use alias interfaces for IPv6. It at least did not work on my other (Fedora) box IPV6ADDR_SECONDARIES on the device DOES work on Centos 5.3
However, this is not provisioning an entire range as follows:
eth0 Link encap:Ethernet HWaddr 00:16:3E:70:FC:96 inet addr:***.***.***.*** Bcast:***.***.***.*** Mask:255.255.255.0 inet6 addr: 2001:470:103:1a::2/64 Scope:Global inet6 addr: fe80::216:3eff:fe70:fc96/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:70 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:6738 (6.5 KiB) TX bytes:2050 (2.0 KiB)
You have a single address provsioned indeed 2001:470:103:1a::2/64 with a network part of 64 bits.
I also have a large number of "unreachable" routes shown on the local loopback when I do ip -6 route show: unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
Nothing to worry abouot. I have that too:
[root@nest network-scripts]# ip -r ro sh 192.168.178.0/24 dev eth0.178 proto kernel scope link src 192.168.178.2 192.168.160.0/24 dev eth0.160 proto kernel scope link src 192.168.160.1 192.168.1.0/24 dev eth0.1 proto kernel scope link src 192.168.1.1 192.168.159.0/24 dev eth0.159 proto kernel scope link src 192.168.159.1 192.168.158.0/24 dev eth0.158 proto kernel scope link src 192.168.158.1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 169.254.0.0/16 dev eth0.178 scope link default via fritz.pheasant dev eth0.178 [root@nest network-scripts]# ip -6 ro sh ::/96 via :: dev sit0 metric 256 mtu 1480 advmss 1420 hoplimit 4294967295 unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 2001:888:10:18e::/64 via :: dev sit1 proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 4294967295 2001:888:118e:18e1::/64 dev eth0.158 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2001:888:118e:18e2::/64 dev eth0.159 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2001:888:118e:18e3::/64 dev eth0.160 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2001:888:118e:18e4::/64 dev eth0.178 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295 2000::/3 dev sit1 metric 1 mtu 1480 advmss 1420 hoplimit 4294967295 fe80::/64 dev virbr0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 via :: dev sit1 proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 4294967295 fe80::/64 dev eth0.1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0.158 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0.159 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0.160 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0.178 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 default dev sit1 metric 1 mtu 1480 advmss 1420 hoplimit 4294967295
Louis
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2009-06-11 at 14:46 -0500, Vadtec wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ok, firstly, I have dropped using the alias notation and am now working solely on eth0.
Secondly, yes, I am talking about provisioning more than *one* IP at a time as being a "range".
As for IPV6ADDR_SECONDARIES, when I use the following config: /etc/sysconfig/network-scripts/ifcfg-eth0: DEVICE=eth0 IPADDR=***.***.***.*** NETMASK=255.255.255.0 BROADCAST=***.***.***.*** ONBOOT=yes
IPV6INIT=yes IPV6ADDR="2001:0470:0103:001A::2/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::3-2001:0470:0103:001A::FFFF" IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no PEERDNS=no VLAN=no
I get the following error:
Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: ERROR : [ipv6_test_ipv6_addr_valid] Given IPv6 address '2001:0470:0103:001A::3-FFFF' is not valid WARN : [ipv6_add_route] 'No route to host' adding route '::/0' via gateway '2001:0470:0103:001A::1' through device 'eth0'
the file /usr/share/doc/initscripts-8.45.25/sysconfig.txt does NOT mention the - for ranges either, so I guess you are out of luck. Louis
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Louis Lagendijk wrote: <snip>
the file /usr/share/doc/initscripts-8.45.25/sysconfig.txt does NOT mention the - for ranges either, so I guess you are out of luck. Louis
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Indeed it doesn't. Guess I'm just out of luck for the time being. Maybe the support will be added soon enough.
Thanks for your help.
Vadtec vadtec@vadtec.net
Vadtec wrote:
Indeed it doesn't. Guess I'm just out of luck for the time being. Maybe the support will be added soon enough.
Thanks for your help.
Hey I'm not sure if this has been mentioned, but even if a range is not allowed you can still have as many IPV6_SECONDARIES lines as you want, i.e.
IPV6INIT=yes IPV6ADDR="2001:0470:0103:001A::2/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::3/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::4/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::5/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::6/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::7/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::8/64" IPV6_AUTOCONF=no IPV6_ROUTER=no IPV6FORWARDING=no PEERDNS=no VLAN=no
I know it's inconvenient for the range you listed, but should work fine for a few.
-Dave
Hi,
On Fri, Jun 12, 2009 at 09:07, David Vdavevc@annapoliswireless.me wrote:
Hey I'm not sure if this has been mentioned, but even if a range is not allowed you can still have as many IPV6_SECONDARIES lines as you want, i.e. IPV6ADDR_SECONDARIES="2001:0470:0103:001A::3/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::4/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::5/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::6/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::7/64" IPV6ADDR_SECONDARIES="2001:0470:0103:001A::8/64"
I really doubt that this will work with this exact syntax, as these are Bourne shell variable assignments and each of them will overwrite the previous one...
Shouldn't it be something like this? IPV6ADDR_SECONDARIES="2001:0470:0103:001A::3/64 2001:0470:0103:001A::4/64 2001:0470:0103:001A::5/64 2001:0470:0103:001A::6/64 2001:0470:0103:001A::7/64 2001:0470:0103:001A::8/64"
HTH, Filipe
Filipe Brandenburger wrote:
I really doubt that this will work with this exact syntax, as these are Bourne shell variable assignments and each of them will overwrite the previous one...
Shouldn't it be something like this? IPV6ADDR_SECONDARIES="2001:0470:0103:001A::3/64 2001:0470:0103:001A::4/64 2001:0470:0103:001A::5/64 2001:0470:0103:001A::6/64 2001:0470:0103:001A::7/64 2001:0470:0103:001A::8/64"
Looking in /etc/sysconfig/network-scripts, a quick grep shows that ifup-ipv6 handles the IPV6ADDR_SECONDARIES.
The comments at the top of this file state: # IPV6ADDR_SECONDARIES="<IPv6 address>[/<prefix length>] ..." (optional)
so yes indeed that appears to be the correct syntax...in fact later in the script IPV6ADDR_SECONDARIES gets walked through in a for loop: # Setup additional IPv6 addresses from list, if given if [ -n "$IPV6ADDR_SECONDARIES" ]; then for ipv6addr in $IPV6ADDR_SECONDARIES; do ipv6_add_addr_on_device $DEVICE $ipv6addr done fi
-Shawn
Filipe Brandenburger wrote:
Shouldn't it be something like this? IPV6ADDR_SECONDARIES="2001:0470:0103:001A::3/64 2001:0470:0103:001A::4/64 2001:0470:0103:001A::5/64 2001:0470:0103:001A::6/64 2001:0470:0103:001A::7/64 2001:0470:0103:001A::8/64"
HTH, Filipe
Thanks Felipe and Shawn, guess I hadn't tested it enough yet. That is the correct syntax.
Here is an example from one of my boxes:
[dveasey@test network-scripts]$ more ifcfg-eth0 USERCTL=yes DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Ethernet ETHTOOL_OPTS="speed 100 duplex full autoneg off" IPV6INIT=yes IPV6ADDR=2001:1938:108:4400::2/64 IPV6ADDR_SECONDARIES="2001:4830:1128:4200::2/64 2001:4830:1128:4200::3/64 2001:4830:1128:4200::4/64" PEERDNS=yes
[dveasey@test network-scripts]$ /sbin/ip addr ls dev eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:30:18:b0:c0:91 brd ff:ff:ff:ff:ff:ff inet 10.8.9.248/19 brd 10.8.31.255 scope global eth0 inet6 2001:4830:1128:4200::4/64 scope global valid_lft forever preferred_lft forever inet6 2001:4830:1128:4200::3/64 scope global valid_lft forever preferred_lft forever inet6 2001:4830:1128:4200::2/64 scope global valid_lft forever preferred_lft forever inet6 2001:1938:108:4400::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::230:18ff:feb0:c091/64 scope link valid_lft forever preferred_lft forever
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
David V wrote:
Filipe Brandenburger wrote:
Shouldn't it be something like this? IPV6ADDR_SECONDARIES="2001:0470:0103:001A::3/64 2001:0470:0103:001A::4/64 2001:0470:0103:001A::5/64 2001:0470:0103:001A::6/64 2001:0470:0103:001A::7/64 2001:0470:0103:001A::8/64"
HTH, Filipe
Thanks Felipe and Shawn, guess I hadn't tested it enough yet. That is the correct syntax.
Here is an example from one of my boxes:
[dveasey@test network-scripts]$ more ifcfg-eth0 USERCTL=yes DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes TYPE=Ethernet ETHTOOL_OPTS="speed 100 duplex full autoneg off" IPV6INIT=yes IPV6ADDR=2001:1938:108:4400::2/64 IPV6ADDR_SECONDARIES="2001:4830:1128:4200::2/64 2001:4830:1128:4200::3/64 2001:4830:1128:4200::4/64" PEERDNS=yes
[dveasey@test network-scripts]$ /sbin/ip addr ls dev eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:30:18:b0:c0:91 brd ff:ff:ff:ff:ff:ff inet 10.8.9.248/19 brd 10.8.31.255 scope global eth0 inet6 2001:4830:1128:4200::4/64 scope global valid_lft forever preferred_lft forever inet6 2001:4830:1128:4200::3/64 scope global valid_lft forever preferred_lft forever inet6 2001:4830:1128:4200::2/64 scope global valid_lft forever preferred_lft forever inet6 2001:1938:108:4400::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::230:18ff:feb0:c091/64 scope link valid_lft forever preferred_lft forever _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
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@vadtec.net
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@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/syscon... and http://cvs.deepspace6.net/view/*checkout*/initscripts-ipv6/common/etc/syscon...
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.
Hi,
On Thu, Jun 11, 2009 at 11:49, Vadtecvadtec@vadtec.net wrote:
So can anyone offer any insight into this? See my reply at the bottom of the message.
I never used IPv6, so I don't know if that applies to IPv6 too or to IPv4 only.
In IPv4 it is possible to assign a whole range to a specific machine by adding it as an alias to the loopback interface.
For instance, if I do:
ifconfig lo:0 192.168.99.32 netmask 255.255.255.224
Then the machine will answer to all the addresses from 192.168.99.32 to 192.168.99.63. If you use a range that is in the same subnet as the IP you have in eth0, it will respond to ARP requests in that interface as well, so it will do exactly what you want.
I don't know if and how that would work with IPv6, but maybe try doing that, assigning a single IP with a proper network mask to an alias of the loopback interface and see if that works as you expect.
HTH, Filipe
-
David V -
Filipe Brandenburger -
Louis Lagendijk -
Shawn O'Shea -
Vadtec