EUChinaGRID IPv6 Tutorial Cataniav2 1

IPv6 Tutorial
Catania
06/06/2007
Gabriella Paolini
gabriella.paolini@garr.it
GARR
1 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

Why do we need IPv6 ? (1/2)
¾ A bigger address space
• From 32 bits to 128 bits:
– A true global connectivity
– No more hidden networks or hosts
– All the hosts can be reachable (From Client-only to “Server”!)
– Security systems End-to-end
¾ Auto configuration
• Opportunity to use 64 bits for host (uniqueness guarantee)
• "plug and play"
• Opportunity to manage Multihoming in an easy way
• Renumbering in an easy way

Why do we need IPv6 ? (2/2)
¾ IP Header efficient and extensible:
• Less fields in the basic header
– Routing efficiency
– Performance
– Header extendibility
– Better options management
¾ No more packet fragmentation during routers
transit
¾ Real implementation of:
• Security
• Mobility
• Multicast
– Replace broadcast
• More efficient use of the network

IPv4 Header (1/3)
• 20 bytes without options field
4Bytes Ver IHL TOS. Total length

4Bytes Identification Flag Fragment offset
4Bytes TTL Protocol Checksum
4Bytes 32 bits Source Address

4Bytes 32 bits Destination Address
IP Options Padding
In yellow fields that are no more included in IPv6

IPv4 Header (2/3)
¾ Version. 4 bit.
• IP header format
• 4 - IP, Internet Protocol.
¾ IHL, Internet Header Length. 4 bit.
• Packet Header length in 32 bits groups. Minimum value is 5.
¾ TOS, Type of Service. 8 bit.
• Type of Service required. To define the packet management
during its transport.
¾ Total length. 16 bit.
• Total packet length.
¾ Identification. 16 bit.
• To identify packet fragment during fragmentation.
¾ Flags. 3 bit.
• To control packet fragmentation
¾ Fragment Offset. 13 bit.
• To order fragmented packet rebuilding.

IPv4 Header (3/3)
¾ TTL, Time to Live. 8 bit.
• To track packet Time to live.
¾ Protocol. 8 bit.
• Next protocol used in the higher level.
¾ Header checksum. 16 bit.
• IP header Checksum, options included .
¾ Source IP address. 32 bit.
• Source IP address.
¾ Destination IP address. 32 bit.
• Destination IP address.
¾ Options. Variable length.
¾ Padding. Variable length.
• Useful to create a 32 bit compliant packet header.

IPv6 Header (1/3)
• 40 byte without other header extensions
Ver Traffic Class Flow Label

Payload Length Next Header Hop Limit
128 bits Source Address

128 bits Destination Address
In yellow fields that are already present in IPv4

IPv6 Header (2/3)
¾ Version. 4 bit.
• 6 - IPv6.
¾ Traffic Class. 8 bit.
• To identify packets priority (IPv4 TOS)
¾ Flow Label. 20 bit.
• To identify flow. Mobile IPv6.
¾ Payload Length. 16 bit.
• Data Length in the packet
• Max size 64 KB. For packets bigger than 64K, use Jumbo
Payload option.

IPv6 Header (3/3)
¾ Next Header. 8 bit.
• Next header value. If it’s a higher level protocol, value is the
same that in IPv4.
• To identify extension header.
¾ Hop Limit. 8 bit.
• Replace the IPv4 TTL.
¾ Source address. 16 byte.
• Source IPv6 address.
¾ Destination address. 16 byte.
• Destination IPv6 address.

Extension Headers (1/6)
¾ A new method for implementing options
¾ After the IPv6 header
IPv6 Header
Next Header TCP Header Data
= TCP
IPv6 Header Routing Header

Next Header Next Header TCP Header Data
= Routing = TCP
IPv6 Header Routing Header ESP Header

Next Header Next Header Next Header TCP Header Data
= Routing = ESP = TCP

¾ 00 = Hop-by-Hop Options
¾ 43 = Routing
¾ 44 = Fragment
¾ 51 = Authentication
¾ 60 = Destination Options
¾ 50 = Encapsulating Security Payload
¾ xx = Higher level protocols, like in IPv4
¾ 58 = Internet Control Message Protocol (ICMPv6)
¾ 59 = No next header

¾ Hop-by-hop options (00)
• All the information will be managed by each node during
packet path.
• Some options:
– Router Alert
– Jumbo Payload
¾ Routing (43)
• Like IPv4 option Loose Source Route
• It specifies a list of routers to jump
• mobile IPv6 & multihoming
– Header valued only by routers in the list

¾ Fragment (44)
• Used only by host (not by Routers!!)
• Minimum MTU of 1280 byte (68 byte in IPv4)
– Link without this capacity have to manage fragmentation at data-link level
¾ Destination Options (60)
• Used to transport optional information (managed only by
destination host)
• In the Daisy Chain:
– Before Routing Header
– Or at the end of Daisy Chain
• Used for Mobile IPv6
– With the Routing header

Security is embedded in IPv6:
IPsec native on IPv6
¾ Authentication Header (51)

• To manage authentication: verifying source address and
integrity of the packet during the path
¾ Encapsulating Security Payload (50)
• Only the destination host will be grant to open the packet
• Like IPv4 there is two model: transport or tunnel

