mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trent Lloyd <lathiat@bur.st>
To: Bernd Eckenfels <be-mail2004@lina.inka.de>, linux-kernel@vger.kernel.org
Cc: 253590@bugs.debian.org
Subject: Re: How to turn off IPV6 (link local)
Date: Tue, 15 Jun 2004 10:30:23 +0800	[thread overview]
Message-ID: <20040615023022.GB24269@thump.bur.st> (raw)
In-Reply-To: <20040614233215.GA10547@lina.inka.de>

Hi Bernd,

CCd: debian bug, read down to the explanation of why this is occuring
and why this is not a bug.

> While solving the debian bug #253590 against net-tools, I discovered, that
> it is not possible to turn off the link local ipv6 addresses.

Indeed.

> 
> net.ipv6.conf.default.autoconf does work for the received prefixes, but does
> not avoid the link local configuration. (this is btw a documentation error)

autoconf defines whether it will auto-configure an address if a router
advertises the IPv6 prefix for the network to it.

> 
> I would not mind the link local address much, if there wont be some
> applications (like mozilla) trying to actually use that address to reach
> internet site.
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=253590

The issue is not having the link local address, because there is no
default route and hence the connection should fail.

The problem, in the case of thi sbug, is that he has IPv6 configured,
but it is not working, 2001: is a real IPv6 address (so he has a tunnel
configured with a router to advertise) and the 2002:: is a '6ot4'
address, which something on the system has configured, and obviously
that is not working either, probably because he has a router preventing
the 6to4 packets from passsing, or the default route for the 2001:
address has a higher metric and thats still broken.

Link-local address start with fe80:: and never have a default route so
they will not be a problem.

> So my question is, how can one prevent linux kernel with build in ipv6 from
> adding the link local prefix, and are the prerequisites of an ipv6 enabled
> application to not prefer link local prefix to ipv4?

You can't, but it is not the issue here, you could however not load the
module.

Cheers,
Trent
Sixlabs

-- 
Trent Lloyd <lathiat@bur.st>
Bur.st Networking Inc.

  reply	other threads:[~2004-06-15  2:30 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 [this message]
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

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=20040615023022.GB24269@thump.bur.st \
    --to=lathiat@bur.st \
    --cc=253590@bugs.debian.org \
    --cc=be-mail2004@lina.inka.de \
    --cc=linux-kernel@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®