Setting up the subnet on linux 2.6
Shadow Hawkins on Saturday, 30 June 2007 16:21:26
Salutations,
I used to have an xs4all ipv6 tunnel, however because I ended my subscription, I was forced to remove that as well. Finally the time for me to try a SixXS subnet has arrived. 8-)
I am using aiccu to setup my 'primary link' (is that the right term?) and I can ping6 to ipv6 hosts. My server has eth0 as internet (not behind NAT / router), and eth1, eth2 and eth3 for LAN segments. I haven't setup the subnet yet.
My question is; is it enough to bind subnet addresses to eth1, eth2 and eth3 then and activate the subnet? Or is further action required? I am using radvd to delegate /64 subnets and i understand how to set that up. However, I'm not getting started on delegating the subnet until I understand the appropriate action.
Thanks for the help,
Mark.
Setting up the subnet on linux 2.6
Shadow Hawkins on Saturday, 30 June 2007 21:26:08
I figured, "might as well try it out and see how far I could come," and voila, got it working in no time. (I should be more confident next time |:( anyway, here are some tips for new IPv6 explorers on how I got it to work.)
I use aiccu to setup my primary IPv6 link to SixXS. This creates a 'sixxs' ip interface with one IPv6 address.
Anyway, what I did after I received my subnet details is this: If my tunnel would be 2001:838:efg::/48 (which ofcourse it isn't), I gave eth1, eth2 and eth3 the addresses 2001:838:efg:1::1/64, 2001:838:efg:2::1/64; and 2001:838:efg:3::/64. Then I configured radvd:
interface eth1 {
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
AdvDefaultPreference high;
AdvHomeAgentFlag off;
prefix 2001:838:efg:1::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};
interface eth2 {
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
AdvDefaultPreference high;
AdvHomeAgentFlag off;
IgnoreIfMissing off;
prefix 2001:838:efg:2::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};
interface eth3 {
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
AdvDefaultPreference high;
AdvHomeAgentFlag off;
prefix 2001:838:efg:3::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};
This was enough to make it work. Ofcourse client PC's usually don't need more configuration than enabling IPv6. Good luck to anyone having troubles 8-)
Setting up the subnet on linux 2.6
Shadow Hawkins on Thursday, 12 July 2007 17:01:53
Hmm, well, I have added this and it's been working for a while now. Without problems; however, for some reason my WindowsXP clients get allocated two IPv6 IP's instead of one! And only one is a valid EUI-64 address (i think.)
Could anyone please help me with this? I don't want two allocated IP's per connection, only one. The linux clients have no problems with this...
Setting up the subnet on linux 2.6
Jeroen Massar on Thursday, 12 July 2007 17:05:09
See this FAQ
Setting up the subnet on linux 2.6
Shadow Hawkins on Sunday, 22 July 2007 16:46:14
A little late, but still thanks to you, Jeroen. 8-)
Posting is only allowed when you are logged in. |