[6bone] .NET RC1 IPv6 6to4

[Matthew Lehman]

It's a holdover from the original research stack.  However it doesn't
work quite like you've detailed.  When the 6to4 auto-tunneling interface
comes up, it attempts to discover 6to4 relays via a DNS lookup to
6to4.ipv6.microsoft.com.  If you lookup that record it resolves to the
MS relay (131.107.33.60) and the 6to4 anycast address.  It attempts to
ping the v4 addresses that are returned.  If you want to override this
behavior, you can set the relay manually:

netsh interface ipv6 6to4 set relay <preferred relay> enabled
<resolution interval in min.>

My machines at home are setup to go to the MS relay because I know it's
topologically close and the closest advertised relay using the 6to4
anycast address is at SWITCH which is a long way from home.

To setup a configured tunnel, follow the instructions in Nicolas' email.

You can find most of this information in the help section of .Net
server.  Just search for IPv6 and/or 6to4 via the help interface.


> -----Original Message-----
> From: Pekka Savola [mailto:pekkas@netcore.fi]
> Sent: Friday, October 11, 2002 7:35 AM
> To: Barker, Ron, vpe
> Cc: 6bone@mailman.isi.edu
> Subject: Re: [6bone] .NET RC1 IPv6 6to4
> 
> Note '2002:c058:6301::c058:6301' below.
> 
> That only works with Microsoft relays because there's a completely
bogus
> and non-interoperable assumption that the relay has address
> '2002:c058:6301::c058:6301' and it's pingable.
> 
> Not a good way to push IPv6 *at all*...
> 
> On Fri, 11 Oct 2002, Barker, Ron, vpe wrote:
> 
> > Has anyone been able to get connected to the 6bone with  .NET RC1
IPv6.
> I have tried in vain for 2 day to no avail.  Some really strange
things
> happens depending on whether the computer is / is not
> > attached to the internet.  Really strange is the fact that prior to
> plugging in the ethernet cable the 6to4 interface is disable,
however,
> whenever I have link to the net, the 6to4 has two strange
> > looking default routes that are automatically generated:
> >
> > Publish  Type       Met  Prefix                    Idx
> Gateway/Interface Name
> > -------  --------  ----  ------------------------  ---
----------------
> -----
> > yes      Manual    1221 	 ::/0                        3
> 2002:836b:213c:1:e0:8f08:f020:8
> > yes      Manual    2147483648  ::/0                  3
> 2002:c058:6301::c058:6301
> > yes      Manual    1001  2002::/16                   3  6to4
Tunneling
> Pseudo-Interface
> >
> > netsh interface ipv6>
> >
> >
> > 1. is a  ::/0 route to what is obviously a rely router at MS -
> 131.107.33.60 - tried pinging but no answer
> > 2- is a  ../0 route to a 192.xxx. route ?????
> >
> > Where do these addresses come from???? magic.
> >
> > Additionaly,  I miss any any all reference to setting up the tunnel.
> >
> >
> > Any comments appreciated
> >
> > Ron
> >
> >
> >
> >
> >
> > Dr. Ronald D. Barker
> > Vodafone Pilotentwicklung GmbH
> > Chiemgaustr. 116
> > D-81549 Munich
> > Germany
> > Fon +49 (89) 95 410 -0
> > Fax +49 (89) 95 410 -111
> > www.v-pe.de
> >
> >
> >
> 
> --
> Pekka Savola                 "Tell me of difficulties surmounted,
> Netcore Oy                   not those you stumble over and fall"
> Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords
> 
> _______________________________________________
> 6bone mailing list
> 6bone@mailman.isi.edu
> http://mailman.isi.edu/mailman/listinfo/6bone