<![CDATA[IPv6 Forum - All Forums]]> http://www.ipv6forum.forums.vedovanetwork.com/ Fri, 02 Jan 2009 08:06:09 +0100 MyBB <![CDATA[Hi!]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-10.html Sun, 01 Nov 2009 18:18:18 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-10.html
feel free to post your feelings in here...

regards,]]>
feel free to post your feelings in here...

regards,]]> <![CDATA[New server!]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-9.html Sun, 01 Nov 2009 18:16:15 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-9.html
irc6.ca.flexnet.org]]>
irc6.ca.flexnet.org]]> <![CDATA[Current ipv6 capable servers]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-8.html Sun, 01 Nov 2009 17:53:41 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-8.html
* irc.ipv6.homelien.no - 2001:840:0:0:0:0:0:1000 (open to all)

* irc.efnet.nl - 2001:7B8:3:3F:201:2FF:FEF6:574E (restricted to 2001::/16)

* efnet.ipv6.xs4all.nl - 2001:888:0:2:0:0:0:2 (open to all)

These two servers are working closely together on an automated web-based I-line request form. As soon as it has been finished, requests for I-lines will be accepted again.]]>
* irc.ipv6.homelien.no - 2001:840:0:0:0:0:0:1000 (open to all)

* irc.efnet.nl - 2001:7B8:3:3F:201:2FF:FEF6:574E (restricted to 2001::/16)

* efnet.ipv6.xs4all.nl - 2001:888:0:2:0:0:0:2 (open to all)

These two servers are working closely together on an automated web-based I-line request form. As soon as it has been finished, requests for I-lines will be accepted again.]]> <![CDATA[The ARP process in IPv6]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-7.html Sun, 01 Nov 2009 17:27:58 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-7.html Discovery.

With IPv4, ARP has an ethernet protocol ID of 0x0806 and IPv4 has a protocol ID
of 0x0800. With IPv6 both the Neighbor Discovery function and regular IPv6
packets have the same protocol ID - 0x86dd. There is then no way to tell
without looking at the higher layers if the traffic is Neighbor Discovery
traffic or regular IPv6 unicast/multicast/anycast traffic.

So, now that we know Neighbor Discovery replaces ARP, lets go through a simple
example showing how it works and the addresses involved.

Here is the topology we will use for the example:

PC1---eth---switch---eth---PC2

The network here is all ethernet, but it could be any Layer 2 medium that
transports ethernet (1483 bridged, LANE, PWE3 etc).

So, assuming no communication has already taken place, we will start a ping
from PC1 to PC2.

PC1 = 2000::1/64
PC2 = 2000::2/64

What happens first is PC1 needs to discover the MAC address of PC2 because the
medium is Ethernet.

PC1 sends out a Neighbor Solicitation packet that looks like this:

----Ethernet Packet----
Source MAC = 00:00:00:00:00:01
Destination MAC = 33:33:FF:00:00:02
Ethernet Protocol ID = 0x86DD

----IPv6 Packet----
IPv6 Next Header = 58 (ICMPv6)
Source IPv6 address = 2000::1
Destination IPv6 address = FF02::1:FF00:2

----ICMPv6 Packet----
Type = 135 (Neighbor Solicitation)
Target Address = 2000::2
Link Layer Address = 00:00:00:00:00:01

Ok, so a few things to explain here. First, where is the destination MAC
address coming from? Well, the 33:33:ff section is reserved for the Neighbor
Discovery process and the 00:00:02 section is an extrapolation of the IPv6 address
(low order 24 bits of the IPv6 address).

Next, where is the destination IPv6 address coming from? This is a special
address which denotes all hosts on the network (FF02::1 - same L2 segment) and
again an extrapolation of the destination IPv6 address (00:2). For example, you
could ping6 FF02::1 and all hosts on that LAN would respond.

Next is the actual ICMPv6 packet and its' contents. The target address is
obvious - it's the destination IPv6 address you're trying to reach. The Link
Layer Address is the local source MAC address.

So, now that we have all the information needed to originate the Neighbor
Discovery process, we will look at the Neighbor Advertisement reply.

Once PC2 receives the Neighbor Solicitation and recognizes his IPv6 address he
must reply with a Neighbor Advertisement packet. This is what it looks like:

----Ethernet Packet----
Source MAC = 00:00:00:00:00:02
Destination MAC = 00:00:00:00:00:01
Ethernet Protocol ID = 0x86DD

----IPv6 Packet----
IPv6 Next Header = 58 (ICMPv6)
Source IPv6 Address = 2000::2
Destination IPv6 Address = 2000::1

----ICMPv6 Packet----
Type = 136 (Neighbor Advertisement)
Sent in *response* to Neighbor Solicitation bit = 1 (true)
Target Address = 2000::2
Link Layer Address = 00:00:00:00:00:02

Here you can see the Unicast Source and Destination MAC address again with the
Protocol ID of 0x86DD. The rest of the information is self explanitory.

The third and fourth packets of the process are the Ping request and Ping reply.

Ping request:

----Ethernet Packet----
Source MAC = 00:00:00:00:00:01
Destination MAC = 00:00:00:00:00:02
Ethernet Protocol ID = 0x86DD

----IPv6 Packet----
IPv6 Next Header = 58 (ICMPv6)
IPv6 Source Address = 2000::1
IPv6 Destination Address = 2000::2

----ICMPv6 Packet----
Type = 128 (Echo Request)

Ping reply:

----Ethernet Packet----
Source MAC = 00:00:00:00:00:02
Destination MAC = 00:00:00:00:01
Ethernet Protocol ID = 0x86DD

----IPv6 Packet----
IPv6 Next Header = 58 (ICMPv6)
IPv6 Source Address = 2000::2
IPv6 Destination Address = 2000::1

----ICMPv6 Packet----
Type = 129 (Echo Reply)

And thats it! The fields I've outlined are the main ones, but there are a
couple others. In a normal default situation, the above fields should be the
only relevant ones.

The last thing we should cover is what a valid Neighbor Cache looks like.
Depending on the OS, the command to display the cache might look different.

Basically, after a successfull Neighbor discovery process, you should have
something like this:

C:\IPv6Kit>ipv6 nc
3: 2000::1 00-00-00-00-00-01 reachable (30000ms) (router)

This example shows Index 3 having IPv6 address 2000::1 using MAC address
00:00:00:00:00:01, is reachable (valid) and has a refresh time of 30 seconds.
2000::1 also happens to be acting as a router in this case (the router bit is
set in the Neighbor Discovery process).]]> Discovery.

