From: Ian Kumlien <pomac@vapor.com>
To: Linux-kernel <Linux-kernel@vger.kernel.org>
Cc: linux-net <Linux-net@vger.kernel.org>
Subject: [ipv6] Odd behaviour...
Date: Tue, 27 May 2008 00:58:30 +0200 [thread overview]
Message-ID: <1211842711.8367.11.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
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?
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-05-26 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 22:58 Ian Kumlien [this message]
2008-05-29 7:27 ` [ipv6] Odd behaviour Andrew Morton
2008-05-29 8:41 ` pomac
2008-05-29 8:51 ` Andrew Morton
2008-05-29 8:59 ` pomac
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=1211842711.8367.11.camel@localhost \
--to=pomac@vapor.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=Linux-net@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