Re: [CentOS] IPv6 docs, howtos, descriptions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 j.witvl...@mindef.nl wrote: *From:* centos-boun...@centos.org [mailto:centos-boun...@centos.org] *On Behalf Of *Tony Asnicar *Sent:* Friday, June 12, 2009 12:38 PM *To:* centos@centos.org; fedora-l...@redhat.com; debian-u...@lists.debian.org; ubuntu-us...@lists.ubuntu.com *Subject:* [CentOS] IPv6 docs, howtos, descriptions I know...google...BUT: Does someone has good howtos, docs, descriptions, opinions in forums, or similar things about IPv6 and related things? I just think it would be a very good idea to collect some links about it... Regards, and thank you in anticipation much info at: http://www.tunnelbroker.net/forums/index.php?PHPSESSID=5ed651d73b5ce537820eeddd11bf0df1board=2.0 http://www.tunnelbroker.net/forums/index.php?PHPSESSID=5ed651d73b5ce537820eeddd11bf0df1board=2.0 If you login with your (free!) account there are a bunch of examples scripts for any OS Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos If you are going to post in another language, please also post in English. It does the mailing list no good for you to post in a language not everyone can read. Vadtec vad...@vadtec.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJKMkYdAAoJEEJXIw5V8gief/8P/02Ddfdy3Ms+00YgfyedgCbC 3jrXo/CWcyKo+VYKXwJxUNgXwiQjRA0hl9RalH6W/jdeVlu0dLhsMwKK8OtPqrdo 4JO5rt2tofdQSnMGeTksDokBETvMfYSss452ghK3No+TLMXpUoKn4sSlRw6xBN3H mpT9yoLRN1q1FSF6/qLoarb+kVGXt4pqHIkbBe0LbQx89eoUOTrz2v1OYL/PiekG VVThS8aU4rhvEZBn7/pGUnJCXXPsJ53zpsJKFCl8uevtESPruyd3WEGQvMv6aPbb mpKnWuRtEJvCY8nUh3x+ReAzhtw5eoVdVlBzVIKfJ4mi/siy39fAkE+ndx/b0ozV 7cA+RwXL4trCh+UC11Zp+AhWFiUC3meGiK3FY5HCyf/upf0wZKOok1vbLoHzyIon ZEbDJEtsUIdX+DVk3WYhu0WQQVMbViEofC1FuGkq5x4s5ne+WY+qHlbyL/Ge3y2Q Gys8EFTU33UNZM23mZYYNphgIj6ZxwFpGyBJbfLzbguKvoGaVHEiqRg+FWY/SqpS NmNtW8Ukoa8jqPQeDxbxbk/sCAJcpForuFDLwakucMzX501pORTDmoA/QTQWch6I B0GsKN64efY5dLuFTxH3qk3R5Cqt7C0l+D2+1JpP6rPPUjLjIY6TE2X40tBnndW1 6pxsK0fGtMcAriZisQd+ =cEvM -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPv6 docs, howtos, descriptions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Mathis wrote: On Fri, Jun 12, 2009 at 8:12 AM, Vadtecvad...@vadtec.net wrote: j.witvl...@mindef.nl wrote: *From:* centos-boun...@centos.org [mailto:centos-boun...@centos.org] *On Behalf Of *Tony Asnicar *Sent:* Friday, June 12, 2009 12:38 PM *To:* centos@centos.org; fedora-l...@redhat.com; debian-u...@lists.debian.org; ubuntu-us...@lists.ubuntu.com *Subject:* [CentOS] IPv6 docs, howtos, descriptions I know...google...BUT: Does someone has good howtos, docs, descriptions, opinions in forums, or similar things about IPv6 and related things? I just think it would be a very good idea to collect some links about it... Regards, and thank you in anticipation much info at: http://www.tunnelbroker.net/forums/index.php?PHPSESSID=5ed651d73b5ce537820eeddd11bf0df1board=2.0 http://www.tunnelbroker.net/forums/index.php?PHPSESSID=5ed651d73b5ce537820eeddd11bf0df1board=2.0 If you login with your (free!) account there are a bunch of examples scripts for any OS Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos If you are going to post in another language, please also post in English. It does the mailing list no good for you to post in a language not everyone can read. Vadtec vad...@vadtec.net ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos The translation in English is right underneath the original text, so your complaint is totally off the mark. Not to mention, one could easily make the same complaint towards people who sign their messages with gigantic GPG signature blocks. At least multiple languages give some value to people who know one of the two languages. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos My apologies, I read his response incorrectly this morning. As for GPG, more people need to use it, so you can expect that I will continue to use my signature as it is. Thunderbird knows how to handle GPG signatures, sorry your client doesn't. Vadtec vad...@vadtec.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJKMmuwAAoJEEJXIw5V8gie9cQP/j+5YGUf6qDyvDFZLdDAFCOR 9aVSUvkBSGVT+amIF5SEPYXOsTZeaWWK3vwQvZqJcJfe2dgivRQ1dk/09ZzDB/0x 2Bryo3nKeFyApUJXzPV+Sq/xvGK4DCZlaYGrOcnwsZ2rbi7wPabVdSELb+5LwG1Z n8BlnCBkCwt9GCRWW96fse3DwlES7BJ2CMXMGW/atF6/gDlgfUA57qEJ6CcleuDD jDQVV/dB0IOBu005kq5FdFJcQKzdvi2YNky7qi5dsy2uJ41Q6P9j3HrqVeL2ik5N XxLrjdxnaj/vhOPQ1rFtNK+PsERAHw6LWF5P9wdriKZ+1T0i5j8ohDAn+PTiPA9c wxSGLTwTm3tWkpt2u29Awoa9M7smNeTbvnuPL5xA+W09zqWUqT1Qkm0k4bR4Ad6d UjeT//YxDMSFrWV98UA5EqoW04uL2elifqpI2QOEGr1a2CP8SYMDLmve7jow+gro IXE+SremOXrvB7e8/lJUMPUuEJcJFpnnVaY/NZsnbnPrild6HNQeDFju2+Ieis1z PW8HAZSs1tbR0Q6Atovl495b+sWWxoRK+wMtEbacVxXTXEtaKGk+dAxCPSnieJ7V K/jSCaHje/9LtsyX7hW+kuovNBFVRRvIRNEIU3MHKjMTeYQlc+/fHYRoyj+CUM4m ssDtOg6cg1lvBcMJtsdP =iapv -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPv6 range provisioning question
-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: [dvea...@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 [dvea...@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 vad...@vadtec.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJKMmwQAAoJEEJXIw5V8gieCYYQAOasRlo854C0ikB2J8hkWEJs JHY+azEC7DVbiXcDbot3WrNkQDGx0Pc2iAmoszurQq3hpcCxjPRnI4fKKLs9ZJDo 6cWW2EOVwAI32aVNcFF/wjTcaWc9EfiG6kUyisHU9aHnTUE5wtoWYui9Bt7mphie Cuf+qgVuHJIvwmmZi8I22OJra6qCQVK9q0muEi5+5DL0jJ/Co5OHjTPpLSmL3Gnr HFeKkYhrtpywhr8xa3wC+hkLd18j0M1zItGHNfhY2TeD8dzB14HpAu9lkBueLBVC 1SfwPbNmGLRkC0SEch2hzSGZgNvVlxYNU5Orgp0dfzq0bXq47ET/NpV65CnKQWlJ 8bXN15rixygAIQ+4uyVAYOiQFiqVskNJ030SZm93/hiH1TUv1wS9W4hxOa3HRaEr ZLXjAtHOEYQSyaKgupNQRNNOc3yvUajC18wEeJ3bUidMrVr8acXG9vCyWsJpl/Yu s6HrxUFvE0Jl6eoE6hptUaMD3F3NlI4pdHsF72PY+h/sLTYHHwqHZtpLRzrl10cb LxygqWq1CqhkXTzc9/HDqmRLTWnSwn6phQdmA//MXrgo+PJGfEVwF0Mr4vS8nHlf Mc1MBS0c4Cn6mGpT2xfttM+X8CcgASGJVaadkT+B+ioWdq5TQ/QTyz2qyXbVqA77 ttx5sxpH0VdGEsepB+pp =MpkA -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPv6 range provisioning question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So can anyone offer any insight into this? See my reply at the bottom of the message. Vadtec vad...@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::::/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
Re: [CentOS] IPv6 range provisioning question
-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:: 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-' 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) loLink 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:: 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::' 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) loLink 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 vad...@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
Re: [CentOS] IPv6 range provisioning question
-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 vad...@vadtec.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJKMXREAAoJEEJXIw5V8gieHFIQAJUSVQZmrizk7SbwDgcW/0jt kS1sIAk7KzjaiCYJ26PyGzMTLdES95YjWarQiK8qb7qUZ4THhOb2WiNN5oRpC1/V JQ2SlVTa10R9lFu5XLUzqIpPuR9KieqI40AIcC5oo2rwWYMA+MxsafrNHTo4jxxv 44KffiVvA3cOOI0/ZYk3mQkTeSOlxAUDZF8AEK4elbEbnqMK6Z4w+pxSD+J/BNjH 4IifGeCy3S/CHEDtBfrzerewCkrYxCH1YYgMf7m3glWnnrZeQHKm4c6H10Q4qZBY UrJX5QPhxGA9Gl4yWgi//hDKgQh18zmQpU4kmc2Eyop8Um2lg4vlwqN2/DhhYgG6 1TJcwspanNLG71RN0NJJWioLhQtGZt9hg9jXvfRUPXrNKfVyPiA8AGgAfYrnlhW2 Viv9cGRD0AEP0hARTZ7KCOd2m3tqOrJgBQnLc+DdjEb7wrJJuazrME4lxm+PY182 Sv8MS7toigaJvpQ8Eh9snXHVBWImxy5qc6fL8sOk6cgUQea2Rp+55KEgZBPZes84 hzr0rrC6IeBCCTJNX8bmBGKeYGoMkGRhL5eRWTA7SJaa8HmkAZUj/moD6BvrBmA1 GnWTI+ROEJ2ieb21db/docwhcmwmHnii+HfeXlo5YDLnIaB65wOY4XyiAq+8A7RT xi/5YqXUi7sYdz7h3kFs =+sif -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] IPv6 range provisioning question
-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::::/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 vad...@vadtec.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJKL/amAAoJEEJXIw5V8gieYUIP/jhhEVNej/sheEahmIHvEbPz Wu7SJnjIbiO/4rQzR4cbSvGG5mQjqrbZ6KKWEHp+raf720sIgv5MaQEEnk+rc0+J H85ntg+yx0AW7MDoCe+1chGTpjmsg0/5Em0vHW7u7bv+739Wi9F2aelVHFPJGKiY UVFjMU2vCetlpVjEJqU61uAIUrv2AgjR0FfSe6HiTuw8ZpkW/fRe5TmeIYg/4lFY AlE67x4FiSWUevw1VsFvLBFFfyFRrCLkFPD48RZUUyAZSjOx0TjjYVlqBKAHIl7+ Adc6ussOeaUq0qvbTzJNuvAWqQYo+3JM4fGAefKyMIBZo9xgnp+SwRrSnT6KV68J 7Y46lgMb6ZLW/LBXl3PMLyS5B5B4z49PkVhlk5B8C77pZW6pR7pPx2CXvkLe8TX8 +RY/Y0fna2HREWl3grot1o4pS7tmc8JCijExD9tHb65xVvtlCZd9olNXbQ9OBiN3 gDruSFu2tVve5kQIySzY1rzFH/RRc43w3L0vSyKa6SZV0mIgyjQDmaXzkLSiwwuE M2D+2WctsPg3cWMeaNJKWQj09P5nDQqN6Ux3xBKFMYuO9j/TAUsgLh8rU+G5kz9B bJmCVY3F9KNiYuvhuZsLpB4U16PuRjSI1Kg1ZgtPtYyLN6d78ClwpMyPBZrS53El aUC93I6hd4JYIH2AT14p =1JlU -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] IPv6 range provisioning question
-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::::/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
