>> - you should have an IPv6 address assigned from freenet6. since
>> you are transmitting from freenet6, you need to use source
>> address from freenet6. however, you do not assign one on gif0.
>> this seems to be configuration mistake.
>It's deliberate. I didn't know of any other way to get a route
>to the 6bone and still have 2002:... as the source address for my
>packets. "It seems to work" -- like I pointed out, I was able to ping
>www.jp.freebsd.org, which is pretty close to KAME as far as addressing
>is concerned. However, I don't deny that it might break things in some
>circumstances.
>> - next. if you use 6to4 address and you are hooked to native
>> IPv6 cloud, you need to announce 2002::/16 to the native IPv6
>> cloud and you need to become a public relay for everybody (see
>> 6to4 specification). you fall into this category (since you are
>> connected to freenet6 too). do you advertise 2002::/16 to the
>> backbone?
>My goal wasn't to provide a relay -- it's just that getting stf set up
>means I have a route to 2002::/16, but it's not clear how to get from
>that to getting full IPv6 connectivity. Freenet6 was a quick hack to
>get an outgoing default route.
then, there's noone who advertise 2002::/16 toward you. I suggest you
to just use source address from freenet6.net.
itojun
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