With IPv4, ARP has an ethernet protocol ID of 0x0806 and IPv4 has a protocol ID
of 0x0800. With IPv6 both the Neighbor Discovery function and regular IPv6
packets have the same protocol ID - 0x86dd. There is then no way to tell
without looking at the higher layers if the traffic is Neighbor Discovery
traffic or regular IPv6 unicast/multicast/anycast traffic.

So, now that we know Neighbor Discovery replaces ARP, lets go through a simple
example showing how it works and the addresses involved.

Here is the topology we will use for the example:

PC1---eth---switch---eth---PC2

The network here is all ethernet, but it could be any Layer 2 medium that
transports ethernet (1483 bridged, LANE, PWE3 etc).

So, assuming no communication has already taken place, we will start a ping
from PC1 to PC2.

PC1 = 2000::1/64
PC2 = 2000::2/64

What happens first is PC1 needs to discover the MAC address of PC2 because the
medium is Ethernet.

PC1 sends out a Neighbor Solicitation packet that looks like this:

----Ethernet Packet----
Source MAC = 00:00:00:00:00:01
Destination MAC = 33:33:FF:00:00:02
Ethernet Protocol ID = 0x86DD

----IPv6 Packet----
IPv6 Next Header = 58 (ICMPv6)
Source IPv6 address = 2000::1
Destination IPv6 address = FF02::1:FF00:2

----ICMPv6 Packet----
Type = 135 (Neighbor Solicitation)
Target Address = 2000::2
Link Layer Address = 00:00:00:00:00:01

Ok, so a few things to explain here. First, where is the destination MAC
address coming from? Well, the 33:33:ff section is reserved for the Neighbor
Discovery process and the 00:00:02 section is an extrapolation of the IPv6 address
(low order 24 bits of the IPv6 address).

Next, where is the destination IPv6 address coming from? This is a special
address which denotes all hosts on the network (FF02::1 - same L2 segment) and
again an extrapolation of the destination IPv6 address (00:2). For example, you
could ping6 FF02::1 and all hosts on that LAN would respond.

Next is the actual ICMPv6 packet and its' contents. The target address is
obvious - it's the destination IPv6 address you're trying to reach. The Link
Layer Address is the local source MAC address.

So, now that we have all the information needed to originate the Neighbor
Discovery process, we will look at the Neighbor Advertisement reply.

Once PC2 receives the Neighbor Solicitation and recognizes his IPv6 address he
must reply with a Neighbor Advertisement packet. This is what it looks like:

----Ethernet Packet----
Source MAC = 00:00:00:00:00:02
Destination MAC = 00:00:00:00:00:01
Ethernet Protocol ID = 0x86DD

----IPv6 Packet----
IPv6 Next Header = 58 (ICMPv6)
Source IPv6 Address = 2000::2
Destination IPv6 Address = 2000::1

----ICMPv6 Packet----
Type = 136 (Neighbor Advertisement)
Sent in *response* to Neighbor Solicitation bit = 1 (true)
Target Address = 2000::2
Link Layer Address = 00:00:00:00:00:02