Extension Headers (6/6) IPv6
Hop by hop }
Destination }
¾ An example: Routing }
Fragmentation }
Authentication }
Security }
Destination }
Upper Layer

Addresses
¾ IPv4 = 32 bits
¾ IPv6 = 128 bits
• 4 times the numbers of bits!
• ~3,4 * 1038 of usable hosts (theoretical max)
• 1030 addresses for each person in the world

IPv6 Address Format (1/2)
¾ X:X:X:X:X:X:X:X
• where X is a field of 16 bits in hexadecimal notation
• Es: 2001:0000:1234:0000:0000:00D0:ABCD:0532
¾ Value is independent by upper o lower case notation
• Es: 2001:0000:1234:0000:0000:00D0:abcd:0532
¾ Zero on the left side of each field are optional
• Es: 2001:0:1234:0:0:D0:ABCD:532

IPv6 Address Format (2/2)
¾ More close fields only with zero are represented by
a :: (double colon symbol) but only once in an
address.
• Es:2001:0:1234::D0:ABCD:532
¾ This notation is not valid:
• 2001::1234::C1C0:ABCD:876
¾ This notation is valid:
• 2001:760:2:0:0:0:0:0 => 2001:760:2::
• FF02:0:0:0:0:0:0:1 => FF02::1
• 0:0:0:0:0:0:0:1 => ::1
• 0:0:0:0:0:0:0:0 => ::

IPv6 address in a URL
¾ In an URL IPv6 addresses have to be represented
between square brackets.
• http://[2001:1:4F3A::206:AE14]:8888/index.html
¾ Software that uses URL (browser, etc.) has been

modified to be IPv6 compliant, but:
• uncomfortable for the users
• Used only for diagnostic
• More useful with a domain name.

Type of Addresses
¾IPv6 divides addresses in:
• Unicast: node addresses
• Multicast: group of nodes addresses
• Anycast: services addresses

IPv6 addresses architecture (1/2)
To calculate on the first 16 bit

es. 2000-3FFF --> 0010 0000 0000 0000 – 0011 1111 1111 1111

IPv6 addresses architecture (2/2)

Unicast Addresses
¾ Unspecified
¾ Loopback
¾ IPv4 Compatible
¾ IPv4 Mapped
¾ Scoped Addresses :
• Link-local
• Site-local
¾ Aggregatable Global Addresses

Unspecified
¾ 0:0:0:0:0:0:0:0 or simply ::
¾ It’s used to specify the absence of an address
¾ It can be used in the initial request for DHCP to
obtain an address
¾ Duplicate Address Detection (DAD)
¾ Like 0.0.0.0 in IPv4
¾ ::/0 is the default route

Loopback
¾ 0:0:0:0:0:0:0:1 or simply ::1
¾ To identify node itself
¾ Like 127.0.0.1 in IPv4 (localhost)
¾ To test if IPv6 stack is working :
• ping6 ::1

IPv4 compatible
¾ Used to insert IPv4 addresses in IPv6 addresses
¾ The first 96 bits are equal to zero, the other 32 bits
specify the IPv4 address
• 0:0:0:0:0:0:192.168.0.1
• ::192.168.0.1
• ::C0A8:1E01
¾ Used for IPv4-IPv6 transition

IPv4 mapped
¾ They permit to define IPv6 addresses for nodes that
support only IPv4
¾ The first 80 bits are equal to zero, the next 16 bits
are equal to 1 (FFFF) and, the last 32 bits specify
the IPv4 address
• 0:0:0:0:0:FFFF:192.168.0.1
• ::FFFF:192.168.0.1
• ::FFFF:C0A8:1E01
¾ Used for IPv4-IPv6 transition

Subnet Prefix and Host Identifier
¾ IPv6 unicast addresses are divided in two parts:
• Subnet Prefix (first 64 bits)
• Host Identifier (last 64 bits)
XXXX:XXXX:XXXX:XXXX XXXX:XXXX:XXXX:XXXX
Subnet Prefix (64 bit) Host Identifier (64 bit)
¾ The host can be identified :

• Manually.
• Using the Interface ID (mac address): the mac address (or
EUI 48/64) is ricalculated and used as host identifier in the
IPv6 address.

EUI-64 format
¾ The Interface ID :
• Identifies univocally an interface
• Has to be univocal on a link
• Can be obtained starting from EUI-64 identifier.
¾ EUI-64 identifier is based on the same base of MAC
address (It’s an evolution)
• It identifies the manufacturer and the serial number of an
input/output interface using 64bits
¾ There is a procedure to move from EUI-48 ID (mac-
address) to EUI-64 ID

Interface ID from mac-address
¾ From MAC address (EUI-48 ID) insert the sequence
“FF-FE” after the first 24 bits.
MAC Address: 00-AA-00-3F-2A-1C
EUI-64 Address: 00-AA-00-FF-FE-3F-2A-1C
U/L complementation: 02-AA-00-FF-FE-3F-2A-1C
In IPV6 notation: 02AA:00FF:FE3F:2A1C
24 bit 24 bit
cccccc00 cccccccc cccccccc xxxxxxxx xxxxxxxx xxxxxxxx IEEE 802 Address
cccccc00 cccccccc cccccccc 11111111 11111110 xxxxxxxx xxxxxxxx xxxxxxxx EUI-64 Address
0xFF 0xFE
cccccc1c cccccccc cccccccc 11111111 11111110 xxxxxxxx xxxxxxxx xxxxxxxx Interface ID

