All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wichert Akkerman <wichert@wiggy.net>
To: Maciej Soltysiak <solt@dns.toxicfilms.tv>,
	netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: ipv6 stack seems to forget to send ACKs
Date: Wed, 8 Jan 2003 16:02:01 +0100	[thread overview]
Message-ID: <20030108150201.GA30490@wiggy.net> (raw)
In-Reply-To: <20030108145211.GD22951@wiggy.net>

Previously Wichert Akkerman wrote:
> traceroute to ipv6.lkml.org (2001:968:1::2) from
> 3ffe:8280:10:1d0:290:27ff:fe2d:968c, 30 hops max, 16 byte packets
>  1  thunder.wiggy.net (3ffe:8280:10:1d0:250:4ff:fe0b:dd79)  0.666 ms 0.22 ms  0.199 ms
>  2  xs4all-29.ipv6.xs4all.nl (3ffe:8280:0:2001::58)  27.568 ms  28.012 ms  30.177 ms
>  3  26.ge-0-2-0.xr1.pbw.xs4all.net (2001:888:0:3::1)  22.035 ms 19.528 ms  44.644 ms
>  4  0.ge-0-3-0.xr1.sara.xs4all.net (2001:888:2:1::1)  19.519 ms 19.002 ms  21.974 ms
>  5  fe-0-0-0.ams-core-01.network6.isp-services.nl (2001:7f8:1::a502:4875:1)  19.978 ms  30.278 ms  20.248 ms
>  6  2001:968::2 (2001:968::2)  24.246 ms  24.083 ms  22.918 ms
>  7  2001:968:1::2 (2001:968:1::2)  24.978 ms  23.866 ms  23.661 ms
> 
> thunder.wiggy.net is my Linux router running 2.4.19-pre5-ac3-freeswan196
> currently. The second hop is a normal sit tunnel and all the other
> hops are native ipv6 using Cisco and Juniper routers as far as I know.

Slight correction to that: xs4all-29.ipv6.xs4all.nl is a FreeBSD-4.5
tunnel server. The toher xs4all.net hops are Junipers running JunOS 5.3
or 5.5.

Wichert.

-- 
Wichert Akkerman <wichert@wiggy.net>           http://www.wiggy.net/
A random hacker

  reply	other threads:[~2003-01-08 14:55 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 13:08 ipv6 stack seems to forget to send ACKs Wichert Akkerman
2003-01-08 13:26 ` Maciej Soltysiak
2003-01-08 13:30   ` Wichert Akkerman
2003-01-08 13:51     ` Maciej Soltysiak
2003-01-08 13:52       ` Wichert Akkerman
2003-01-08 13:56         ` Maciej Soltysiak
2003-01-08 14:09           ` Wichert Akkerman
2003-01-08 14:43 ` Maciej Soltysiak
2003-01-08 14:52   ` Wichert Akkerman
2003-01-08 15:02     ` Wichert Akkerman [this message]
2003-01-08 16:39       ` Maciej Soltysiak
2003-01-08 16:43         ` Wichert Akkerman
2003-01-08 17:01         ` Wichert Akkerman
2003-01-08 17:43           ` Maciej Soltysiak
2003-01-08 19:52           ` Andrew McGregor
2003-01-09 22:12           ` Mika Liljeberg
2003-01-09 22:21             ` Wichert Akkerman
2003-01-08 15:22 ` Fabio Massimo Di Nitto
2003-01-08 18:05 ` Fabio Massimo Di Nitto
2003-01-08 19:59   ` Andrew McGregor
2003-01-08 20:27     ` Maciej Soltysiak
2003-01-08 20:31       ` [OT] " Fabio Massimo Di Nitto
2003-01-08 20:39         ` Andrew McGregor
2003-01-08 22:43     ` Wichert Akkerman
2003-01-09  7:29       ` Fabio Massimo Di Nitto
2003-01-09  9:38         ` Wichert Akkerman
2003-01-09  9:43           ` Fabio Massimo Di Nitto
2003-01-10 20:59             ` Paul Jakma
2003-01-09 10:32       ` Maciej Soltysiak
2003-01-09 10:40         ` Wichert Akkerman
2003-01-09 22:50     ` Bill Davidsen
2003-01-09  8:32 ` Herbert Xu
2003-01-09 11:38 ` Rogier Wolff
2003-01-09 11:55   ` Andrew McGregor
2003-01-09 15:41   ` Wichert Akkerman
2003-01-09 15:52   ` Wichert Akkerman
2003-01-09 16:03     ` Wichert Akkerman
2003-01-10  1:17     ` Andrew McGregor

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=20030108150201.GA30490@wiggy.net \
    --to=wichert@wiggy.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=solt@dns.toxicfilms.tv \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.