Here you can see the Unicast Source and Destination MAC address again with the
Protocol ID of 0x86DD. The rest of the information is self explanitory.

The third and fourth packets of the process are the Ping request and Ping reply.

Ping request:

----Ethernet Packet----
Source MAC = 00:00:00:00:00:01
Destination MAC = 00:00:00:00:00:02
Ethernet Protocol ID = 0x86DD

----IPv6 Packet----
IPv6 Next Header = 58 (ICMPv6)
IPv6 Source Address = 2000::1
IPv6 Destination Address = 2000::2

----ICMPv6 Packet----
Type = 128 (Echo Request)

Ping reply:

----Ethernet Packet----
Source MAC = 00:00:00:00:00:02
Destination MAC = 00:00:00:00:01
Ethernet Protocol ID = 0x86DD

----IPv6 Packet----
IPv6 Next Header = 58 (ICMPv6)
IPv6 Source Address = 2000::2
IPv6 Destination Address = 2000::1

----ICMPv6 Packet----
Type = 129 (Echo Reply)

And thats it! The fields I've outlined are the main ones, but there are a
couple others. In a normal default situation, the above fields should be the
only relevant ones.

The last thing we should cover is what a valid Neighbor Cache looks like.
Depending on the OS, the command to display the cache might look different.

Basically, after a successfull Neighbor discovery process, you should have
something like this:

C:\IPv6Kit>ipv6 nc
3: 2000::1 00-00-00-00-00-01 reachable (30000ms) (router)