Link and Site
¾ For link we mean a unique physical network like a
LAN or a point-to-point connection. Nodes on the
same link are named neighbor.
¾ A site is a group of link managed by a unique

authority (ex. A University campus)

Link-local (1/2)
¾ It’s a Scoped address (new with IPv6)
¾ Scope = local link (i.e. LAN, VLAN)

• It can be used only between nodes in the same link
• No routing
¾ Automatically configured for each interface

• good to start communication.
• Using the interface identifier
¾ Format:
• FE80:0:0:0:<interface identifier>
10 bit 54 bit 64 bit

1111111010 0 interface ID

Link-local (2/2)

Site-local (1/3)
¾ It’s a Scoped address
¾ Scope = site (a network of links)

• It can be used only between nodes in the same site
• Non to be used out of the site (es. Internet)
• Similar to the IPv4 private addresses
¾ Not configured by default

Site-local (2/3)
¾ Used for an address plan in a whole site
¾ Examples :
• Numbering for a site before to be connected to the Internet.
• Privet addressing (ex. Local printers)
¾ Format:
• FEC0:0:0:<subnet id>:<interface id>
• Subnet id = 16 bits = 64K subnets
10 bit 38 bit 16 bit 64 bit

1111111011 0 subnet ID interface ID

Site-local (2/3)

Aggregatable Global IPv6
Addresses
/23 Regional Registries
/32 Local Internet Registries
/48 Site IANA 2000::/3
/64 Link
/23 /23
/23
RIPE
ARIN RIR NCC
RIR APNIC RIR
/32
GARR
TLA Registry
/48 /48 Sub-TLA Registry
NLA Registry
CASPUR Roma Tre
SLA Registry
/64 /64 /64 /64 /64 /64
End-User (LAN)

Multicast (1/3)
¾ Multicast = one to many
¾ No broadcast in IPv6. Multicast is used instead of

broadcast, above all in the local links.
¾ Scoped addresses: it substitutes TTL in IPv4

Multicast (2/3)
¾ Format:
• FF<flags><scope>::<group id>
• Identify by FP 11111111 (=FF)
• Flag = 0 permanent / 1 temporary
• Scope: node (1), link (2), site (5), organization (8), global
(E)
• Group ID: It identifies a multicast group in a specific scope.
8 4 4 112
1111-1111 Flag Scope Group ID

Multicast (3/3)
¾ For example:
• Considering the Group ID All-Nodes (1) :
• The address FF01::1 affects all the interfaces on the same

node
link
site
• The address FF0E::1 affects all the interfaces in Internet

Multicast addresses
¾ Some reserved multicast addresses :
ADDRESS SCOPE Type

FF01::1 Node All Nodes
FF02 ::1 Link All Nodes
FF01::2 Node All Routers
FF02 ::2 Link All Routers
FF05 ::2 Site All Routers
FF02 ::1: FFXX :XXXX Link Solicited-Node

Anycast
¾ One-to-any
¾ The Anycast addresses are not distinguishable from
unicast addresses
¾ They are unicast addresses assigned to a group of
interfaces (usually in different nodes)
¾ They help to find the server closer to the source.
¾ Some anycast addresses are reserved for specific

use:
• Router subnet
• Mobile IPv6 home-agent discovery

Addresses for each host
¾ Each IPv6 host has to recognize as its own this
addresses:
• One link-local address for each interface
• Assigned unicast/anycast addresses (manually or
automatically)
• Loopback address
• All-Nodes group multicast address
• Solicited-node multicast addresses for each assigned
unicast/anycast address
• All the other multicast addresses for each group it joins

How to select an address
¾ One node can use different network connections
• It’s possible to have more IPv6 addresses assigned on the
same interface (more than one global address)
¾ For each flow node has to select source and
destination address.
¾ The choice is done following this rules :
• To use the right scope following the destination (global, site,
local)
• To use the address more similar to the destination (IPv4,
IPv6)
¾ The algorithm of choice can be overwritten by the
stack or the application.

DNS
¾ The use of IPv6 is not changing basic mechanism of
Domain Name System
¾ This new record are introduced to manage IPv6
addresses:
• A new resource record to associate IPv6 address to a name
• A new domain for reverse resolution of IPv6 addresses.

A name for an IPv6 address
¾ AAAA record
• To define mapping between a domain name and an IPv6
address
• Like A record in IPv4
• Supported in Bind from 4.9.5 version.

An IPv6 address for a name
¾ PTR record
• To define mapping between an IPv6 address and a domain
name
• The same record used in IPv4
• A new Top Level domain used for IPv6:
– from ip6.int
– to ip6.arpa
• Divided by 4 bits. In IPv4 classful division. Easier to
delegate.

BIND configuration
¾ AAAA record
¾ $ORIGIN 6net.garr.it
¾ www IN AAAA 3ffe:b00:c18:1:290:27ff:fe17:fc1d
¾ PTR record (ip6.arpa)

¾ $ORIGIN 1.0.0.0.8.1.c.0.0.0.b.0.e.f.f.3.ip6.arpa
¾ d.1.c.f.7.1.e.f.f.f.7.2.0.9.2.0 IN PTR www.6net.garr.it

