Assigning IPV6 in different OS

Hi All,

Now a days the internet user's are growing and the ip addresses are decreasing .so ipv4 is a limited ip addresses to assign .In ipv6 there is no limit to assign ip add and here mac add of the user are included .the header of the IPV6 we can observe in the below figure.

Windows 

Check

First check to see if IPv6 is installed.

• Execute ipv6 if from a DOS windows.
• If it returns the message below, then IPv6 is not installed. If it returns a large amount of interface configuration information, IPv6 is installed and you can proceed to the Configure section.

Could not access IPv6 protocol stack-the stack is not installed.

Install

To install IPv6 on Windows XP SP2, execute the following commands as a administrator from the command line (DOS window):

• ipv6 install

• The output from this command is likely to be 1 of 2 possibilities:’

1. The command returns OK. IPv6 has installed correctly, proceed to the Configure section.
2. The command returns

Installing...
Failed to complete the action.
Error 0x800704b8

This problem relates to a windows internal security database that needs to be integrity checked and possibly repaired. ** If you’re using a corporate machine that is built as part of a Windows Domain, then please check with your IS people before following these procedures, as they may alter or erase Group Policy settings that have been pushed to your machine via a Domain Controller.**

• If you issue esentutl /g c:\windows\security\Database\secedit.sdb, this will check the security database for errors.

Check the output of that command, if it declares…

Checking database integrity.

The database is not up-to-date. This operation may find that this database 

is corruptbecause data from the log files has yet to be placed in the database.

• …then the database has errors which need to be corrected before IPv6 can be installed. The following command will rebuild the Local Security database on the machine.

** THIS IS POTENTIALLY DAMAGING TO YOUR DOMAIN SETTINGS **

• Execute “esentutl /p c:\windows\security\Database\secedit.sdb” as an Administrator user.

• You will likely get a warning box pop up which states…

You should only run Repair on damaged or corrupted databases

• …Hit “OK”
• Once the command has run-trough, re-execute esentutl /g c:\windows\security\Database\secedit.sdb which should result in the following output

Integrity check successful.
Operation completed successfully in some seconds.

• Now, you should be able to execute the ipv6 install command successfully.
• Run ipv6 if to confirm (see above).

Configure

Once IPv6 is Installed and running, it’s time to assign IPv6 Addresses, gateways and routes.

To configure an IPv6 address, determine which of the Interfaces shown by the command ipv6 if matches the name of your main network connection under “START–Control Panel–Network Connection”, it should be called something like “Local Area Connection X” where X is a number.

• As an example, ipv6 if on my machine shows

Interface 5: Ethernet: Local Area Connection
 Guid {3E4601A7-041B-4D5A-ACD3-B6D840BBEF39}
zones: link 5 site 2
uses Neighbor Discovery
uses Router Discovery
link-layer address: 00-16-cb-97-4a-4e
  preferred global 2404:138:4000:1::203, life infinite (manual)
  preferred link-local fe80::216:cbff:fe97:4a4e, life infinite
  multicast interface-local ff01::1, 1 refs, not reportable
  multicast link-local ff02::1, 1 refs, not reportable
  multicast link-local ff02::1:ff97:4a4e, 1 refs, last reporter
  multicast link-local ff02::1:ff00:203, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 20000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
default site prefix length 48

• To assign 2404:138:4000:1::203 to Local Area Connection 5, execute ipv6 adu 5/2404:138:4000:1::203
• To define the default gateway for that interface, execute ipv6 rtu ::/0 5/2404:138:4000:1::2. This defines the default route (::/0) on interface 5 as being 2404:138:4000:1::2.

• To check IPv6 routes execute netsh, then interface ipv6 and then show route.

It should show something like

Publish  Type     Met  Prefix                  Idx  Gateway/Interface Name
-------  -------- ----  ---------------------  ---  ---------------------
no       Manual     0     ::/0                   5  2404:138:4000:1::2

• To get out of netsh, type bye

Finalise

Once you have configured IPv6 Gateway and routes, test you can ping:

1. Your local loopback. Try ping6 ::1. This should return replies that look similar to a normal IPv4 ping response
2. Your v6 Gateway. Try ping6 <IPv6 gateway address>. Again, we’re looking for a normal ping response.

