Best practice for running 6to4 relays (was Re: 6to4 borkeness)

Felipe Grazziotin - SouthTech SuperDatacenter fgrazziotin at stech.net.br
Thu Mar 20 21:20:06 CET 2008


Felipe Grazziotin - SouthTech SuperDatacenter escreveu:
> Kevin Day escreveu:
>
> ...
>> It's pretty simple really:
>>
>> router bgp 19255
>>  bgp router-id 192.88.99.1
>>  network 192.88.99.0/24
>>  neighbor 216.14.98.5 remote-as 19255
>>  neighbor 216.14.98.5 update-source 216.14.98.26
>>  neighbor 2001:4978:1:410::ffff remote-as 19255
>>  no neighbor 2001:4978:1:410::ffff activate
>> !
>>  address-family ipv6
>>  network 2002::/16
>>  neighbor 2001:4978:1:410::ffff activate
>>  exit-address-family
>> !
>>
>> 216.14.98.5 is our core router's v4 address for this link. 
>> 2001:4978:1:410::ffff is it's v6 address.
>>
>>
> ...
>
> Config for BGP sounds quite acceptable, but I still don't get how 
> would one configure the ip tunnel for this kind of setup.
>
> Would that be something in the lines of:
>
> ip tunnel add tun6to4 mode sit ttl 80 remote any local 192.88.99.1
> ip link set dev tun6to4 up
> ip -6 addr add 2002:????:????:1/16 dev tun6to4
>
> (from a Linux-admin view, in this case).

Just to answer myself on that question, The IPv6 Portal already had it:

http://www.ipv6tf.org/index.php?page=using/connectivity/6to4

It teaches how to configure CISCO, LINUX and BSD for both client and 
relay mode.

>
> And, after that tunnel is up, does the 6to4 gateway start to throw 
> proto-41 packets into the internet for each 2002::/16 it is requested 
> to access?
>
That still needs to be answered, tho.

-- 
Felipe Grazziotin
25933*100




More information about the ipv6-ops mailing list