patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity
zephyr/subsys/net/ip/Kconfig.ipv6

228 lines
6.8 KiB
Plaintext
Raw Normal View History

kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 13:45:29 +01:00
# IPv6 Options
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
# Copyright (c) 2016 Intel Corporation.
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 02:01:01 +01:00
# SPDX-License-Identifier: Apache-2.0
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
menuconfig NET_IPV6
bool "IPv6"
default y
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
Enable IPv6 support. This should be selected by default as there
is limited set of network bearers provided that support IPv4.
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
if NET_IPV6
net: if: Make interface IP configuration more flexible Instead of always allocating both IPv6 and IPv4 address information to every network interface, allow more fine grained address configuration. So it is possible to have IPv6 or IPv4 only network interfaces. This commit introduces two new config options: CONFIG_NET_IF_MAX_IPV4_COUNT and CONFIG_NET_IF_MAX_IPV6_COUNT which tell how many IP address information structs are allocated statically. At runtime when network interface is setup, it is then possible to attach this IP address info struct to a specific network interface. This can save considerable amount of memory as the IP address information struct can be quite large (depends on how many IP addresses user configures in the system). Note that the value of CONFIG_NET_IF_MAX_IPV4_COUNT and CONFIG_NET_IF_MAX_IPV6_COUNT should reflect the estimated number of network interfaces in the system. So if if CONFIG_NET_IF_MAX_IPV6_COUNT is set to 1 and there are two network interfaces that need IPv6 addresses, then the system will not be able to setup IPv6 addresses to the second network interface in this case. This scenario might be just fine if the second network interface is IPv4 only. The net_if.c will print a warning during startup if mismatch about the counts and the actual number of network interface is detected. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2018-01-19 18:01:23 +01:00
config NET_IF_MAX_IPV6_COUNT
int "Max number of IPv6 network interfaces in the system"
net: if: vlan: Add virtual lan support This allows creation of virtual lan (VLAN) networks. VLAN support is only available for ethernet network technology. Fixes #3234 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2018-01-19 11:24:33 +01:00
default NET_VLAN_COUNT if NET_VLAN
net: ip: Increase the number of IPv4/IPv6 interfaces with loopback In case loopback interface is enabled, it's most likely there will be more than a one network interface if running on real hardware. Therefore increase the default IPv4/IPv6 interface count to avoid the need to increase it manually in every test suite. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2022-10-25 13:56:02 +02:00
default 2 if NET_LOOPBACK
Kconfig: Use the first default with a satisfied condition Up until now, Zephyr has patched Kconfig to use the last 'default' with a satisfied condition, instead of the first one. I'm not sure why the patch was added (it predates Kconfiglib), but I suspect it's related to Kconfig.defconfig files. There are at least three problems with the patch: 1. It's inconsistent with how Kconfig works in other projects, which might confuse newcomers. 2. Due to oversights, earlier 'range' properties are still preferred, as well as earlier 'default' properties on choices. In addition to being inconsistent, this makes it impossible to override 'range' properties and choice 'default' properties if the base definition of the symbol/choice already has 'range'/'default' properties. I've seen errors caused by the inconsistency, and I suspect there are more. 3. A fork of Kconfiglib that adds the patch needs to be maintained. Get rid of the patch and go back to standard Kconfig behavior, as follows: 1. Include the Kconfig.defconfig files first instead of last in Kconfig.zephyr. 2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of last in arch/Kconfig. 3. Include arch/<arch>/soc/*/Kconfig first instead of last in arch/<arch>/Kconfig. 4. Swap a few other 'source's to preserve behavior for some scattered symbols with multiple definitions. Swap 'source's in some no-op cases too, where it might match the intent. 5. Reverse the defaults on symbol definitions that have more than one default. Skip defaults that are mutually exclusive, e.g. where each default has an 'if <some board>' condition. They are already safe. 6. Remove the prefer-later-defaults patch from Kconfiglib. Testing was done with a Python script that lists all Kconfig symbols/choices with multiple defaults, along with a whitelist of fixed symbols. The script also verifies that there are no "unreachable" defaults hidden by defaults without conditions As an additional test, zephyr/.config was generated before and after the change for several samples and checked to be identical (after sorting). This commit includes some default-related cleanups as well: - Simplify some symbol definitions, e.g. where a default has 'if FOO' when the symbol already has 'depends on FOO'. - Remove some redundant 'default ""' for string symbols. This is the implicit default. Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and BT_L2CAP_TX_MTU (caused by confusing inconsistency). Piggyback some fixes for style nits too, e.g. unindented help texts. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 10:57:47 +02:00
default 1
net: if: Make interface IP configuration more flexible Instead of always allocating both IPv6 and IPv4 address information to every network interface, allow more fine grained address configuration. So it is possible to have IPv6 or IPv4 only network interfaces. This commit introduces two new config options: CONFIG_NET_IF_MAX_IPV4_COUNT and CONFIG_NET_IF_MAX_IPV6_COUNT which tell how many IP address information structs are allocated statically. At runtime when network interface is setup, it is then possible to attach this IP address info struct to a specific network interface. This can save considerable amount of memory as the IP address information struct can be quite large (depends on how many IP addresses user configures in the system). Note that the value of CONFIG_NET_IF_MAX_IPV4_COUNT and CONFIG_NET_IF_MAX_IPV6_COUNT should reflect the estimated number of network interfaces in the system. So if if CONFIG_NET_IF_MAX_IPV6_COUNT is set to 1 and there are two network interfaces that need IPv6 addresses, then the system will not be able to setup IPv6 addresses to the second network interface in this case. This scenario might be just fine if the second network interface is IPv4 only. The net_if.c will print a warning during startup if mismatch about the counts and the actual number of network interface is detected. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2018-01-19 18:01:23 +01:00
help
Kconfig: Use the first default with a satisfied condition Up until now, Zephyr has patched Kconfig to use the last 'default' with a satisfied condition, instead of the first one. I'm not sure why the patch was added (it predates Kconfiglib), but I suspect it's related to Kconfig.defconfig files. There are at least three problems with the patch: 1. It's inconsistent with how Kconfig works in other projects, which might confuse newcomers. 2. Due to oversights, earlier 'range' properties are still preferred, as well as earlier 'default' properties on choices. In addition to being inconsistent, this makes it impossible to override 'range' properties and choice 'default' properties if the base definition of the symbol/choice already has 'range'/'default' properties. I've seen errors caused by the inconsistency, and I suspect there are more. 3. A fork of Kconfiglib that adds the patch needs to be maintained. Get rid of the patch and go back to standard Kconfig behavior, as follows: 1. Include the Kconfig.defconfig files first instead of last in Kconfig.zephyr. 2. Include boards/Kconfig and arch/<arch>/Kconfig first instead of last in arch/Kconfig. 3. Include arch/<arch>/soc/*/Kconfig first instead of last in arch/<arch>/Kconfig. 4. Swap a few other 'source's to preserve behavior for some scattered symbols with multiple definitions. Swap 'source's in some no-op cases too, where it might match the intent. 5. Reverse the defaults on symbol definitions that have more than one default. Skip defaults that are mutually exclusive, e.g. where each default has an 'if <some board>' condition. They are already safe. 6. Remove the prefer-later-defaults patch from Kconfiglib. Testing was done with a Python script that lists all Kconfig symbols/choices with multiple defaults, along with a whitelist of fixed symbols. The script also verifies that there are no "unreachable" defaults hidden by defaults without conditions As an additional test, zephyr/.config was generated before and after the change for several samples and checked to be identical (after sorting). This commit includes some default-related cleanups as well: - Simplify some symbol definitions, e.g. where a default has 'if FOO' when the symbol already has 'depends on FOO'. - Remove some redundant 'default ""' for string symbols. This is the implicit default. Piggyback fixes for swapped ranges on BT_L2CAP_RX_MTU and BT_L2CAP_TX_MTU (caused by confusing inconsistency). Piggyback some fixes for style nits too, e.g. unindented help texts. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-07-30 10:57:47 +02:00
This tells how many network interfaces there will be in the system
that will have IPv6 enabled.
net: if: Make interface IP configuration more flexible Instead of always allocating both IPv6 and IPv4 address information to every network interface, allow more fine grained address configuration. So it is possible to have IPv6 or IPv4 only network interfaces. This commit introduces two new config options: CONFIG_NET_IF_MAX_IPV4_COUNT and CONFIG_NET_IF_MAX_IPV6_COUNT which tell how many IP address information structs are allocated statically. At runtime when network interface is setup, it is then possible to attach this IP address info struct to a specific network interface. This can save considerable amount of memory as the IP address information struct can be quite large (depends on how many IP addresses user configures in the system). Note that the value of CONFIG_NET_IF_MAX_IPV4_COUNT and CONFIG_NET_IF_MAX_IPV6_COUNT should reflect the estimated number of network interfaces in the system. So if if CONFIG_NET_IF_MAX_IPV6_COUNT is set to 1 and there are two network interfaces that need IPv6 addresses, then the system will not be able to setup IPv6 addresses to the second network interface in this case. This scenario might be just fine if the second network interface is IPv4 only. The net_if.c will print a warning during startup if mismatch about the counts and the actual number of network interface is detected. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2018-01-19 18:01:23 +01:00
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
config NET_IF_UNICAST_IPV6_ADDR_COUNT
int "Max number of unicast IPv6 addresses per network interface"
net: openthread: Simplify openthread enabling Currently user needs to specify quite much additional options to enable OpenThread support. He also needs to set ip address count, heap size, etc depending on features enabled. Nade changes to automatically select/set some of the options on enabling OpenThread Signed-off-by: Marek Porwisz <marek.porwisz@nordicsemi.no>
2020-06-19 13:22:32 +02:00
default 6 if NET_L2_OPENTHREAD
drivers: net: loopback: Register loopback IP address to the interface Regsiter loopback IPv4/IPv6 to the loopback interface during interface initialization. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2021-10-06 16:45:44 +02:00
default 3 if NET_LOOPBACK
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
default 2
config NET_IF_MCAST_IPV6_ADDR_COUNT
int "Max number of multicast IPv6 addresses per network interface"
net: openthread: Simplify openthread enabling Currently user needs to specify quite much additional options to enable OpenThread support. He also needs to set ip address count, heap size, etc depending on features enabled. Nade changes to automatically select/set some of the options on enabling OpenThread Signed-off-by: Marek Porwisz <marek.porwisz@nordicsemi.no>
2020-06-19 13:22:32 +02:00
default 8 if NET_L2_OPENTHREAD
net: ipv6: Increase default multicast address count to 3 Usually it is not enough to have just one IPv6 multicast address defined for the network interface. So allocate three IPv6 multicast addresses for the network interface as IPv6 by default uses multicast a lot. This hopefully will avoid some mysterious errors if the addresses run out. Note that this will increase memory usage a bit so you might need to lower the count in your conf file if memory is low. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-07-07 14:02:28 +02:00
default 3
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
config NET_IF_IPV6_PREFIX_COUNT
int "Max number of IPv6 prefixes per network interface"
default 2
net: ipv6: Fix Kconfig dependencies when native IPv6 is disabled In case native IPv6 is disabled, Kconfig entries related to native IPv6 stack should not be enabled. Otherwise, circular dependencies can be created if native stack is disabled, as in case of recent changes in NET_IPV6_RA_RDNSS option (where a dependency for a native stack module was enabled). Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2023-03-21 12:43:28 +01:00
if NET_NATIVE_IPV6
net: ipv6: Allow user to configure the IPv6 MTU size This makes it possible to set the minimum IPv6 packet size that can be sent without fragmentation. The default value is 1280 bytes. This commit allows user to set the IPv6 MTU value within reasonable limits [1280, 1500]. Fixes #61587 Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2024-02-09 08:37:38 +01:00
config NET_IPV6_MTU
int "Initial IPv6 MTU value"
default 1280
range 1280 1500
help
The value should normally be 1280 which is the minimum IPv6 packet
size that implementations need to support without fragmentation.
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
config NET_INITIAL_HOP_LIMIT
net: Add support for adjusting IPv6 multicast hop limit Add option support for adjusting the IPv6 multicast multicast hop limit value. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2023-11-28 15:41:44 +01:00
int "Initial IPv6 hop limit value for unicast packets"
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
default 64
net: Add support for adjusting IPv6 multicast hop limit Add option support for adjusting the IPv6 multicast multicast hop limit value. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2023-11-28 15:41:44 +01:00
range 0 255
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
help
net: Add support for adjusting IPv6 multicast hop limit Add option support for adjusting the IPv6 multicast multicast hop limit value. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
2023-11-28 15:41:44 +01:00
The value should normally be > 0. The device receiving the IPv6
packet will decrement the value and will drop the packet if the hop
limit value is 0. When sending, the packet is dropped before
transmitting to network if hop limit is 0.
config NET_INITIAL_MCAST_HOP_LIMIT
int "Initial IPv6 hop limit value for multicast packets"
default 1
range 0 255
help
The value should normally be > 0. The device receiving the IPv6
packet will decrement the value and will drop the packet if the hop
limit value is 0. When sending, the packet is dropped before
transmitting to network if hop limit is 0.
The default is 1 (same as in IPv4) which means that multicast packets
don't leave the local network unless the application explicitly
requests it.
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
config NET_IPV6_MAX_NEIGHBORS
int "How many IPv6 neighbors are supported"
default 8
range 1 254
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
The value depends on your network needs.
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
net: ipv6: Support fragmented IPv6 packets This commit adds support for IPv6 packet fragmentation when receiving (IPv6 reassembly) and when sending larger than 1280 bytes long IPv6 packet. See RFC 2460 chapter 4.5 for more details. Jira: ZEP-1718 Change-Id: Ia31c147cce4d456ee48f39276cca99aa09ce81d6 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-28 16:43:32 +02:00
config NET_IPV6_FRAGMENT
bool "Support IPv6 fragmentation"
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
IPv6 fragmentation is disabled by default. This saves memory and
should not cause issues normally as we support anyway the minimum
length IPv6 packets (1280 bytes). If you enable fragmentation
support, please increase amount of RX data buffers so that larger
than 1280 byte packets can be received.
net: ipv6: Support fragmented IPv6 packets This commit adds support for IPv6 packet fragmentation when receiving (IPv6 reassembly) and when sending larger than 1280 bytes long IPv6 packet. See RFC 2460 chapter 4.5 for more details. Jira: ZEP-1718 Change-Id: Ia31c147cce4d456ee48f39276cca99aa09ce81d6 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-28 16:43:32 +02:00
config NET_IPV6_FRAGMENT_MAX_COUNT
int "How many packets to reassemble at a time"
range 1 16
default 1
depends on NET_IPV6_FRAGMENT
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
How many fragmented IPv6 packets can be waiting reassembly
simultaneously. Each fragment count might use up to 1280 bytes
of memory so you need to plan this and increase the network buffer
count.
net: ipv6: Support fragmented IPv6 packets This commit adds support for IPv6 packet fragmentation when receiving (IPv6 reassembly) and when sending larger than 1280 bytes long IPv6 packet. See RFC 2460 chapter 4.5 for more details. Jira: ZEP-1718 Change-Id: Ia31c147cce4d456ee48f39276cca99aa09ce81d6 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-28 16:43:32 +02:00
net: ip: replace hardcoded NET_IPV6_FRAGMENTS_MAX_PKT with a Kconfig Currently the stack is limited to a maximum of 2 incoming fragments per packet. While this can be enough in most cases, it might not be enough in other cases. Make this value configurable at build time. Signed-off-by: Florian Vaussard <florian.vaussard@gmail.com>
2021-07-09 15:08:24 +02:00
config NET_IPV6_FRAGMENT_MAX_PKT
int "How many fragments can be handled to reassemble a packet"
default 2
depends on NET_IPV6_FRAGMENT
help
Incoming fragments are stored in per-packet queue before being
reassembled. This value defines the number of fragments that
can be handled at the same time to reassemble a single packet.
We do not have to accept IPv6 packets larger than 1500 bytes
(RFC 2460 ch 5). This means that we should receive everything
within the first two fragments. The first one being 1280 bytes and
the second one 220 bytes.
You can increase this value if you expect packets with more
than two fragments.
net: ipv6: Support fragmented IPv6 packets This commit adds support for IPv6 packet fragmentation when receiving (IPv6 reassembly) and when sending larger than 1280 bytes long IPv6 packet. See RFC 2460 chapter 4.5 for more details. Jira: ZEP-1718 Change-Id: Ia31c147cce4d456ee48f39276cca99aa09ce81d6 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-28 16:43:32 +02:00
config NET_IPV6_FRAGMENT_TIMEOUT
int "How long to wait the fragments to receive"
range 1 60
net: ipv6: Default reassembly timeout set to 5 sec The previous default 60 seconds is way too long for our limited amount of memory. It might be that the 5 sec is still too long but that can be changed in the future. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-05-19 22:19:46 +02:00
default 5
net: ipv6: Support fragmented IPv6 packets This commit adds support for IPv6 packet fragmentation when receiving (IPv6 reassembly) and when sending larger than 1280 bytes long IPv6 packet. See RFC 2460 chapter 4.5 for more details. Jira: ZEP-1718 Change-Id: Ia31c147cce4d456ee48f39276cca99aa09ce81d6 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-28 16:43:32 +02:00
depends on NET_IPV6_FRAGMENT
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
How long to wait for IPv6 fragment to arrive before the reassembly
will timeout. RFC 2460 chapter 4.5 tells to wait for 60 seconds but
this might be too long in memory constrained devices. This value
is in seconds.
net: ipv6: Support fragmented IPv6 packets This commit adds support for IPv6 packet fragmentation when receiving (IPv6 reassembly) and when sending larger than 1280 bytes long IPv6 packet. See RFC 2460 chapter 4.5 for more details. Jira: ZEP-1718 Change-Id: Ia31c147cce4d456ee48f39276cca99aa09ce81d6 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-28 16:43:32 +02:00
net: ipv6: Add support to join/leave multicast group This and subsequent commits adds API to join or leave an IPv6 multicast group. Jira: ZEP-1673 Change-Id: I26dcfe16a4527dbf7886a30827a5d4ebfdeaac01 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-02-09 08:55:15 +01:00
config NET_IPV6_MLD
bool "Multicast Listener Discovery support"
default y
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
The value depends on your network needs. MLD should normally
be active. Currently we support only MLDv2. See RFC 3810 for
details.
net: ipv6: Add support to join/leave multicast group This and subsequent commits adds API to join or leave an IPv6 multicast group. Jira: ZEP-1673 Change-Id: I26dcfe16a4527dbf7886a30827a5d4ebfdeaac01 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-02-09 08:55:15 +01:00
net: ipv6: Make config options more fine grained Add CONFIG_NET_IPV6_NBR_CACHE option that is the base for both neighbor discovery (ND) and duplicate address detection (DAD). Both ND and DAD can be disabled if needed. If NBR cache is disabled, then ND and DAD are disabled too. Note that it makes not much sense to disable DAD or NBR cache as IPv6 will not work properly without them. It is possible to disable ND but then the neighbor information needs to come via other sources like RPL. Change-Id: I57c8668ad828b3a153dfc58eea78bf5f7ac3938a Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-14 10:15:13 +01:00
config NET_IPV6_NBR_CACHE
bool "Neighbor cache"
default y
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
The value depends on your network needs. Neighbor cache should
normally be active.
net: ipv6: Make config options more fine grained Add CONFIG_NET_IPV6_NBR_CACHE option that is the base for both neighbor discovery (ND) and duplicate address detection (DAD). Both ND and DAD can be disabled if needed. If NBR cache is disabled, then ND and DAD are disabled too. Note that it makes not much sense to disable DAD or NBR cache as IPv6 will not work properly without them. It is possible to disable ND but then the neighbor information needs to come via other sources like RPL. Change-Id: I57c8668ad828b3a153dfc58eea78bf5f7ac3938a Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-14 10:15:13 +01:00
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
config NET_IPV6_ND
bool "Activate neighbor discovery"
net: ipv6: Make config options more fine grained Add CONFIG_NET_IPV6_NBR_CACHE option that is the base for both neighbor discovery (ND) and duplicate address detection (DAD). Both ND and DAD can be disabled if needed. If NBR cache is disabled, then ND and DAD are disabled too. Note that it makes not much sense to disable DAD or NBR cache as IPv6 will not work properly without them. It is possible to disable ND but then the neighbor information needs to come via other sources like RPL. Change-Id: I57c8668ad828b3a153dfc58eea78bf5f7ac3938a Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-14 10:15:13 +01:00
depends on NET_IPV6_NBR_CACHE
net/ipv6: Enforce MLD to be selected if ND is enabled As noted in net_if.c:net_if_ipv6_addr_add() IPv6 ND needs MLD. It is not selected during test, as the combination of ND without DAD/MLD breaks (something to study/fix further it seems). Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2023-12-13 19:08:48 +01:00
select NET_IPV6_MLD if !NET_TEST
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
default y
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
The value depends on your network needs. ND should normally
be active.
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
config NET_IPV6_DAD
bool "Activate duplicate address detection"
net: ipv6: Make config options more fine grained Add CONFIG_NET_IPV6_NBR_CACHE option that is the base for both neighbor discovery (ND) and duplicate address detection (DAD). Both ND and DAD can be disabled if needed. If NBR cache is disabled, then ND and DAD are disabled too. Note that it makes not much sense to disable DAD or NBR cache as IPv6 will not work properly without them. It is possible to disable ND but then the neighbor information needs to come via other sources like RPL. Change-Id: I57c8668ad828b3a153dfc58eea78bf5f7ac3938a Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-03-14 10:15:13 +01:00
depends on NET_IPV6_NBR_CACHE
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
default y
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
The value depends on your network needs. DAD should normally
be active.
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
config NET_IPV6_RA_RDNSS
bool "Support RA RDNSS option"
net: Remove CONFIG_NET_IPV6_NO_ND config option The option is no longer used so it can be removed. Use CONFIG_NET_IPV6_ND option instead. Change-Id: Ibaa3d3deb52b8b176e85f8b9e1d8c80c1026aea1 Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
2017-01-26 12:13:42 +01:00
depends on NET_IPV6_ND
net: icmpv6: Implement IPv6 RA Recursive DNS Server option Handle RA RDNSS and use the first DNS server fetched. This is needed when building IPv6 only without static DNS server IP addresses. This implementation does not handle the lifetime, because the current resolve logic does not have support for a DNS server lifetime. Signed-off-by: Stig Bjørlykke <stig.bjorlykke@nordicsemi.no>
2023-02-20 08:26:15 +01:00
select DNS_RESOLVER
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
default y
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
Support Router Advertisement Recursive DNS Server option.
See RFC 6106 for details. The value depends on your network needs.
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
config NET_6LO
kconfig: remove Enable from boolean prompts According to Kconfig guidelines, boolean prompts must not start with "Enable...". The following command has been used to automate the changes in this patch: sed -i "s/bool \"[Ee]nables\? \(\w\)/bool \"\U\1/g" **/Kconfig* Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-03-09 12:05:12 +01:00
bool "6lowpan IPv6 Compression library"
net/6lo: Enable it by default if IEEE 802.15.4 is enabled This rework commit 77b8f5c1f635b12160fa0111e4f1d1b68b41bc78 Comparing it to BT IPSP is a the wrong comparison: BT IPSP does specify 6lo/ipv6 for it to work. Whereas 802.15.4 does not. Instead of selecting 6lo from 802.15.4's Kconfig, let's do the reverse way. If the user enabled 802.15.4 and IPv6 as well (to which 6lo depends on), then 6lo is enabled by default as using IPv6 on 15.4 without it does not make much sense. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-10-06 18:15:54 +02:00
default y if NET_L2_IEEE802154
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
6lowpan compression and fragmentation. It is enabled by default
if 802.15.4 is present, since using IPv6 on it requires it.
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
net: l2: ieee802154: decouple L2/L3 concerns This change decouples the IEEE 802.15.4 (L2) layer from all IPv6 (L3) concerns. Applications may now choose to set CONFIG_NET_6LO=n and CONFIG_NET_L2_IEEE802154=y at the same time. Setting CONFIG_NET_6LO=n will build a vanilla IEEE 802.15.4-2006 specs compliant L2 layer without any reference to 6LoWPAN or IPv6. This allows application developers to design custom non-IP protocols on top of IEEE 802.15.4-2006 and thereby makes the L2 layer much more re-usable. Fixes #48585. Signed-off-by: Florian Grandel <jerico.dev@gmail.com>
2022-08-02 20:19:10 +02:00
You may disable this option if you wish to implement a non-IP
custom protocol on top of the 802.15.4 MAC (L2) layer.
net: Add support for 6CO 6lowpan context options(CO) are supplied in RA (Router Advertisement) message. Added support for parsing and cache it. This information will be used in context based compression and uncompression. Change-Id: I6e9b5bf02aab3a574ba6a1454232e2d56e855bb0 Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
2016-10-05 16:20:06 +02:00
config NET_6LO_CONTEXT
kconfig: remove Enable from boolean prompts According to Kconfig guidelines, boolean prompts must not start with "Enable...". The following command has been used to automate the changes in this patch: sed -i "s/bool \"[Ee]nables\? \(\w\)/bool \"\U\1/g" **/Kconfig* Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-03-09 12:05:12 +01:00
bool "6lowpan context based compression"
net: Add support for 6CO 6lowpan context options(CO) are supplied in RA (Router Advertisement) message. Added support for parsing and cache it. This information will be used in context based compression and uncompression. Change-Id: I6e9b5bf02aab3a574ba6a1454232e2d56e855bb0 Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
2016-10-05 16:20:06 +02:00
depends on NET_6LO
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
Enables 6lowpan context based compression based on information
net: l2: ieee802154: improve inline comments This change contains some merely editorial changes to inline comments plus updates references from the IEEE 802.15.4-2003 spec to IEEE 802.15.4-2006 which corresponds to the implementation level of the module. Signed-off-by: Florian Grandel <jerico.dev@gmail.com>
2022-08-02 20:03:35 +02:00
received in Router Advertisement (RA) message.
net: Add support for 6CO 6lowpan context options(CO) are supplied in RA (Router Advertisement) message. Added support for parsing and cache it. This information will be used in context based compression and uncompression. Change-Id: I6e9b5bf02aab3a574ba6a1454232e2d56e855bb0 Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
2016-10-05 16:20:06 +02:00
config NET_MAX_6LO_CONTEXTS
int "Number of supported 6CO (6lowpan contexts options)"
net: Fix leaving NET_MAX_6LO_CONTEXTS set when 6lowpan deselected Make NET_MAX_6LO_CONTEXTS depends on NET_6LO_CONTEXT, otherwise at the moment even deselecting 6lowpan leaves NET_MAX_6LO_CONTEXTS set. Change-Id: Iaa34d324005817be05190e203f6899ab89f89e5d Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
2017-01-27 11:49:35 +01:00
depends on NET_6LO_CONTEXT
default 1
net: Add support for 6CO 6lowpan context options(CO) are supplied in RA (Router Advertisement) message. Added support for parsing and cache it. This information will be used in context based compression and uncompression. Change-Id: I6e9b5bf02aab3a574ba6a1454232e2d56e855bb0 Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
2016-10-05 16:20:06 +02:00
range 1 16
help
kconfig: fix more help spacing issues Fix Kconfig help sections and add spacing to be consistent across all Kconfig file. In a previous run we missed a few. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-02-15 14:36:16 +01:00
6lowpan context options table size. The value depends on your
network and memory consumption. More 6CO options uses more memory.
net: Add support for 6CO 6lowpan context options(CO) are supplied in RA (Router Advertisement) message. Added support for parsing and cache it. This information will be used in context based compression and uncompression. Change-Id: I6e9b5bf02aab3a574ba6a1454232e2d56e855bb0 Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
2016-10-05 16:20:06 +02:00
net: Convert core IP stack to use log levels Instead of one global log level option and one on/off boolean config option / module, this commit creates one log level option for each module. This simplifies the logging as it is now possible to enable different level of debugging output for each network module individually. The commit also converts the code to use the new logger instead of the old sys_log. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2018-07-06 10:35:07 +02:00
if NET_6LO
module = NET_6LO
module-dep = NET_LOG
module-str = Log level for 6LoWPAN library
module-help = Enables 6LoWPAN code to output debug messages.
source "subsys/net/Kconfig.template.log_config.net"
endif # NET_6LO
module = NET_IPV6
module-dep = NET_LOG
module-str = Log level for core IPv6
module-help = Enables core IPv6 code to output debug messages.
source "subsys/net/Kconfig.template.log_config.net"
net: ipv6: Introduce separate logger module for IPv6 ND Debugging IPv6 Neighbor Discovery issues requires to enable full IPv6 logs, which can get bloated given it provides logs for every single packet. We should be able to focus on IPv6 ND logs only, hence introduce a separate log module for IPv6 ND. Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2024-03-19 16:23:50 +01:00
module = NET_IPV6_ND
module-dep = NET_LOG
module-str = Log level for IPv6 Neighbor Discovery
module-help = Enables IPv6 Neighbor Discovery code to output debug messages.
source "subsys/net/Kconfig.template.log_config.net"
net: Convert core IP stack to use log levels Instead of one global log level option and one on/off boolean config option / module, this commit creates one log level option for each module. This simplifies the logging as it is now possible to enable different level of debugging output for each network module individually. The commit also converts the code to use the new logger instead of the old sys_log. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2018-07-06 10:35:07 +02:00
module = NET_ICMPV6
module-dep = NET_LOG
module-str = Log level for ICMPv6
module-help = Enables ICMPv6 code to output debug messages.
source "subsys/net/Kconfig.template.log_config.net"
module = NET_IPV6_NBR_CACHE
module-dep = NET_LOG
module-str = Log level for IPv6 neighbor cache
module-help = Enables IPv6 Neighbor Cache code to output debug messages.
source "subsys/net/Kconfig.template.log_config.net"
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
net: ipv6: Fix Kconfig dependencies when native IPv6 is disabled In case native IPv6 is disabled, Kconfig entries related to native IPv6 stack should not be enabled. Otherwise, circular dependencies can be created if native stack is disabled, as in case of recent changes in NET_IPV6_RA_RDNSS option (where a dependency for a native stack module was enabled). Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
2023-03-21 12:43:28 +01:00
endif # NET_NATIVE_IPV6
net: Move IPv6 related Kconfig options to its own file As option list will grow, it will be saner to put them there instead of growing the base Kconfig. Change-Id: I610c47540e4fd6784b70198986813b737a38165c Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-08-24 10:01:20 +02:00
endif # NET_IPV6
Reference in a new issue Copy permalink