From: Jeff Garzik <jgarzik@pobox.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Netdev <netdev@oss.sgi.com>,
YOSHIFUJI Hideaki / ???????????? <yoshfuji@linux-ipv6.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: IPv6 badness continues
Date: Tue, 04 Jan 2005 18:26:27 -0500 [thread overview]
Message-ID: <41DB2623.7000601@pobox.com> (raw)
In-Reply-To: <20050104093335.GB7823@xi.wantstofly.org>
Lennert Buytenhek wrote:
> On Tue, Jan 04, 2005 at 01:40:32AM -0500, Jeff Garzik wrote:
>
>
>>Standard FC2 OS with IPv6 6to4 setup as described on
>>http://linux.yyz.us/ipv6-fc2-howto.html
>
>
> I upgraded my problematic machine to FC3, which somehow broke 6to4, and I
> didn't bother to reenable it again because the local DNS server (dnscache)
> just drops AAAA queries on the floor anyway, leading to lots of timeouts
> when trying to resolve host names, etc. Ever since 6to4 was turned off
> on that box I stopped seeing these messages.
hmmm, that's annoying. My router is still FC2, but I'll check that out
when I upgrade it to FC3.
Jeff
next prev parent reply other threads:[~2005-01-04 23:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 6:40 IPv6 badness continues Jeff Garzik
2005-01-04 9:33 ` Lennert Buytenhek
2005-01-04 20:57 ` Pekka Savola
2005-01-05 10:19 ` Lennert Buytenhek
2005-01-04 23:26 ` Jeff Garzik [this message]
2005-01-07 2:18 ` [RFC PATCH] Fix double dereference (Re: IPv6 badness continues) YOSHIFUJI Hideaki / 吉藤英明
2005-01-07 3:53 ` David S. Miller
2005-01-07 9:30 ` [RFC PATCH] Fix double dereference YOSHIFUJI Hideaki / 吉藤英明
2005-01-08 3:24 ` [RFC PATCH] Fix double dereference (Re: IPv6 badness continues) Herbert Xu
2005-01-08 4:25 ` IPv6 badness continues Herbert Xu
2005-01-08 17:24 ` Jeff Garzik
2005-01-08 18:35 ` Herbert Xu
2005-01-09 1:12 ` Jeff Garzik
2005-01-09 10:31 ` Herbert Xu
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=41DB2623.7000601@pobox.com \
--to=jgarzik@pobox.com \
--cc=buytenh@wantstofly.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).