netdev - Re: [PATCH] Assign linklocal addresses to isatap from link dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090304.032835.183524465.davem@davemloft.net>
Date:	Wed, 04 Mar 2009 03:28:35 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	mail@...chahlusiak.de
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] Assign linklocal addresses to isatap from link dev

From: Sascha Hlusiak <mail@...chahlusiak.de>
Date: Sun, 1 Mar 2009 01:34:48 +0100

> That way stateless autoconf works with isatap tunnels and without
> knowledge of the local v4 address.

This is not my understanding of how ISATAP works on hosts.

Real autoconf is not performed, but rather you must configure your
system with a PRL (potential routers list) and these routers are
probed periodically in order to keep track of which of them are still
functioning and also to perform a sort-of unicast-only autoconf.

I am pretty sure that the person who added the ISATAP code created the
current behavior intentionally.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html