On Mon, Mar 06, 2000 at 09:22:45AM -0800, Bob Fink wrote:
> Please read, then ask any questions you may have. 6to4 is currently
> supported, and there are relay routers up and running.
My apologies if I sound like I need "IPv6 for Dummies".
Just to clarify. You mean that 6to4 is currently supported in FreeBSD/KAME?
Of course, I'm not quite sure what I mean by this. I guess, if I configure
a FreeBSD/KAME host as an IPv6 router, will the router automatically do the
IPv6->IPv4 encapsulation when it encounters a destination prefix of 2002::/16
and vice versa for incoming packets? Or, do I need to configure a pseudo
interface somehow (gif doesn't look quite like the right thing?). Also, will
FreeBSD/KAME hosts (both router and non-router hosts) somehow automatically
do the proper address selection algorithm when they encounter multiple IPv6
addresses, or is that an application level requirement?
Also, if I have (for example) IPv4 addresses of 204.95.187/24, I assume
I can use any of the 2002:[V4ADDR]:/48 prefixes within my allocation, but
for external 6to4 connectivity I should probably choose the V4ADDR of the
external interface of the 6to4 router?
And, finally, do some of the 6to4 relay routers that are "up and running"
serve small isolated sites? I assume the best case is that one's ISP
provides IPv6 connectivity in some shape or form. But, if thats not the
case, I assume the main options are IPv6-IPv4 tunnel to a co-operative
IPv6 site, or 6to4 with a default route to a relay router (who I assume
must configure a static route back?). Or, run a more sophisticated routing
protocol (BGP), but thats a little much for me, I think.
Of course, if everyone configures 6to4 (or at least everyone you want to reach)
then am I correct that you don't really need 6to4 "relay" routers? This is
only for reaching native IPv6 sites without 6to4 addresses?
Thanks.
--
Richard Seaman, Jr. email: [EMAIL PROTECTED]
5182 N. Maple Lane phone: 262-367-5450
Chenequa WI 53058 fax: 262-367-5852
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