ICMPv6 protocol
¾ It is the IPv6 version of ICMP with the same basic
features
• Error discovery, control, debugging
¾ Add new functionalities
• Neighbor discovery
– Neighbor Solicitation, Unreachability, Autoconfiguration
• Multicast group management
¾ It has the same functionalities of ICMP, ARP, e
IGMP protocols for IPv4.

ICMPv6: Message type
¾ Two class of messaged:
• From type 0 to 127 Error Messages
• From type 128 to 255 Informational Messages
¾ The most common error messages are:
– Destination Unreachable (1)
– Packet Too Big (2)
– Time Exceeded (3)
– Parameter Problem (4)

Path MTU Discovery (1/2)
¾ IPv6 fragmentation management is end-to-end
• Routers don’t fragmented packets
• The fragmentation process is managed by host
¾ The host use Path MTU Discovery to know the
maximum MTU available on the link.
• Based on ICMPv6 “Packet too big” messages
– A router creates a packet too big message when the MTU
used is too large for the path
– Specifies the new MTU in the data field.

Path MTU Discovery (1/2)
¾ How MTU path discovery works:
• The host sends the first packet with the same dimension as
MTU of its link
• If a “Packet Too Big” is reached the host sends another
message with the new MTU
• The host repeats the process until no error is found
¾ The host sends packets periodically, to check if the
path has changed
¾ Minimum MTU for IPv6 is 1280 byte

Neighbor Discovery
¾ Uses ICMPv6
¾ Manages the control information within a link
• Address resolution
– Neighbor Solicitation and Neighbor Advertisement
– Neighbor Unreachability Detection
• Autoconfiguration
– Router Solicitation e Router Advertisement
• Redirect
¾ Messages cannot be sent outside the link
• Valid messages have Hop Limit = 255

Stateless Autoconfiguration
¾ Allows the IPv6 hosts to connect to the network without manual
configuration
¾ No need to use DHCP
• Uses specific multicast group
¾ Addresses are based on Interface ID
¾ On the link, hosts can communicate among them using link-
local addresses
¾ Unlike DHCP, the DNS must be configured manually

Stateful Configuration
¾ Addresses and other network parameters (ex. DNS)
can be configured manually:
• Entirely manual configuration
• DHCPv6

Configuration Basics
Linux

Configuration Basics – Linux (1/3)
¾ IPv6 support is available since Linux kernel release
2.4.
¾ The current support does not implement all RFC
features
¾ A patch (USAGI patch) is available to provide all

extensions to the kernel.
¾ Further information:
¾ USAGI Project http://www.linux-ipv6.org/

¾ If the IPv6 support is available on our kernel, the file
• /proc/net/if_inet6
¾ must be present. If not, we can try to load the IPv6

kernel module,
• # modprobe ipv6
¾ and then test it again.

¾ If the module is not available we must rebuild our
kernel.

¾ Resources:
¾ Kernel documentation
¾ Linux Kernel HOWTO

(http://www.linuxdoc.org/HOWTO/Kernel-
HOWTO.html).

Interface Configuration – Linux
(1/2)
¾ The configuration syntax for IPv6 is similar to IPv4.In the
following examples, we will use ifconfig.
¾ Add an IPv6 address to an interface
# /sbin/ifconfig <interface> inet6 add

<ipv6address>/<prefixlength>
# /sbin/ifconfig eth0 inet6 add 2001:760:ffff::126/64
¾ Delete an IPv6 address from an interface
# /sbin/ifconfig <interface> inet6 del <ipv6address>/<prefixlength>

# /sbin/ifconfig eth0 inet6 del 2001:760:ffff::126/64

Interface Configuration –
Linux(2/2)
Show the interface configuration
#ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:10:B5:DA:59:B8
inet addr:193.206.158.126 Bcast:193.206.158.255
Mask:255.255.255.0
inet6 addr: 2001:760:ffff::126/64 Scope:Global
inet6 addr: fe80::210:b5ff:feda:59b8/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6262494 errors:0 dropped:0 overruns:0 frame:0
TX packets:7971062 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Global unicast address
Interrupt:5 Base address:0xc000
Link local address
MAC ADDRESS EUI-64 format

Routing table – Linux (1/2)
As for IPv4 we can operate on the routing table.
We will use for these functions the route command.
•Show the routing table

#route --inet6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::1/128 :: U 0 0 0 lo
2001:760:ffff::126/128 :: U 0 0 0 lo
2001:760:ffff::/64 :: UA 256 0 0 eth0 ;route for the global address
fe80::210:b5ff:feda:59b8/128 :: U 0 0 0 lo
fe80::250:56ff:fec0:1/128 :: U 0 0 0 lo
fe80::250:56ff:fec0:8/128 :: U 0 0 0 lo
fe80::/10 :: UA 256 0 0 eth0 ;route for the link-local
ff00::/8 :: UA 256 0 0 eth0 ;generic route for multicast
::/0 :: UDA 256 0 0 eth0 ; automatic default route

Routing table – Linux (2/2)
Add or delete an entry on the routing table
#route --inet6 add|del <ipv6network>/<prefix> gw <ipv6addr> [dev <device>]

#route --inet6 add|del <ipv6network>/<prefix> [dev <device>]
#route --inet6 add default gw 2001:760:ffff::11
#route --inet6
Kernel IPv6 routing table

Destination Next Hop Flags Metric Ref Use Iface
………
::/0 2001:760:ffff::11 UG 1 0 0 eth0 ;default route

