mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Eckenfels <be-mail2004@lina.inka.de>
To: Trent Lloyd <lathiat@bur.st>
Cc: linux-net@vger.kernel.org
Subject: How to turn off IPV6 (link local)
Date: Wed, 16 Jun 2004 03:17:43 +0200	[thread overview]
Message-ID: <20040616011743.GA15385@lina.inka.de> (raw)
In-Reply-To: <20040616001630.GB24753@thump.bur.st>

On Wed, Jun 16, 2004 at 08:16:31AM +0800, Trent Lloyd wrote:
> Ahh, i see, however you would have to set autoconf to off then *remove*
> the link-local addresses, because they are setup before that variable is
> changed? [or is there an option for this in the kernel? afaik its just
> in proc (sysctl)]

you can set net.ipv6.conf.defaul.autoconf=0 and then up the interface. This
will prevent it from getting any  announced prefixes, but it wont prevent it
from getting linklocal prefix.

So my idea is, that autoconf=0 will prevent it from getting linklocal and
advertised adddresses and accept_ra=0 will prevent it from getting announced
prefixes.

> That said, the link-local addresses are *NOT* the issue here, and having
> them will not cause said problems, the problem here is the user has 4
> real world IPv6 addresses configured by a router on his network + user
> configuration (the 6to4 address).

Well, the user does not have them now anymore and Mozilla uses the
link-local. However I agree with you, that it might not help to remove
(prevent autoconfgration) because mozilla still might suceed in AF_INET6
binding and try the connect w/o failback.

> Check out http://www.sixlabs.org/talks/, in my IPv6 programming talk I
> have code showing how to use getaddrinfo() and try each address until
> one suceeds.

There is btw an additional issue with sending AAAA requests on a host which
is not fully configured for ipv6. In fact I think we should disable to
compile ipv6 into the kernel, its so painfull to turn the AF off.

Greetings
Bernd
-- 
  (OO)      -- Bernd_Eckenfels@Mörscher_Strasse_8.76185Karlsruhe.de --
 ( .. )      ecki@{inka.de,linux.de,debian.org}  http://www.eckes.org/
  o--o     1024D/E383CD7E  eckes@IRCNet  v:+497211603874  f:+497211606754
(O____O)  When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!

      reply	other threads:[~2004-06-16  1:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 23:32 Bernd Eckenfels
2004-06-15  2:30 ` Trent Lloyd
2004-06-15 19:46   ` Bug#253590: " Bernd Eckenfels
2004-06-15 21:27     ` Felipe Alfaro Solana
2004-06-15 22:58       ` Bernd Eckenfels
2004-06-16  0:16     ` Trent Lloyd
2004-06-16  1:17       ` Bernd Eckenfels [this message]

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=20040616011743.GA15385@lina.inka.de \
    --to=be-mail2004@lina.inka.de \
    --cc=lathiat@bur.st \
    --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

all inboxes | Powered by JetHome®