From b5d475d1af4e0f19e96dc0fbacee0870e26a6e32 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?G=C3=B6tz=20G=C3=B6risch?= Date: Thu, 21 Mar 2024 20:24:15 +0100 Subject: [PATCH] doc: describe the IPv6 address generation (#3704) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * doc: describe the IPv6 address generation * fixes https://github.com/esphome/issues/issues/5618 * Update network.rst --------- Co-authored-by: H. Árkosi Róbert --- components/network.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/components/network.rst b/components/network.rst index 34b1d1c71..31e717ab7 100644 --- a/components/network.rst +++ b/components/network.rst @@ -22,6 +22,12 @@ Configuration variables: - **enable_ipv6** (*Optional*, boolean): Enables IPv6 support. Defaults to ``false``. - **min_ipv6_addr_count** (*Optional*, integer): ESPHome considers the network to be connected when it has one IPv4 address and this number of IPv6 addresses. Defaults to ``0`` so as to not hang on boot with networks where IPv6 is not enabled. ``2`` is typically a reasonable value for configurations requiring IPv6. +.. note:: + + The `lwIP `_ library used for the network component currently only implements IPv6 SLAAC according to `RFC4862 `_. The interface identifier (IID) is directly generated from the device MAC address. + This has various security and privacy implications decribed in `RFC7721 `_, as this might leak outside of the smart home network and makes the device uniquely identifiable. + Therefore, the address generation does not comply to `RFC7217 `_. + See Also --------