::/0 :: UDA 256 0 0 eth0 ; automatic default route

Host Configuration – Fedora Core
Linux
Edit the file /etc/sysconfig/network-scripts/ifcfg-<interfacename>
(ifcfg-eth0 for the first ethernet interface)
Add the following lines
IPV6INIT=yes
IPV6ADDR=<ipv6address/prefixlen>
Adding the following configuration to /etc/sysconfig/network

NETWORKING_IPV6=yes
IPV6_DEFAULTGW=<ipv6gatewayaddress>
Restart the network

#service network restart

Host Configuration – Generic Linux
The following configuration should be used if the IPv6 scripts are
not available on the operating system
Add the following lines to /etc/rc.local (it could be /etc/rc.d/rc.local
on many distributions)
IPV6_ADDRESS=<ipv6address/prefixlen>
IPV6_GW=<ipv6gatewayaddress>
/sbin/ifconfig eth0 inet6 add $IPV6_ADDRESS
/sbin/route --inet6 add default gw $IPV6_GW

Configuration Basics
Microsoft Windows

Configuration Basics – Microsoft
Windows (1/2)
¾ IPv6 for Windows is currently available for:
• Windows Vista
• Windows 2003
• Windows XP
• Windows 2000 with a special kit provided by Microsoft
http://msdn.microsoft.com/downloads/sdks/platform/tpipv6.asp
¾ References:
http://www.microsoft.com/ipv6

Windows (2/2)
¾ Windows IPv6 implementation supports:
• Autoconfiguration
• Tunnel
• Teredo
¾ Windows software is IPv6 ready:

• Internet Explorer.
• Ping, traceroute e telnet.
• Firewall

Windows 2000
¾ On Windows 2000 you need to install Service Pack-1,2 o 3.
The installation kit must be modified as follow:
¾ Download the IPv6 kit from URL

http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/dow
nload.asp
¾ Extract the archive content to a temporary folder (e.g.
C:\>ipv6kit);
¾ From this folder, execute setup.exe -x,
¾ A folder called files will be created;
¾ Edit the file Hotfix.inf and modify the key
NTServicePackVersion:
• For SP2 “NTServicePackVersion=512”
• For SP3 “NTServicePackVersion=768”
¾ Run Hotfix.exe and restart the computer.

Running IPv6 – Microsoft Windows 2000
/XP
We can activate or deactivate the IPv6 stack using the
command net
net stop tcpip6
Disable the IPv6 support and remove the related kernel module
The net command cannot deactivate IPv6 if an IPv6 socket is in
use.
net start tcpip6
Load the IPv6 kernel module (tcpip6.sys) and activate the IPv6
support.

(1/3)
The ipv6 command manage the windows IPv6 stack.
The following command show the interfaces configuration:
C:>ipv6 if 4
Interface 4 (site 1):

uses Neighbor Discovery
link-level address: 00-50-56-a3-00-01
preferred address 2001:760::196, infinite/infinite
preferred address fe80::250:56ff:fea3:1, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ffa3:1, 1 refs, last reporter
multicast address ff02::1:ff00:0, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 36000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1

(2/3)
The ipv6.exe command is also used to:
•Add and delete IPv6 addresses on the network interfaces.

•View and modify the some protocol attributes
(router advertisement, forward options etc.)
•Add or delete an interface
•Show and manage the routing table

(3/3)
C:\>ipv6
usage: ipv6 if [ifindex]
ipv6 ifc ifindex [forwards] [-forwards] [advertises] [-advertises] [mtu #
bytes] [site site-identifer]
ipv6 ifd ifindex
ipv6 adu ifindex/address [lifetime validlifetime[/preflifetime]] [anycast
] [unicast]
ipv6 nc [ifindex [address]]
ipv6 ncf [ifindex [address]]
ipv6 rc [ifindex address]
ipv6 rcf [ifindex [address]]
ipv6 bc
ipv6 rt
ipv6 rtu prefix ifindex[/address] [lifetime L] [preference P] [publish] [
age] [spl SitePrefixLength]
ipv6 spt
ipv6 spu prefix ifindex [lifetime L]

Running IPv6 – Microsoft Windows XP
(1/3)
In Windows XP the use of the netsh utility instead of ipv6.exe is
suggested
A complete reference to migrate ipv6.exe command to netsh is
available at the URL:
http://www.microsoft.com/technet/itsolutions/network/ipv6/ipv62netshtable.mspx
To install the IPv6 support type the following command in a
command window
netsh interface ipv6 install

(2/3)
Show the interface table
C:>netsh interface ipv6 show interface
Idx Met MTU State Name
--- ---- ----- ------------ -----
6 0 1500 Disconnected Wireless Network Connection
5 0 1500 Connected Local Area Connection
4 2 1280 Disconnected Teredo Tunneling Pseudo-Interface
3 1 1280 Connected 6to4 Pseudo-Interface
2 1 1280 Connected Automatic Tunneling Pseudo-Interface
1 0 1500 Connected Loopback Pseudo-Interface
Add the IPv6 address to the Local Area Connection Interface

C:>netsh interface ipv6 add address interface=5 address=<ipv6address/prefixlen>
Add the default gateway route through the same interface

C:>netsh interface ipv6 add route ::/0 5 <ipv6gatewayaddress>

