Re: 6to4 problem

To: Laitinen Ismo <laitinei@cs.tut.fi>
Cc: debian-ipv6@lists.debian.org
Subject: Re: 6to4 problem
From: Bernd Eckenfels <lists@lina.inka.de>
Date: Mon, 12 Aug 2002 09:37:32 +0200
Message-id: <[🔎] 20020812073732.GB15428@lina.inka.de>
In-reply-to: <[🔎] Pine.SOL.4.44.0208120847040.4067-100000@mustatilhi.cs.tut.fi>
References: <.ID.deb.3.0.0208120945210.29942-100000@Sniper.Security.1stWAP.com> <[🔎] Pine.SOL.4.44.0208120847040.4067-100000@mustatilhi.cs.tut.fi>

On Mon, Aug 12, 2002 at 09:09:13AM +0300, Laitinen Ismo wrote:
> ping6:
> 
> 08:49:33.274608 e272.w3.ton.tut.fi > 192.88.99.1: 2002:c1a6:5c4e::1 >
> apple.kame.net: icmp6: echo request (encap)
> 08:49:33.592821 kddilab.6to4.jp > e272.w3.ton.tut.fi: apple.kame.net >
> 2002:c1a6:5c4e::1: icmp6: echo reply (encap)
> 
> What might cause that? Something between eth0 and tunnel?

the encap mean, that it is still inside the ipv4 encapsulation. The tunnel
does not have matched in that case. I guess this is due to the fact, that it
needs to be set up with a remote "any" :)

BTW: instead of using 6to4 auto mapping you can slso use a direct tunnel to
a 6bone site. You could try www.freenet6.net

Greetings
Bernd

Reply to:

Follow-Ups:
- Re: 6to4 problem
  - From: Laitinen Ismo <laitinei@cs.tut.fi>

References:
- Re: 6to4 problem
  - From: Indra Kusuma <indra@Kusuma.OR.ID>
- Re: 6to4 problem
  - From: Laitinen Ismo <laitinei@cs.tut.fi>

Prev by Date: Re: 6to4 problem
Next by Date: Re: 6to4 problem
Previous by thread: Re: 6to4 problem
Next by thread: Re: 6to4 problem
Index(es):
- Date
- Thread