From: pomac@vapor.com
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux-kernel <Linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: [ipv6] Odd behaviour...
Date: Thu, 29 May 2008 10:59:14 +0200 [thread overview]
Message-ID: <20080529085914.GE11812@pomac.netswarm.net> (raw)
In-Reply-To: <20080529015131.da6bdcfb.akpm@linux-foundation.org>
On Thu, May 29, 2008 at 01:51:31AM -0700, Andrew Morton wrote:
> On Thu, 29 May 2008 10:41:57 +0200 pomac@vapor.com wrote:
>
> > On Thu, May 29, 2008 at 12:27:29AM -0700, Andrew Morton wrote:
> > > On Tue, 27 May 2008 00:58:30 +0200 Ian Kumlien <pomac@vapor.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > I just recently acquired a new ipv6 tunnel since my two previous brokers
> > > > has gone out of business. I now use hurricane electrics tunnel since i
> > > > have really good ping times to it's node in Amsterdam.
> > > >
> > > > Anyways, i have setup a local network tunnel and enabled forwarding.
> > > >
> > > > After about 300 seconds, it all stops working. I have to disable and
> > > > re-enable it on the firewall/router to get it working again.
> > > >
> > > > tcpdump shows the router/firewall doing odd things like:
> > > > (i renamed my host to piv6)
> > > >
> > > > 00:48:14.294173 IP6 piv6 > igloo.stacken.kth.se: ICMP6, echo request,
> > > > seq 321, length 64
> > > >
> > > > 00:48:14.341288 IP6 igloo.stacken.kth.se > piv6: ICMP6, echo reply, seq
> > > > 321, length 64
> > > >
> > > > 00:48:14.341317 IP6 fe80::55e4:1b90 > igloo.stacken.kth.se: ICMP6,
> > > > redirect, piv6 to piv6, length 160
> > > >
> > > > 00:48:14.341332 IP6 igloo.stacken.kth.se > piv6: ICMP6, echo reply, seq
> > > > 321, length 64
> > > > ---
> > > >
> > > > fe80::55e4::1b90 is the local ip of the ipv6 tunnel.
> > > > (note: the packet never arrives at it's destination)
> > > >
> > > > Any ideas of what could be going wrong?
> > >
> > > (cc netdev - afaik linux-net is kind of dead)
> >
> > Thanks, i knew i missed something, -net was the one that was already in
> > my email client so... =)
>
> Yeah. linux-net _might_ be a hive of activity, dunno. I haven't been
> there in years. Perhaps it should be retired.
Heh, i'll look in the archives... =)
> > > What kernel version are you running?
> >
> > The router/fw is running 2.6.25.1, the client is running 2.6.25.4
> >
> > Any additional information i should provide?
>
> It would be interesting if you know of any earlier kernel version which
> works OK?
Well, for me it was ages since i used ipv6... So i can't really help. I
was more hoping for someone in the same position or someone who'd seen
something simular and solved it.
>From what i gather, i have done nothing wrong and a forward shouldn't
time out. Ie, if it works it should keep working.
It would be really interesting to see what the other end of a ipv6
tunnel sees when it pings, but i don't have the means to test that
currently.
next prev parent reply other threads:[~2008-05-29 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 22:58 Ian Kumlien
2008-05-29 7:27 ` Andrew Morton
2008-05-29 8:41 ` pomac
2008-05-29 8:51 ` Andrew Morton
2008-05-29 8:59 ` pomac [this message]
2008-05-29 9:28 ` YOSHIFUJI Hideaki / 吉藤英明
2008-05-29 10:08 ` pomac
2008-05-29 10:46 ` YOSHIFUJI Hideaki / 吉藤英明
2008-05-29 12:20 ` pomac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080529085914.GE11812@pomac.netswarm.net \
--to=pomac@vapor.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=akpm@linux-foundation.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®