Illidan's Castle of Runes

Sec.1 Dynagen Configuration

autostart = False
ghostios = true
 
[localhost]
    port = 7200
    udp = 10000
    workingdir = ../workingdir/
     
    [[router R1]]
        image = ../ios/unzip-c3640-js-mz.124-10.bin
        model = 3640
        console = 3001
        ram = 80
        confreg = 0x2102
        exec_area = 64
        mmap = true
        slot0 = NM-1FE-TX
        f0/0 = R2 f0/0
     
    [[router R2]]
        image = ../ios/unzip-c3640-js-mz.124-10.bin
        model = 3640
        console = 3002
        ram = 80
        confreg = 0x2102
        exec_area = 64
        mmap = true
        slot0 = NM-1FE-TX
        slot1 = NM-4T
        s1/0 = R3 s1/0
     
    [[router R3]]
        image = ../ios/unzip-c3640-js-mz.124-10.bin
        model = 3640
        console = 3003
        ram = 80
        confreg = 0x2102
        exec_area = 64
        mmap = true
        slot1 = NM-4T
        s1/1 = R4 s1/0
     
    [[router R4]]
        image = ../ios/unzip-c3640-js-mz.124-10.bin
        model = 3640
        console = 3004
        ram = 80
        confreg = 0x2102
        exec_area = 64
        mmap = true
        slot0 = NM-1FE-TX
        slot1 = NM-4T
    f0/0 = R5 f0/0
     
    [[router R5]]
        image = ../ios/unzip-c3640-js-mz.124-10.bin
        model = 3640
        console = 3005
        ram = 80
        confreg = 0x2102
        exec_area = 64
        mmap = true
        slot0 = NM-1FE-TX 

Sec.2 Router Configurations

Only commands that need typing in are presented.

hostname R1
ipv6 unicast-routing
interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
 ipv6 address 2000:1:1:1:1:1:1:1112/112
 ipv6 rip 6bone enable
ipv6 router rip 6bone

hostname R2
interface Tunnel0
 no ip address
 ipv6 address 3000::1/112
 ipv6 rip 6bone enable
 tunnel destination 192.34.1.4
 tunnel mode ipv6ip

interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
 ipv6 address 2000:1:1:1:1:1:1:1111/112
 ipv6 rip 6bone enable

!
interface Serial1/0
 ip address 192.23.1.2 255.255.255.0
ipv6 router rip 6bone
router ospf 1
 log-adjacency-changes
 network 192.23.1.0 0.0.0.255 area 0
ipv6 router rip 6bone

Sec.3 Running

R1#sh ipv6 route
IPv6 Routing Table - 6 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
C 2000:1:1:1:1:1:1:0/112 [0/0]
via ::, FastEthernet0/0
L 2000:1:1:1:1:1:1:1112/128 [0/0]
via ::, FastEthernet0/0
R 3000::/112 [120/2]
via FE80::CE01:1AFF:FE72:0, FastEthernet0/0
R 4000:1:1:1:1:1:1:0/112 [120/3]
via FE80::CE01:1AFF:FE72:0, FastEthernet0/0
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0


R1#ping 4000:1:1:1:1:1:1:1112

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4000:1:1:1:1:1:1:1112, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/168/328 ms

6to4 (sometimes written 6 to 4) is a system that allows IPv6 packets to be transmitted over an IPv4 network (generally the IPv4 internet) without the need to configure explicit tunnels. Routing conventions are also in place that allow 6to4 hosts to communicate with hosts on the IPv6 internet. It is typically used when an end site or end user wants to connect to the IPv6 internet using their existing IPv4 connection.

Since IPv6 is not required to be configured or supported on any nearby networking devices relative to the host, 6to4 is especially relevant during the initial phases of deployment to full, native IPv6 connectivity. However, it is intended only as transition mechanism and is not meant to be used permanently.

6to4 may be used by an individual host, or by a local IPv6 network. When used by an individual host, that host must have IPv4 connectivity and a global IPv4 address, and the host is responsible for encapsulation of outgoing IPv6 packets and decapsulation of incoming 6to4 packets. Many host operating systems implement this encapsulation and decapsulation via a 6to4 pseudo-interface.