This example shows Index 3 having IPv6 address 2000::1 using MAC address
00:00:00:00:00:01, is reachable (valid) and has a refresh time of 30 seconds.
2000::1 also happens to be acting as a router in this case (the router bit is
set in the Neighbor Discovery process).]]> <![CDATA[Setting up IPv6 forwarding on Windows 2000]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-6.html Sun, 01 Nov 2009 17:12:28 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-6.html
This explains how to set up IPv6 forwarding (and default routing) on a Windows 2000 box with a Windows XP client which only has a NAT IPv4 address. I couldn't find this on the 'net anywhere, so I decided to write it up myself. Hopefully it helps someone else out there.

Versions:
Windows 2000, SP4, MS IPv6 Kit
Windows XP, SP1

Topology:

IPv6Internet---[v6]TunnelbrokerRouter[v4tov6]---IPv4Internet---[v4tov6]Win2k[v6]---eth---[v6]WinXP

The Windows 2000 box acts as a NAT router for IPv4 packets. It has a 192.168.0.1 IPv4 address on the "eth" network. The WindowsXP box has a 192.168.0.100 IP address on the "eth" network with a default gateway of 192.168.0.1. All of the IPv4 NAT stuff works and I can access the IPv4 Internet through the Windows 2000 box via NAT just fine.

Now, the problem was I wanted to be able to access the WindowsXP box from anywhere on the IPv6 Internet without worrying about port forwarding on the Windows 2000 box, and I wanted to see the dancing Kame just for kicks Smile

So, I received a /64 allocation from the Tunnelbroker. They gave me the address:

2001:470:1f00:367::/64

This is what I will be using on the inside of my network (the eth network).

Previously, I had received a /127 IPv6 address from the Tunnelbroker. This establishes the 6to4 connectivity. The address I received was:

2001:470:1f00:ffff::217/127

Their side was:

2001:470:1f00:ffff::216/127

Via 6to4 I could easily ping6 from my Windows 2000 box to the Tunnelbroker IPv6 address. Doing a packet capture, I could see IPv4 packets going out with IPv6 inside of them.

C:\WINNT>ping6 2001:470:1f00:ffff::216

Pinging 2001:470:1f00:ffff::216 with 32 bytes of data:

Reply from 2001:470:1f00:ffff::216: bytes=32 time=86ms
Reply from 2001:470:1f00:ffff::216: bytes=32 time=84ms
Reply from 2001:470:1f00:ffff::216: bytes=32 time=88ms
Reply from 2001:470:1f00:ffff::216: bytes=32 time=85ms

Now, the tricky part was making it so I could configure one of the /64 addresses which was allocated to me on my WinXP box as well as my Win2k box "eth" interface and forward using the Win2k box.

First I assigned the IPv6 address to the WinXP box like this:

ipv6 adu 4/2001:470:1f00:367::2 (the "4" is my Ethernet Nic in the WinXp box on the same network as the Win2k box)

Then I assigned the IPv6 address to the Win2k box like this:

ipv6 adu 5/2001:470:1f00:367::1 (the "5" is the Ethernet nic on the eth network which is the same network the WinXP box is on)

I still wasn't able to ping which was weird. I had to enter a route table entry before I could ping.

So, on the Win2k box, I entered:

ipv6 rtu 2001:470:1f00:367::/64 5

Strangely, I didn't need this entry on the WinXP box. I still don't know the answer for that..but atleast it pings now.

Then, on the WinXP box, I needed to add a default route so I could reach addresses that weren't local to my subnet (basically, the whole IPv6 internet).

ipv6 rtu ::/0 4

Which looks like this when you type "ipv6 rt":

::/0 -> 4/2001:470:1f00:367::1 pref 0 life infinite (manual)

This basically says, if you don't know where to go, use Interface 4, address 2001:470:1f00:367::1 as your gateway.

Lastly, I just needed to turn on IPv6 forwarding on the correct interfaces. This was tricky because I didn't know which interface needed IPv6 forwarding. There are multiple interfaces such as a 6to4 interface, a Pseudo Tunnel interface, as well as the actual ethernet interfaces.

By trial and error, I was able to get the correct configuration. I enabled forwarding on the 6to4 Interface assigned with my IPv4 Internet interface as well as the Ethernet interface (called Home) which is on the eth network.

ipv6 ifc 6 forward
ipv6 ifc 5 forward

This allows packets to be forwarded from the eth network to the IPv6 Internet and back to the eth network again.

Whats cool is that I can now reach my WinXP host which sits on a private IPv4 network (192.168.0.x) directly through the IPv6 internet (2001:470:1f00:367::2) without doing any port forwarding or anything special in general!

Now, I truely have end-to-end connectivity.
Cool!

Here are the snapshots of both boxes IPv6 interfaces and the route tables.

Win2k box:

C:\WINNT>ipv6 if
Interface 6 (site 1): 6-over-4 Virtual Interface
uses Neighbor Discovery
forwards packets
link-level address: 24.154.21.2
preferred address fe80::189a:e7e3, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff9a:e7e3, 1 refs, last reporter
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 28500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 5 (site 1): Home
uses Neighbor Discovery
forwards packets
link-level address: 00-0c-6e-3d-61-ee
preferred address 2001:470:1f00:367::1, infinite/infinite
preferred address fe80::20c:6eff:fe3d:61ee, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff3d:61ee, 1 refs, last reporter
multicast address ff02::1:ff00:1, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 33000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 4 (site 1): Internet
uses Neighbor Discovery
link-level address: 00-26-54-0e-42-86
preferred address fe80::226:54ff:fe0e:4286, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff0e:4286, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 29000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 3 (site 1): 6-over-4 Virtual Interface
uses Neighbor Discovery
link-level address: 192.168.0.1
preferred address fe80::c0a8:1, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ffa8:1, 1 refs, last reporter
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 31000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 2 (site 0): Tunnel Pseudo-Interface
does not use Neighbor Discovery
link-level address: 0.0.0.0
preferred address 2001:470:1f00:ffff::217, infinite/infinite
preferred address ::24.154.231.227, infinite/infinite
preferred address ::192.168.0.1, infinite/infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0
Interface 1 (site 0): Loopback Pseudo-Interface
does not use Neighbor Discovery
link-level address:
preferred address ::1, infinite/infinite
link MTU 1500 (true link MTU 1500)
current hop limit 1
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0

C:\WINNT>ipv6 rt
2001:470:1f00:367::/64 -> 5 pref 0 (lifetime infinite)
::/0 -> 2/::64.71.128.82 pref 0 (lifetime infinite, publish, no aging)

WinXP:

C:\Documents and Settings\Administrator>ipv6 if
Interface 4: Ethernet: Wireless Network Connection
{83601622-4843-4852-B8F9-9543C6288725}
uses Neighbor Discovery
uses Router Discovery
link-layer address: 00-90-96-38-ad-c6
preferred global 2001:470:1f00:367::2, life infinite (manual)
preferred link-local fe80::290:96ff:fe38:adc6, 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:ff38:adc6, 1 refs, last reporter
multicast link-local ff02::1:ff00:2, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 43000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 3: 6to4 Tunneling Pseudo-Interface
{A995346E-9F3E-2EDB-47D1-9CC7BA01CD73}
does not use Neighbor Discovery
does not use Router Discovery
routing preference 1
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 32500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 0
Interface 2: Automatic Tunneling Pseudo-Interface
{48FCE3FC-EC30-E50E-F1A7-71172AEEE3AE}
does not use Neighbor Discovery
does not use Router Discovery
routing preference 1
EUI-64 embedded IPv4 address: 0.0.0.0
router link-layer address: 0.0.0.0
preferred link-local fe80::5efe:192.168.0.236, life infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 27500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 0
Interface 1: Loopback Pseudo-Interface
{6BD113CC-5EC2-7638-B953-0B889DA72014}
does not use Neighbor Discovery
does not use Router Discovery
link-layer address:
preferred link-local ::1, life infinite
preferred link-local fe80::1, life infinite
link MTU 1500 (true link MTU 4294967295)
current hop limit 128
reachable time 29000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 0

C:\Documents and Settings\Administrator>ipv6 rt
::/0 -> 4/2001:470:1f00:367::1 pref 0 life infinite (manual)]]>
This explains how to set up IPv6 forwarding (and default routing) on a Windows 2000 box with a Windows XP client which only has a NAT IPv4 address. I couldn't find this on the 'net anywhere, so I decided to write it up myself. Hopefully it helps someone else out there.

