OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/tests/net/iface/prj.conf

27 lines
626 B
Plaintext
Raw Normal View History

tests: net: Add tests for network interface Change-Id: I35f0b3f1794c65b08d32ca561b6189ee59a7a76c Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-02-01 18:49:04 +08:00
CONFIG_NETWORKING=y
net: enable SLIP only on QEMU targets In many networking tests we had to configure SLIP in the prj.conf leaving those configurations Qemu specific. This change enables SLIP for QEMU targets automatically and allows reuse of prj.conf for multiple boards. Additionally, the TUN options is removed. This option was not used anywhere. To enable self-contained networking tests that do not depend on SLIP, we introduce the new option NET_TEST which disables TAP and allows testing in QEMU without the need for a host interface. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-07-26 20:45:13 +08:00
CONFIG_NET_TEST=y
tests: net: Add tests for network interface Change-Id: I35f0b3f1794c65b08d32ca561b6189ee59a7a76c Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-02-01 18:49:04 +08:00
CONFIG_NET_IPV6=y
CONFIG_NET_UDP=y
CONFIG_NET_TCP=n
CONFIG_NET_IPV4=n
CONFIG_NET_MAX_CONTEXTS=4
CONFIG_NET_L2_DUMMY=y
CONFIG_NET_LOG=y
CONFIG_SYS_LOG_SHOW_COLOR=y
drivers: Rename `random` to `entropy` This should clear up some of the confusion with random number generators and drivers that obtain entropy from the hardware. Also, many hardware number generators have limited bandwidth, so it's natural for their output to be only used for seeding a random number generator. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2017-10-14 07:30:55 +08:00
CONFIG_ENTROPY_GENERATOR=y
tests: net: Add tests for network interface Change-Id: I35f0b3f1794c65b08d32ca561b6189ee59a7a76c Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-02-01 18:49:04 +08:00
CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_NET_IPV6_DAD=n
net: if: Join/leave pre-defined IPv6 multicast groups When we setup the network interface, add predefined IPv6 multicast groups into the network interface. When interface is taken down, then leave all the multicast groups that joined. See RFC 4291 ch 2.8 for details. Change-Id: If17d3e8c75157a02aa93c92e2fb499619c1484cf Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-02-09 15:57:06 +08:00
CONFIG_NET_IPV6_MLD=n
net: Renaming net nbuf API to net pkt API There have been long lasting confusion between net_buf and net_nbuf. While the first is actually a buffer, the second one is not. It's a network buffer descriptor. More precisely it provides meta data about a network packet, and holds the chain of buffer fragments made of net_buf. Thus renaming net_nbuf to net_pkt and all names around it as well (function, Kconfig option, ..). Though net_pkt if the new name, it still inherit its logic from net_buf. ' This patch is the first of a serie that will separate completely net_pkt from net_buf. Change-Id: Iecb32d2a0d8f4647692e5328e54b5c35454194cd Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-04-03 23:14:35 +08:00
CONFIG_NET_PKT_TX_COUNT=10
CONFIG_NET_PKT_RX_COUNT=5
CONFIG_NET_BUF_RX_COUNT=10
CONFIG_NET_BUF_TX_COUNT=10
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-20 01:01:23 +08:00
CONFIG_NET_IF_MAX_IPV6_COUNT=3
tests: net: Add tests for network interface Change-Id: I35f0b3f1794c65b08d32ca561b6189ee59a7a76c Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-02-01 18:49:04 +08:00
CONFIG_NET_IF_UNICAST_IPV6_ADDR_COUNT=6
CONFIG_NET_MAX_NEXTHOPS=8
CONFIG_NET_IPV6_MAX_NEIGHBORS=8
CONFIG_NET_IPV6_ND=n
CONFIG_ZTEST=y
#CONFIG_NET_DEBUG_IF=y
#CONFIG_SYS_LOG_NET_LEVEL=4