When 6to4 is used by a local network, the entire local network needs only a single IPv4 address. Within that network, hosts learn their IPv6 addresses and routing using ordinary router discovery protocols, just as on a native IPv6 network.

6to4 does not facilitate interoperation between IPv4-only hosts and IPv6-only hosts.

How 6to4 works

6to4 performs three functions:

1. Assigns a block of IPv6 address space to any host or network that has a global IPv4 address.
2. Encapsulates IPv6 packets inside IPv4 packets for transmission over an IPv4 network.
3. Routes traffic between 6to4 and "native" IPv6 networks.

Address Block Allocation

For any 32-bit global IPv4 address that is assigned to a host, a 48-bit 6to4 IPv6 prefix can be constructed for use by that host (and if applicable the network behind it) by prepending 2002 (hex) to the IPv4 address. Thus for the global IPv4 address 207.142.131.202, the corresponding 6to4 prefix would be 2002:CF8E:83CA::/48. (IPv4 addresses use decimal notation while IPv6 addresses use hexadecimal notation). This gives a total prefix length of 48 bits, the same as an end site is supposed to be allocated under normal IPv6 address alocation leaving room for a 16 bit subnet field and a 64 bit address within the subnet.

Any IPv6 address that begins with the 2002::/16 prefix is known of as a 6to4 address, as opposed to a native IPv6 address which does not use that prefix.

Encapsulation and Transmission

6to4 embeds an IPv6 packet in the payload portion of an IPv4 packet with protocol type 41. To send an IPv6 packet over an IPv4 network to a 6to4 destination address, an IPv4 header with protocol type 41 is prepended to the IPv6 packet. The IPv4 destination address for the prepended packet header is derived from the IPv6 destination address of the inner packet, by extracting the 32 bits immediately following the IPv6 destination address's 2002:: prefix. The IPv4 source address in the prepended packet header is the IPv4 address of the host or router which is sending the packet over IPv4. The resulting IPv4 packet is then routed to its IPv4 destination address just like any other IPv4 packet.

Routing Between 6to4 and Native IPv6

To allow hosts and networks using 6to4 addresses to exchange traffic with hosts using "native" IPv6 addresses, "relay routers" have been established. A relay router connects to an IPv4 network and an IPv6 network. 6to4 packets arriving on an IPv4 interface will have their IPv6 payloads routed to the IPv6 network, while packets arriving on the IPv6 interface with a destination address prefix of 2002::/16 will be encapsulated and forwarded over the IPv4 network.

To allow a 6to4 router to communicate with the native IPv6 Internet, it must have its IPv6 default gateway set to a 6to4 address which contains the IPv4 address of a 6to4 relay router. To avoid the need for users to set this up manually, the 6to4 relay anycast address of 192.88.99.1 (which when wrapped in 6to4 with the subnet and hosts fields zero becomes 2002:c058:6301::) has been allocated for the purpose of sending packets to a relay router. For routing reasons the whole of 192.88.99.0/24 has been allocated for routes pointed at 6to4 relay routers that use the anycast IP. Providers willing to provide 6to4 service to their clients or peers should advertise the anycast prefix like any other IP prefix, and route the prefix to their 6to4 relay.

Packets from the IPv6 Internet to 6to4 systems must be sent to a 6to4 relay router by normal IPv6 routing methods. The specification states that such relay routers must only advertise 2002::/16 and not subdivisions of it to prevent IPv4 routes polluting the routing tables of IPv6 routers. From here they can then be sent over the IPv4 Internet to the destination.


Running Example


This example resembles the scenario in RFC 3056 Section 5.5. In the RFC scenario, there are multiple IPv6 sites, connected to one IP backbone. While in this scenario, there is only one IPv6 site connected to the IP backbone. Site A and Site C are 6to4 sites while Site B is 6to4 relay and Site B pure IPv6.









After running lets see the IPv6 forwarding table in Site A dual-stack gateway (Router A):



The incoming and outing traffic flow on IPv6 layer of Workstation C in 6to4 Site C:



The PING report (ICMPv6) from Workstation A to Workstation C (Site A -> Site C):