Versions:
Windows 2000, SP4, MS IPv6 Kit
Windows XP, SP1

Topology:

IPv6Internet---[v6]TunnelbrokerRouter[v4tov6]---IPv4Internet---[v4tov6]Win2k[v6]---eth---[v6]WinXP

The Windows 2000 box acts as a NAT router for IPv4 packets. It has a 192.168.0.1 IPv4 address on the "eth" network. The WindowsXP box has a 192.168.0.100 IP address on the "eth" network with a default gateway of 192.168.0.1. All of the IPv4 NAT stuff works and I can access the IPv4 Internet through the Windows 2000 box via NAT just fine.

Now, the problem was I wanted to be able to access the WindowsXP box from anywhere on the IPv6 Internet without worrying about port forwarding on the Windows 2000 box, and I wanted to see the dancing Kame just for kicks Smile

So, I received a /64 allocation from the Tunnelbroker. They gave me the address:

2001:470:1f00:367::/64

This is what I will be using on the inside of my network (the eth network).

Previously, I had received a /127 IPv6 address from the Tunnelbroker. This establishes the 6to4 connectivity. The address I received was:

2001:470:1f00:ffff::217/127

Their side was:

2001:470:1f00:ffff::216/127

Via 6to4 I could easily ping6 from my Windows 2000 box to the Tunnelbroker IPv6 address. Doing a packet capture, I could see IPv4 packets going out with IPv6 inside of them.

C:\WINNT>ping6 2001:470:1f00:ffff::216

Pinging 2001:470:1f00:ffff::216 with 32 bytes of data:

Reply from 2001:470:1f00:ffff::216: bytes=32 time=86ms
Reply from 2001:470:1f00:ffff::216: bytes=32 time=84ms
Reply from 2001:470:1f00:ffff::216: bytes=32 time=88ms
Reply from 2001:470:1f00:ffff::216: bytes=32 time=85ms

Now, the tricky part was making it so I could configure one of the /64 addresses which was allocated to me on my WinXP box as well as my Win2k box "eth" interface and forward using the Win2k box.

First I assigned the IPv6 address to the WinXP box like this:

ipv6 adu 4/2001:470:1f00:367::2 (the "4" is my Ethernet Nic in the WinXp box on the same network as the Win2k box)

Then I assigned the IPv6 address to the Win2k box like this:

ipv6 adu 5/2001:470:1f00:367::1 (the "5" is the Ethernet nic on the eth network which is the same network the WinXP box is on)

I still wasn't able to ping which was weird. I had to enter a route table entry before I could ping.

So, on the Win2k box, I entered:

ipv6 rtu 2001:470:1f00:367::/64 5

Strangely, I didn't need this entry on the WinXP box. I still don't know the answer for that..but atleast it pings now.

Then, on the WinXP box, I needed to add a default route so I could reach addresses that weren't local to my subnet (basically, the whole IPv6 internet).

ipv6 rtu ::/0 4

Which looks like this when you type "ipv6 rt":

::/0 -> 4/2001:470:1f00:367::1 pref 0 life infinite (manual)

This basically says, if you don't know where to go, use Interface 4, address 2001:470:1f00:367::1 as your gateway.

Lastly, I just needed to turn on IPv6 forwarding on the correct interfaces. This was tricky because I didn't know which interface needed IPv6 forwarding. There are multiple interfaces such as a 6to4 interface, a Pseudo Tunnel interface, as well as the actual ethernet interfaces.

By trial and error, I was able to get the correct configuration. I enabled forwarding on the 6to4 Interface assigned with my IPv4 Internet interface as well as the Ethernet interface (called Home) which is on the eth network.

ipv6 ifc 6 forward
ipv6 ifc 5 forward

This allows packets to be forwarded from the eth network to the IPv6 Internet and back to the eth network again.

Whats cool is that I can now reach my WinXP host which sits on a private IPv4 network (192.168.0.x) directly through the IPv6 internet (2001:470:1f00:367::2) without doing any port forwarding or anything special in general!

Now, I truely have end-to-end connectivity.
Cool!

Here are the snapshots of both boxes IPv6 interfaces and the route tables.

Win2k box:

C:\WINNT>ipv6 if
Interface 6 (site 1): 6-over-4 Virtual Interface
uses Neighbor Discovery
forwards packets
link-level address: 24.154.21.2
preferred address fe80::189a:e7e3, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff9a:e7e3, 1 refs, last reporter
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 28500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 5 (site 1): Home
uses Neighbor Discovery
forwards packets
link-level address: 00-0c-6e-3d-61-ee
preferred address 2001:470:1f00:367::1, infinite/infinite
preferred address fe80::20c:6eff:fe3d:61ee, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff3d:61ee, 1 refs, last reporter
multicast address ff02::1:ff00:1, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 33000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 4 (site 1): Internet
uses Neighbor Discovery
link-level address: 00-26-54-0e-42-86
preferred address fe80::226:54ff:fe0e:4286, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ff0e:4286, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 29000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 3 (site 1): 6-over-4 Virtual Interface
uses Neighbor Discovery
link-level address: 192.168.0.1
preferred address fe80::c0a8:1, infinite/infinite
multicast address ff02::1, 1 refs, not reportable
multicast address ff02::1:ffa8:1, 1 refs, last reporter
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 31000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 2 (site 0): Tunnel Pseudo-Interface
does not use Neighbor Discovery
link-level address: 0.0.0.0
preferred address 2001:470:1f00:ffff::217, infinite/infinite
preferred address ::24.154.231.227, infinite/infinite
preferred address ::192.168.0.1, infinite/infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0
Interface 1 (site 0): Loopback Pseudo-Interface
does not use Neighbor Discovery
link-level address:
preferred address ::1, infinite/infinite
link MTU 1500 (true link MTU 1500)
current hop limit 1
reachable time 0ms (base 0ms)
retransmission interval 0ms
DAD transmits 0

C:\WINNT>ipv6 rt
2001:470:1f00:367::/64 -> 5 pref 0 (lifetime infinite)
::/0 -> 2/::64.71.128.82 pref 0 (lifetime infinite, publish, no aging)

WinXP:

C:\Documents and Settings\Administrator>ipv6 if
Interface 4: Ethernet: Wireless Network Connection
{83601622-4843-4852-B8F9-9543C6288725}
uses Neighbor Discovery
uses Router Discovery
link-layer address: 00-90-96-38-ad-c6
preferred global 2001:470:1f00:367::2, life infinite (manual)
preferred link-local fe80::290:96ff:fe38:adc6, 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:ff38:adc6, 1 refs, last reporter
multicast link-local ff02::1:ff00:2, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 43000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
Interface 3: 6to4 Tunneling Pseudo-Interface
{A995346E-9F3E-2EDB-47D1-9CC7BA01CD73}
does not use Neighbor Discovery
does not use Router Discovery
routing preference 1
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 32500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 0
Interface 2: Automatic Tunneling Pseudo-Interface
{48FCE3FC-EC30-E50E-F1A7-71172AEEE3AE}
does not use Neighbor Discovery
does not use Router Discovery
routing preference 1
EUI-64 embedded IPv4 address: 0.0.0.0
router link-layer address: 0.0.0.0
preferred link-local fe80::5efe:192.168.0.236, life infinite
link MTU 1280 (true link MTU 65515)
current hop limit 128
reachable time 27500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 0
Interface 1: Loopback Pseudo-Interface
{6BD113CC-5EC2-7638-B953-0B889DA72014}
does not use Neighbor Discovery
does not use Router Discovery
link-layer address:
preferred link-local ::1, life infinite
preferred link-local fe80::1, life infinite
link MTU 1500 (true link MTU 4294967295)
current hop limit 128
reachable time 29000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 0

C:\Documents and Settings\Administrator>ipv6 rt
::/0 -> 4/2001:470:1f00:367::1 pref 0 life infinite (manual)]]> <![CDATA[IPv6 Multiplayer Gaming Network]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-5.html Sun, 01 Nov 2009 17:08:06 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-5.html http://sourceforge.net/projects/sinet/

It is described as follows:
The aim of the SiNET (Secure Integrated Network) is to develop a secure Multiplayer network for the gaming industry using the next generation IP protocol, IPv6. Upon this framework services will be developed including Portals, Wireless services.........

The project is still categorised as 'In Planning' but the project manager has informed me the project is live but off to a slow start.

If there are any developers out there that could lend a hand I'm sure your help would be appreciated.

This could certainly become something interesting.]]> http://sourceforge.net/projects/sinet/

It is described as follows:
The aim of the SiNET (Secure Integrated Network) is to develop a secure Multiplayer network for the gaming industry using the next generation IP protocol, IPv6. Upon this framework services will be developed including Portals, Wireless services.........

The project is still categorised as 'In Planning' but the project manager has informed me the project is live but off to a slow start.

If there are any developers out there that could lend a hand I'm sure your help would be appreciated.