(3/3)
Check the routing table
C:>netsh interface ipv6 show route

Querying active state...
Publish Type Met Prefix Idx Gateway/Interface Name

------- ----- ---- ------------------ --- ---------------------
no Manual 0 ::/0 5 2001:760::11

Running IPv6 – Microsoft Windows
Vista (1/3)
¾IPv6 is enabled by default !!!
• Includes GUI configuration
¾New features:
• Complete IPsec support
• MLD v2
• IPv6 over PPP
• DHCPv6
• Teredo with symmetric NAT support
• Can’t be uninstalled
• Can be disabled for a given interface

Vista (2/3)
¾

Running IPv6 – Microsoft
Windows Vista (3/3)

The ping6 command is used to check the IPv6 connectivity
C:>ping6 www.kame.net
Pinging www.kame.net [2001:200:0:8002:203:47ff:fea5:3085]

from 2001:760::73 with 32 bytes of data:
Reply from 2001:200:0:8002:203:47ff:fea5:3085: bytes=32 time=310ms

Ping statistics for 2001:200:0:8002:203:47ff:fea5:3085:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 310ms, Maximum = 310ms, Average = 310msnetsh interface ipv6 add address
interface=5 address=<ipv6address/prefixlen>

IPv4-IPv6 transition

A General Transition Roadmap
(1/2)
Step 1
¾ Network Design
• Define Wide and Local network segments
• Define “special” areas (due to requirements and operations) -
VLANs, DMZs etc.
• Define management entities and their areas of responsibility
• Network management information flow
• Security requirements:
• For users and applications
– For the network itself (protection of the management information,
protection of network devices, security of management procedures)
• Plan the steps to transition to the new protocol. Examine the
possibility of deploying transition mechanisms (for communications
between IPv6 areas within an IPv4 network and vise-versa)

A General Transition Roadmap
(2/2)
Step 2
¾ Implementation of a mixed IPv4/IPv6 environment
¾ Gradual transition of non-critical systems to IPv6
• Allows the evaluation of the operation and stability of the network
devices and non-critical systems under IPv6
• Develops the transition procedures
• Disseminates the usages of transition mechanisms (tunnels,
gateways, etc.) for communications between exclusive IPv6 areas
Step 3
¾ Transition of all systems to IPv6
¾ Exclusive usage of IPv6 in the network
• Maintaining transition mechanisms for legacy systems and contacts
with IPv4 networks

Transition mechanisms
¾ Three categories:
• Implemented on the host
– Dual Stack Host
– BIS, BIA, ...
• Implemented on the network layer
– Tunnel
> Manuals,
> ISATAP, Teredo, ...
– Dual Stack Network
• Based on protocol translators
– SIIT and NAT-PT

Dual Stack Host (1/2) Applicazione
TCP,UDP
IPv4 IPv6
¾ It’s easy 0x0800 0x86DD
¾ A dual stack node : Ethernet
• Implements both the protocols

• Has IPv4 and IPv6 addresses on the same interface
¾ The IPv4-only applications use IPv4
¾ For the application that support IPv6:
• DNS resolves both IPv4 and Ipv6 addresses
• If destination has an IPv6 address, the host uses IPv6
• If destination has only an IPv4 address, the host uses IPv4

Dual Stack Host (2/2)
¾ Advantages:
• Easy
• No particular support
¾ Limitations:
• No reduces the need of IPv4 addresses
• Needs a dual stack network
• Doesn’t integrate the IPv6 network with IPv4
– The two networks are completely separate
– It’s a compatibility mechanism more than a transition one
¾ At present almost all of the IPv6 nodes are dual
stack host.

IPv6-in-IPv4 Tunnel (1/3)
¾ Tunnels are usually used to Ver
IPv4 Header
IHL TOS Length
transport a protocol through a Identification
TTL Protocol
F Fragment Offset
Hdr checksum
network based on another Source Address
Destination Address
protocol Ver Class

Length
Flow Label
Next Hdr Hop Limit
¾ IPv6-in-IPv4 tunnels permits Source Address
to use IPv6 without a native

IPv6 infrastructure Destination Address
¾ IPv6 packets are Data
encapsulated in IPv4 packets IPv6 Packet

adding an IPv4 Header
¾ The Protocol field in the IPv4
¾I
header is 41

IPv6-in-IPv4 Tunnel (2/3) Link IPv4
Router IPv4
Link IPv6
Router IPv6
Tunnel IPv6 su IPv4
Router dual stack
Example of IPv6-in-IPv4 tunnel
¾ On the tunnel Ingress interface IPv6 packets are encapsulated

in IPv4 packets
¾ The obtained IPv4 packets are routed over the IPv4 networks
as all the other IPv4 packets
¾ At the tunnel egress interface packets are decapsulated
¾ The IPv6 packets are elaborated as they are arrived from a
native IPv6 network.

IPv6-in-IPv4 Tunnel (3/3)
¾ The end points have to be dual stack nodes
¾ In the path, tunnel is only an IPv6 hop
¾ From IPv6 point of view, the IPv4 network is
something like a layer 2 technology
¾ Tunnet MTU is - 20 byte for the IPv4 header
¾ Tunnels can be :
– Router to router
– Host to router
– Host to host
¾ Very useful for first experiences with IPv6 and in the
first phase of transition