If you are having problems pinging gateways, then it may be with the Teredo Tunneling adapter that XP & Vista installs by default. This can be disabled using the netsh command

• At a DOS prompt, execute netsh
• Execute interface and then execute ipv6
• Execute set teredo disable
• Execute bye to exit from netsh

• Finally, ensure you have a DNS server configured that can return Ipv6 or AAAA (Quad A) records.

Mac OS X

Configuring a static (manual) IPv6 address under Mac OS X (version 10.5.3 ) should be an easy case of bringing up the Network Preferences window, choosing your preferred interface, clicking on ‘Advanced’ and then choosing the TCIP/IP pane. From this pane, there is an ability to have IPv6 off, automatically configure or manually configure.

We haven’t tried automatic configuration yet [June 2008] as we don’t have an IPv6 DHCP server setup at the office. However, we do support IPv6 – as does KAREN of course – and have an allocation of IPv6 addresses.

Unfortunately, we discovered what appears to be a bug in using the GUI to manually set a static IPv6 address configuration in OS X. Whilst you can fill out the fields in the GUI pan and they are remembered, the underlying network configuration does not appear to change.

A manual workaround has been successful.

• Ignore the GUI – at least for setting a static address
• From the terminal, setup your IPv6 details:
  • sudo ifconfig en0 inet6 2404:138:4000:x::xx/64
  • sudo route add -inet6 -prefixlen 0 default 2404:138:4000:x::x
  • (replace en0 with the relevant network interface you want to IPv6 enable and xx with the relevant address numbering for your machine and the default gateway)
• From the terminal, check the details have been applied
  • ifconfig en0 | grep inet6

inet6 fe80::21f:5bff:fe84:5a2f%en0 prefixlen 64 scopeid 0x4
inet6 2404:138:4000:x::xx prefixlen 64

(note the fe80: address is the internal IPv6 address assigned by the OS. It is similar to a 10.x or 192.168.x address under IPv4)

• • netstat -r -f inet6

Internet6:
Destination        Gateway            Flags      Netif Expire
::                 2404:138:4000:x::x UGSc        en0
default            2404:138:4000:x::x UGSc        en0

• You can then test ping the IPv6 net
  • website: ping6 www.aarnet.ed.au [2001:388:1:4001:20a:e4ff:fe0d:be04]
  • Or one of the Internet2 test hosts listed at http://ipv6.internet2.edu/ipv6hosts.shtml
  • Or http://ipv6.beijing2008.cn/en/

Note: As this method does not use the GUI, you may find that as you switch back to other networks using the same interface you will have to reset or manually remove your default gateway.

Linux/Unix

The following instructions were developed using Ubuntu Server 7.10, and is very simple. You need to edit /etc/network/interfaces with an appropriate editor such as vi. The catch is that the following lines need to be added before the IPv4 configuration.

iface eth(n) inet6 static
    address 2404:138:xxxx:xxxx::xxxx (static address of your host)
    netmask 64
    gateway 2404:138:xxxx:xxxx::xxxx (static address of the default router)

Once this has been saved restart the interface and use ping6 <address> to test connectivity to a remote subnet.

Automatic IPv6 address configuration – DHCP v6

Unfortunately, neither Mac OS X, Windows XP, nor most default linux installs come with a DHCPv6 client ). This means that any DNS, default routes and search paths have to be set manually.

This reflects the non-finalised protocols / standards around DHCPv6.

The Internet2 gurus says that one of the challenges is support for IPv6 ‘helpers’ (for example http://www.blackviper.com/WinXP/Services/IPv6_Helper_Service.htm).

Some community DHCP IPv6 links follow:

• Dibbler – Dibbler is a portable DHCPv6 implementation. It supports stateful ( IPv6 address granting) as well as stateless (option granting) autoconfiguration for IPv6. Supports IPv6 and WinXP.
• dhcpv6 project – DHCPv6 is a stateful address autoconfiguration protocol for IPv6, a counterpart to IPv6 stateless address autoconfiguration protocol.
• ISC DHCP suite – version 4 onwards supports DHCPv6

 

Source: http://wiki.karen.net.nz/index.php/Main_Page