OLD, NOT UPTODATE!!!!
Mail me for a more correct information!


TD - IPv6

IPv6 project at TD by Roger Jørgensen

This pages is still under construction (and I guess it always will be), but for now I have added some info
to it, the following topics are covered by this document.

0.Who supplies us with IPv6
1.Our current network
2.Network of the Future (IPv6)
3.The  address space
4.Routing
This project are something I'm doing, if you think this sounds like fun or want to try out IPv6, we (TD) have
it and you can try it through us. BUT... it's still under development, don't expect it to be plug'n'play(r)

Anyway, the basic network we use for this are something TD has today and since I'm the one that are most
interested in testing out IPv6 I was the one who started this. Who I am? People call me Roger Jørgensen since
that's my real name, you can mail me direct or you can contact the ipv6-team at TD.

The goal for this is much harder to describe, think the only way to describe it is to say that we are trying to
learn about IPv6, both to use it and to install it, or in other words, play with IPv6 and see what it ends up with.
This way we hope to learn alot about IPv6.
 

0.Who supplies us with IPv6

University of Tromsø and some other Universities around the world has a ongoing project called
Pasta project. Part of that project are IPv6. Check the homepage for more information about them.
www.wanadoo.be where the person working with this happends to be a friend of me, axs on ircnet#ipv6
www.stealth.net where another of my friends work, also from IRCNet.
www.toledolink.com  where a good friend from DALnet work
www.chello.be  where some friends of me work with the ipv6 project, also ircnet#ipv6
www.ins.net.uk, I got a 2001 test prefix from them, efnet#ipv6

Our main uplink is The Pasta Project at UiTø but depending on where your target is you are routed through one
of the tunnels.

1.Our current network

Our current network was once very simple, one cable into the IT-department at UiTø, today it is
a bit more advanced. From the start TD was located close to the IT-department and the main
machine hall (the central place where most of the network/computer stuff are). Around 1998 and
1999 we lost our location because they wanted to use the place for something else (and if you ask me,
I personaly mean it's something stupid:))

Anyway, UiTø, or bether, Uninet was one of the first in Norway (and pretty early in the world) to
get Internet. That's why UiTø has a full class B-network, 129.242.0.0.
TD got the network 129.242.219.0.

Today it's divided into two different parts both delivered from the IT-department through two different
pairs of fiber.

Our main network:
Network prefix: 129.242.219.0-31 (netmask 255.255.255.224 if I don't remember wrong)

This network is where all the computer that belongs to TD and are direct under TD-drift@ control are
located. (TD-drift@td.org.uit.no are the admin group that run the network/system TD has.)

Our second (private) network:
Network prefix: 129.242.219.32-63 (same netmask, 255.255.255.224)

This is a new idea that came up in 1998 sometime...the basic idea is that we should give our members
a possibility to take their home computer and hook it onto our network and to Internet.
Don't missunderstand it, this network also belongs to TD and are under control of TD-drift@ but the
difference are that this is a separte network for private computers that belongs to members of TD.

This picture show the network pretty good:


 

2.Network of the Future (IPv6)

Our network, have several IPv6 uplinks, only ipv6-in-ipv4 tunnels so far. There is also another ipv6 network build on top of this,
it's a project I and some friend has started and is called 7bone, for more info about it can you mail me. Will try to get some info
online asap!
 


 

If you look at the map for our current network, ipv4 based you will find out that .4 (129.242.219.4) and
.44 (129.242.219.44) are located on those two network TD has. The reason are simple, both network
should be provided with IPv6.

We got the prefix 3ffe:2a00:100:3021::/64 (and maybe 3ffe:2a00:100:3022::/64)
 

The uplink are two IPv6-in-IPv4 tunnels to the Pasta project, the gateway are server.pasta.cs.uit.no.
US-direct are a uplink I may add sometimes in the future. I have a friend in US which has a ::/32 network,
that means 2^96 (128 - 32) addresses, that's _alot_. I want to see how it is to use a multihomed system.
How to use it, install it... just to see how it work. But before we get that far we need to have a few other
things in place. We need:

Why do I use IRCd or IRC that it's bether known as. The reason are very simple:

* IRC are chat in REAL time, that means that 1 second delay are noticed VERY easy when you talk with others.
   There are alot of issues around this, one of them are routing:

How can we reach the world from the different places? It's easy done on the host part, all the host connected
and are using IPv6, it's much harder for all the routers, two like we have/will have.
So far I have come up with this routing-table :

(OLD INFO, the new is located here)

First a few "definition":
v6gw0 - server.pasta.cs.uit.no
v6gw1 - 129.242.219.4 in ipv4
v6gw2 - 129.242.219.44 in ipv4
v6gw3 - US-direct
 

v6gw1:
router from - to traffic goes to
v6gw1 3021::/64 -> 3022::/64 v6gw2
3021::/64 -> world v6gw0
3021::/64 -> unknown::/32
3022::/64 -> unknown::/32		 v6gw3 (US-direct)
v6gw2:
router from - to traffic goes to
v6gw2 3022::/64 -> 3021::/64 v6gw1
3022::/64 -> unknown::/32 v6gw1 (US-direct connected to v6gw1)
3022::/64 -> world v6gw0
v6gw3:
router from - to traffic goes to
v6gw3 unknown::/32 v6gw1

...
 

copyright by TD 2003 - Made by Roger Jørgensen

[A