Tunnel Broker (1/2)
Router
Client IPv6
IPv4
Broker
¾ Web service in IPv4

¾ It helps the host to create dynamically a tunnel with a preconfigured
end point.
¾ A user asks for a tunnel using a web page
¾ The tunnel broker identifies the user
¾ The tunnel broker configures a router as tunnel end-point and sends
parameters to the user
¾ For “occasional” users

Tunnel Broker (2/2)
¾ http://www.go6.net/4105/freenet.asp
¾ http://www.coredumps.org/
¾ http://www.ngnet.it/i/privati.php (solo per gli utenti

Telecom Italia)
¾ http://www.fast-labs.net/tb/ (solo per gli utenti

Fastweb)

Automatic Tunneling Mechanisms
¾ ISATAP
• “Intra-Site Automatic Tunnel Addressing Protocol”
• To connect nodes and routers IPv6 over an IPv4 only
infrastructure
¾ Teredo
• “Tunneling IPv6 over UDP Through NATs”
• Encapsulated IPv6 packets in UDP IPv4 packets instead of
tunnel IPv4 packets
• To permit to use tunnel also behind IPv4 NAT

Teredo (1/2)
¾ Useful for hosts behind NAT
¾ Encapsulates the IPv6 packets within UDP v4 packets to
bypass the problem of NAT in many cases restricting protocol
41 (IP encapsulated) packets
¾ The encapsulation takes place at the communicating node
itself rather than at a border router (like it happens in 6to4)
¾ The Teredo-relay then forwards the packets to the native IPv6
network
¾ Issues:
• Complex implementation
• Can operate only with specific NAT types
• Limited number of Teredo-relays available in the Internet
¾ Used only if there is no other available solution…

Teredo (2/2)
Teredo tunnel: IPv6 in UDPv4
Private IPv4 Public IPv4 IPv6

NAT
Server
Client 1
2
Public IPv4
4 3
Private IPv4 5 6
Public IPv6
NAT Relay

Teredo address format
32 bits 32 bits 16 bits 16 bits 32 bits
Teredo
IPv4 @ Flags Port Client IPv4
prefix
¾ Teredo IPv6 prefix

¾ IPv4 address: global address of the server
¾ Flags: Cone or Symmetric NAT
¾ Port: port number to be used with the IPv4 address
¾ The “client IPv4 field” contains the global address of the NAT

Teredo limitations
¾ Vulnerability to DoS attacks on relay,
¾ The entity that operates the Teredo relay has little
means in order to control who is using the service
¾ Some NATs are not supported
¾ Teredo relays are not deployed!
• Lack of implementation in routers
• Teredo prefix is not advertised in the IPv6 Internet

Protocol Translators
¾ It’s a method to permit communication between IPv4-only
nodes with IPv6-only nodes
¾ An alternative to Dual Stack nodes
• Dual Stack needs an IPv4 address for each node
¾ Where ?
• All the traffic (IPv4-to-IPv6 and vice versa) runs on the translator
node
• Limitations :
– Robustness
– Security
– Accountability
– Traffic

NAT-PT
¾ Like NAT in IPv4
• The translator node has a pool of IPv4 addresses that can be assigned to
the nodes that ask for it
• The translator maintains IPv4-IPv6 connections table
• IPv4 address is represent by IPv6 address adding the 32 bits IPv4
address to a 96 bits prefix
• IPv6 mapping → dynamic IPv4, IPv4 → deterministic IPv6
¾ Needs a translation mechanism for DNS queries (DNS ALG)
¾ In a static configuration, it can be used from IPv4 to IPv6.

NAT-PT : an example (1/4)
NAT-PT
IPv6
IPv4
A www.garr.it
2001:760:4:f005::2 193.206.158.2
DNS
¾ A is an IPv6-only node that want to be connected to the web

server www.garr.it, that is using IPv4 only

NAT-PT
IPv6
IPv4
A www.garr.it
2001:760:4:f005::2 193.206.158.2
DNS
¾ A ask for a DNS query for the IPv6 address www.garr.it

¾ DNS ALG of the NAT-PT resolves the query in the following
way:
• It does the DNS query for the IPv4 address : 193.206.158.2
• It sends to A an IPv6 address : ::f00f:c1ce:9e02

2001:760:4:f005::2 ::f00f:c1ce:9e02 193.204.161.12 193.206.158.2
NAT-PT
IPv6
IPv4
A www.garr.it
2001:760:4:f005::2 193.206.158.2
DNS
¾ A sends a packet to ::f00f:c1ce:9e02

¾ NAT-PT elaborates the request
• Associated to A an dynamic IPv4 address from the pool:
2001:760:4:f005::2 ↔ 193.204.161.12
• Maintain the association information in a table
• Sends packets over the IPv4 network to 193.206.158.2 using as
source address 193.204.161.12

NAT-PT : an example
c1ce:9e02
(4/4)
193.206.158.2
2001:760:4:f005::2 ::f00f: 193.204.161.12
NAT-PT
IPv6
IPv4
A www.garr.it
2001:760:4:f005::2 193.206.158.2
DNS
¾ Reply packets to A are routed to NAT-PT and translated in

IPv6 to be sent to A
¾ A received the IPv6 packets with the source address
::f00f:c1cd:8be5