This could certainly become something interesting.]]> <![CDATA[TurboIRC 5 Supports IPv6 IRC networks]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-4.html Sun, 01 Nov 2009 17:07:07 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-4.html http://www.turboirc.com/t

An advanced IRC and communication program, extremely small < 1MB but yet the most powerful.
Available in 9 languages (English,Greek,German,French,Portuguese,Hungarian,Spanish,Czech,Estonian) and 7 experimental ones.
For the beginner,HTML Setup/Repair/Uninstall and documentation,Tutorials and Easy-Usage Trainers,Smileys & emoticons,Easy/Advanced mode.
For the advanced IRC user,Full unique IPv6 support,Auto-update when newer version is found,custom menus,Flash IRC messages,ActiveX Chats,VBScripts,JavaScripts,ICQ,PGP and MP3 support,C-style scripting language,calendar,
notebook,RTF support,animated text support,alarm editor,enhanced preferences and logging options,Skinable,Plugins supported, and a huge collection of popups.]]> http://www.turboirc.com/t

An advanced IRC and communication program, extremely small < 1MB but yet the most powerful.
Available in 9 languages (English,Greek,German,French,Portuguese,Hungarian,Spanish,Czech,Estonian) and 7 experimental ones.
For the beginner,HTML Setup/Repair/Uninstall and documentation,Tutorials and Easy-Usage Trainers,Smileys & emoticons,Easy/Advanced mode.
For the advanced IRC user,Full unique IPv6 support,Auto-update when newer version is found,custom menus,Flash IRC messages,ActiveX Chats,VBScripts,JavaScripts,ICQ,PGP and MP3 support,C-style scripting language,calendar,
notebook,RTF support,animated text support,alarm editor,enhanced preferences and logging options,Skinable,Plugins supported, and a huge collection of popups.]]> <![CDATA[ircNET IRC Servers]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-3.html Sun, 01 Nov 2009 17:04:13 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-3.html I-lines only for Estonian clients.
irc.ipv6.estpak.ee _________ 2001:7d0::6666
No I-line requests. Open I-lines for Estonian clients
linz.irc.at ________________ 2001:628:fffe:ffff:204:76ff:fe23:2024
I-line web form: http://www.irc.at/ipv6/
irc6.nara.wide.ad.jp _______ 2001:200:0:1::800:6667
Japanese clients only.
irc6.edisontel.it __________ 2001:750:2:0:202:a5ff:fef0:aac7
I-lines only for Italian ip-ranges
irc6.ngnet.it ______________ 2001:6b8:0:700::1
I-lines only for Italian ip-ranges
irc.song.fi ________________ 2001:6e8::1
"no ipv6 I-lines"
irc.powertech.no ___________ 2001:840::1001
irc.ipv6.cesnet.cz _________ 2001:718:1:1:203:47ff:fe71:9eaa
Czech and Slovak users only.
irc.cc.tut.fi ______________ 2001:708:310:4952:4320:5365:7276:6572
irc6.seed.net.tw ___________ 2001:cd8:3002:0:2e0:18ff:fe00:4d35
irc.uni-erlangen.de ________ 2001:638:a00:2::53
No I-Lines for non .DE Addresses. Others: irc@uni-erlangen.de
irc.ipv6.oamk.fi ___________ 2001:708:510:31:203:baff:fe06:2fb2
ipv6.irc.hu ________________ 3ffe:2c03Big Grin0::1
irc.ipv6.xs4all.nl _________ 2001:888:0:2::6667
web form: http://requests.ipv6.xs4all.nl (ipv6 only)]]> I-lines only for Estonian clients.
irc.ipv6.estpak.ee _________ 2001:7d0::6666
No I-line requests. Open I-lines for Estonian clients
linz.irc.at ________________ 2001:628:fffe:ffff:204:76ff:fe23:2024
I-line web form: http://www.irc.at/ipv6/
irc6.nara.wide.ad.jp _______ 2001:200:0:1::800:6667
Japanese clients only.
irc6.edisontel.it __________ 2001:750:2:0:202:a5ff:fef0:aac7
I-lines only for Italian ip-ranges
irc6.ngnet.it ______________ 2001:6b8:0:700::1
I-lines only for Italian ip-ranges
irc.song.fi ________________ 2001:6e8::1
"no ipv6 I-lines"
irc.powertech.no ___________ 2001:840::1001
irc.ipv6.cesnet.cz _________ 2001:718:1:1:203:47ff:fe71:9eaa
Czech and Slovak users only.
irc.cc.tut.fi ______________ 2001:708:310:4952:4320:5365:7276:6572
irc6.seed.net.tw ___________ 2001:cd8:3002:0:2e0:18ff:fe00:4d35
irc.uni-erlangen.de ________ 2001:638:a00:2::53
No I-Lines for non .DE Addresses. Others: irc@uni-erlangen.de
irc.ipv6.oamk.fi ___________ 2001:708:510:31:203:baff:fe06:2fb2
ipv6.irc.hu ________________ 3ffe:2c03Big Grin0::1
irc.ipv6.xs4all.nl _________ 2001:888:0:2::6667
web form: http://requests.ipv6.xs4all.nl (ipv6 only)]]> <![CDATA[Not Only Two 2.0 supports IPv6 connections]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-2.html Sun, 01 Nov 2009 17:02:38 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-2.html http://www.turboirc.com/not

The ONLY voice and video chat program that allows MORE THAN TWO (and up to 100) users to chat
with voice and video simultaneously.
Full IPv6 listen and connect support.
HTML documentation.
Compatible with ICQ,MSN Messenger and TurboIRC.
Auto updates itself when necessary.]]> http://www.turboirc.com/not

