Brian McCullough wrote:
> On Mon, Dec 22, 2008 at 12:08:57PM +1300, Bill Walker wrote:
>> Brian,
>
> Thank you for the help, Bill and Everybody.
>
>
> I think, however, that I should back up a few steps and start again.
>
>
> What documentation, HowTo pages, or other instructions would you
> recommend to guide a "newbee" from "turn on computer" to "watch the
> dancing turtle?" I know that this is a Debian group, but since I have a
> mixed network, I am open to different flavours of instructions.
There is no generic document afaik, but I might point to the following
http://www.sixxs.net/wiki/Subnet which is a good read so that you know
how a subnet looks like ;)
And some config stuff:
http://www.sixxs.net/wiki/Installing_a_Subnet
http://www.sixxs.net/wiki/Aiccu/Installation
There is quite some more info in that Wiki and also in the FAQ.
It all depends on what you are looking for. The Forums can be of help
there too.
But generally it is:
* Get connectivity
- native where possible
- tunneled otherwise
I would recommend AGAINST using Teredo and 6to4 unless you only
want a temporary setup. (IPv4 changes means changing your network)
Next to the various issues that one will run into with it like
asymmetric routing etc etc etc.
= You know will most likely have at least a /64 for connecting to
your ISP and if requested a /48 or /56 from them too.
* Draw a little map of your network
- In that map everything on the same switch (L2, unrouted L3)
lives in the same /64, thus out of your /48 assign one /64
to that part.
eg if you have 2001:db8:4321::/48 from your ISP then you
can use 2001:db8:4321:0001::/64 for your first subnet and
2001:db8:4321:0002::/64 for the second one.
* Give routers out of those prefixes a fixed IP, eg for the
router on the first subnet use 2001:db8:4321:1::1
Then if you need to route a /64 or more to another router
on that prefix you can route it to eg 2001:db8:4321:1::2
(ip -6 ro add 2001:db8:4321:2::/64 via 2001:db8:4321:1::2)
* Now start configuring stuff
- Setup the native connectivity or tunnel
- Route the blocks where they need to go
- Install radvd on router boxes so that they announce the
respective routes et voila
* Play with it
Of course you can make it complex by introducing BGP/OSPF/IS-IS etc etc
etc. And there is a lot more to it than the above.
And remember when running into issues ALWAYS look and provide:
- Output of:
- OS, kernel, distro version etc
- interface lists (ip -6 link sho && ip -6 addr sho)
- routing tables (ip -6 ro sho)
- problems on local net: ip -6 nei sho)
- firewall configuration
- antivirus tools in use
- traceroute
- Check if your clock is synced (required for AYIYA/heartbeat tunnels)
and to debug use things like Wireshark, traceroute etc.
When using tunnels realize that there might be a problem on the IPv4
level, thus always also look at the underlying interface when using tunnels.
Greets,
Jeroen
Attachment:
signature.asc
Description: OpenPGP digital signature