NAT-PT: limitations and
advantages
¾ Advantages:
• Transparent to the nodes
¾ Limitations:
• The same problems of IPv4 NAT
– Fragility
– Need of DNS ALG
– No direct connectivity

IPv4-IPv6 transition
Configuration

How to configure a tunnel (Linux)
(1/4)
IPv4 Network
192.168.1.10 192.168.10.2
IPv6 in IP
2001:760:ffff::10/127 2001:760:ffff::11/127

(2/4)
¾ To configure use the iptunnel command that permits
to create, to delete and to modify a tunnel ip-over-ip,
gre, sit.
¾ iptunnel {add|change|del|show} NAME mode

{ipip|gre|sit} remote <endpointaddr> local
<localaddr> [ ttl TTL ] [ tos TOS ] [ nopmtudisc ] [ dev
PHYS_DEV ]

(3/4)
¾ Tunnel configuration and creation of the tunnel interface;
#iptunnel add sit1 remote 192.168.10.2 local 192.168.1.10 mode sit ttl 64
¾ IPv6 address configuration on the tunnel interface
#ifconfig sit1 inet6 add 2001:760:ffff::10/127
¾ Tunnel interface activation
#ifconfig sit1 up
¾ Creation of a static route to the tunnel interface
#route --inet6 add default gw 2001:760:ffff::11
¾ With this route, traffic is routed by default to the tunnel.

(4/4)
#route --inet6
.....
::/0 2001:760:fff::11 UG 1 0 0 sit1
#iptunnel show
sit1: ipv6/ip remote 192.168.10.2 local any ttl 64

How to configure a tunnel
(Windows)
192.168.1.10 192.168.10.2
IPv6 in IP
2001:760:ffff::10 2001:760:ffff::11
c>ipv6 rtu ::0 2/::192.168.10.2 pub interface tunnel0

c>ipv6 adu 2/2001:760:ffff::10 ipv6 address 2001:760:ffff::11
tunnel source 192.168.10.2
tunnel destination 192.168.1.10
tunnel mode ipv6ip

IPv6 enabled applications
¾ http://6net.iif.hu/ipv6_apps
¾ http://www.deepspace6.net/docs/ipv6_status_page_apps.html
(Linux only)
¾Sendmail, Qmail, Postfix, Thunderbird,

Bind, VLC, SSH, Apache, Mozilla,
Firefox , Internet Explorer, Irc, Xchat…

References
¾ http://www.ipv6ready.org/
¾ http://www.ipv6tf.org/
¾ http://www.go6.net/
¾ http://www.deepspace6.net/
¾ http://www.6diss.org/
¾ http://www.sixxs.net/

EUChinaGRID IPv6 Tutorial Cataniav2 1

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

EUChinaGRID IPv6 Tutorial Cataniav2 1

Загружено:

Авторское право:

Доступные форматы

IPv6 Tutorial

 1 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 2 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 3 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

4Bytes Ver IHL TOS. Total length

4Bytes 32 bits Source Address

In yellow fields that are no more included in IPv6

 4 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 5 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 6 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

Ver Traffic Class Flow Label

128 bits Source Address

In yellow fields that are already present in IPv4

 7 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 8 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 9 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

IPv6 Header Routing Header

IPv6 Header Routing Header ESP Header

 10 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 11 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 12 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 13 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

¾ Authentication Header (51)

 14 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 15 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 16 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 17 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 18 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

¾ Software that uses URL (browser, etc.) has been

 19 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

• Unicast: node addresses

• Multicast: group of nodes addresses

• Anycast: services addresses

 20 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

To calculate on the first 16 bit

 21 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 22 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 23 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 24 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 25 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 26 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 27 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

¾ The host can be identified :

 28 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 29 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

cccccc00 cccccccc cccccccc xxxxxxxx xxxxxxxx xxxxxxxx IEEE 802 Address

cccccc1c cccccccc cccccccc 11111111 11111110 xxxxxxxx xxxxxxxx xxxxxxxx Interface ID

 30 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

¾ A site is a group of link managed by a unique

 31 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

¾ Scope = local link (i.e. LAN, VLAN)

¾ Automatically configured for each interface

10 bit 54 bit 64 bit

 32 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 33 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

¾ Scope = site (a network of links)

¾ Not configured by default

 34 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

10 bit 38 bit 16 bit 64 bit

 35 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 36 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

 37 Gabriella Paolini - GARR  IPv6 Tutorial  Catania, 06/06/2007

¾ No broadcast in IPv6. Multicast is used instead of

1 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

2 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

3 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

4 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

5 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

6 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

7 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

8 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

9 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

10 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

11 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

12 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

13 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

14 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

15 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

16 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

17 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

18 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

19 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

20 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

21 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

22 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

23 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

24 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

25 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

26 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

27 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

28 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

29 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

30 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

31 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

32 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

33 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

34 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

35 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

36 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

37 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

38 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

39 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

40 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

41 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

42 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

43 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

44 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

45 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

46 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

47 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

48 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

49 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

50 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

51 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

52 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

53 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

54 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

55 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

56 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

57 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

58 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

59 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

60 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

61 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

We will use for these functions the route command.

62 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

63 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

Adding the following configuration to /etc/sysconfig/network

Restart the network

64 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

65 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

66 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

67 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

68 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

69 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

70 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

71 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

72 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

73 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007

74 Gabriella Paolini - GARR IPv6 Tutorial Catania, 06/06/2007