Commit e288040b authored by Flavio Santes's avatar Flavio Santes Committed by Anas Nashif
Browse files

samples/net: Add KNOWN_ISSUES file for NATS and DNS sample apps 



The KNOWN_ISSUES file describes issues and workarounds for the NATS
and DNS sample applications.

Change-Id: I9a33a82073707dbdd4109e0740108b99c42ad772
Signed-off-by: default avatarFlavio Santes <flavio.santes@intel.com>
parent 8c55291e

samples/net/dns_client/KNOWN_ISSUES

0 → 100644
+17 −0
Original line number Diff line number Diff line 
Issues

------



- RX or TX error:

	Caused by:

		net_send error, see:

		https://jira.zephyrproject.org/browse/ZEP-428

		https://jira.zephyrproject.org/browse/ZEP-676



	Workaround:

		Wait until the IP stack is "activated"

		or reset the board.



Limitations

-----------



See the ./README_API file.

samples/net/nats_clients/KNOWN_ISSUES

0 → 100644
+34 −0
Original line number Diff line number Diff line 
Issues

------



- Unable to connect

	Caused by:

		Incorrect TCP flags handling from the Zephyr IP Stack.

	Workaround:

		Reset the board.



- Publisher or Subscriber error

	Caused by:

		The NATS server will send the PING message at configurable

		intervals. If the PING message is not handled by the

		client, the server will close the connection.



		The NATS applications are synchronous, so if the PING

		message arrives when the application is processing

		another message (i.e. verbose = 1), the PING message

		will be ignored and the server will close the connection.

	Workaround:

		Codify a routine similar to handle_msg (see main.c) to

		handle all the incoming messages.



- RX or TX error

	Caused by:

		Perhaps the rx/tx timeouts are too short for the LAN.

        Workaround:

		Increase the rx or tx timeout.

		See: publisher/src/netz.c, struct netz_ctx_t.



Limitations

-----------



See the ./README file.

CRA Git | Maintained and supported by SUSTech CRA and CCSE