summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxengineering <me@xengineering.eu>2025-03-21 22:41:45 +0100
committerxengineering <me@xengineering.eu>2025-03-21 22:41:45 +0100
commit3d28070910e3cf6ec5375e18cafbda0b7b22cfc8 (patch)
tree8ab9fc53d469a2e37edf154fcab5af0ad0ac7676
parent3447721d20146ba0447ee9998838266619e4c789 (diff)
downloadiot-contact-3d28070910e3cf6ec5375e18cafbda0b7b22cfc8.tar
iot-contact-3d28070910e3cf6ec5375e18cafbda0b7b22cfc8.tar.zst
iot-contact-3d28070910e3cf6ec5375e18cafbda0b7b22cfc8.zip
fw: network: Add Kconfig-based IPv6 ULA
Using Kconfig for now is a way to continue faster for now. Proper runtime configuration should be added later. The firmware in general should be fully usable without a DHCPv6 server to not require central infrastructure. While IPv6 link-local addresses provide static and unique addresses for local communication and SLAAC provides global addresses there is still a need for an additional static address. For this there are basically two choices: - global IPv6 prefixes - IPv6 unique local addresses (ULAs) ULAs are picked with this commit. They cannot be routed which makes isolation from the internet independent of firewall rules adding security. Furthermore by picking them randomly they are in practise always unique. This allows to assign them without a central IP network management and allows to keep those addresses forever. Both great advantages over the IPv4 192.168.0.0/16 and similar ranges.
-rw-r--r--fw/prj.conf4
1 files changed, 4 insertions, 0 deletions
diff --git a/fw/prj.conf b/fw/prj.conf
index 3df3155..3d243c0 100644
--- a/fw/prj.conf
+++ b/fw/prj.conf
@@ -15,6 +15,10 @@ CONFIG_NET_TCP=y
CONFIG_NET_HOSTNAME_ENABLE=y
CONFIG_NET_HOSTNAME_DYNAMIC=y
+CONFIG_NET_CONFIG_SETTINGS=y
+CONFIG_NET_CONFIG_MY_IPV6_ADDR="fdb3:c9f2:efda:1:1"
+CONFIG_NET_IF_UNICAST_IPV6_ADDR_COUNT=4
+
CONFIG_LOG=y
CONFIG_LOG_BACKEND_NET=y
CONFIG_LOG_BACKEND_NET_SERVER="[2001:db8::2]:514"