The ONLY voice and video chat program that allows MORE THAN TWO (and up to 100) users to chat
with voice and video simultaneously.
Full IPv6 listen and connect support.
HTML documentation.
Compatible with ICQ,MSN Messenger and TurboIRC.
Auto updates itself when necessary.]]> <![CDATA[IPv6 Only Network (QaD Quickstart)]]> http://www.ipv6forum.forums.vedovanetwork.com/thread-1.html Sun, 01 Nov 2009 16:57:20 +0100 http://www.ipv6forum.forums.vedovanetwork.com/thread-1.html
First, you need 2 peices of software, TOTD (Trick or Treat Daemon), and Ptrtd (Pretty Tasty Routing Toad Demon, I guess). (In *BSD there is "Faithd" in place of Ptrtd, but hell it's a Linux forum)

Your IPv6 network is setup as usual. Now, your 'IPv6->IPv4 Masq' router must have IPv6 support and TUN/TAP support. This option is found in the Network Options section in 2.4 I believe.

Install totd on the target system, and when configuring it, you want it to listen on IPv6 on your internal network. You can listen to all too, but external users may be able to translate ipv4 addresses to ipv6 addresses at your expense (oh no!)

At this point, you will decide on a 'fake' IPv6 block for your translated IPv4 addresses. But first, let's look at what it all means.

Yahoo.com A 66.218.71.198

and, as reported from TOTD on my configuration:
Yahoo.com AAAA 2005:0:0:ffff::42da:47c6

Neat, huh? Well, 2005:0:0:ffff::/64 is a completely invalid block, but easy to route etc. etc.

In the translated IPv6 addy, the last 2 quads represend the IPv4 address in hex. Don't worry, this is the same method Ptrtd (or faithd) uses.

Now, your workstations on your lan (and servers) should have a route for the 2005:0:0:ffff::/64 block pointing to your ptrtd router. Ptrtd does the physical work. Install Ptrtd, and take a look at the config. Your prefixes must match, and generally they should always be /64's.

It's likely not safe to have ptrtd listening on an external interface (ie, outside the lan) and i would suggest to run the router behind an IPMASQ firewall for good measure.

If all is configured, fire up ptrtd and you should be able to connect to any IPv4 service from your IPv6 only network using any IPv6 capable software!


Post any questions below, I'm hoping for a few.]]>
First, you need 2 peices of software, TOTD (Trick or Treat Daemon), and Ptrtd (Pretty Tasty Routing Toad Demon, I guess). (In *BSD there is "Faithd" in place of Ptrtd, but hell it's a Linux forum)

Your IPv6 network is setup as usual. Now, your 'IPv6->IPv4 Masq' router must have IPv6 support and TUN/TAP support. This option is found in the Network Options section in 2.4 I believe.

Install totd on the target system, and when configuring it, you want it to listen on IPv6 on your internal network. You can listen to all too, but external users may be able to translate ipv4 addresses to ipv6 addresses at your expense (oh no!)

At this point, you will decide on a 'fake' IPv6 block for your translated IPv4 addresses. But first, let's look at what it all means.

Yahoo.com A 66.218.71.198

and, as reported from TOTD on my configuration:
Yahoo.com AAAA 2005:0:0:ffff::42da:47c6

Neat, huh? Well, 2005:0:0:ffff::/64 is a completely invalid block, but easy to route etc. etc.

In the translated IPv6 addy, the last 2 quads represend the IPv4 address in hex. Don't worry, this is the same method Ptrtd (or faithd) uses.

Now, your workstations on your lan (and servers) should have a route for the 2005:0:0:ffff::/64 block pointing to your ptrtd router. Ptrtd does the physical work. Install Ptrtd, and take a look at the config. Your prefixes must match, and generally they should always be /64's.

It's likely not safe to have ptrtd listening on an external interface (ie, outside the lan) and i would suggest to run the router behind an IPMASQ firewall for good measure.

If all is configured, fire up ptrtd and you should be able to connect to any IPv4 service from your IPv6 only network using any IPv6 capable software!


Post any questions below, I'm hoping for a few.]]>