Demo client not working: getaddrinfo() error: Name or service not known about anjay HOT 2 CLOSED

@eabase

The most serious error seem to be this one:

/Anjay/deps/avs_commons/src/net/compat/posix/avs_compat_addrinfo.c:242]: 
getaddrinfo() error: Name or service not known; family == (avs_net_af_t) 2

Also not sure why it is logged as DEBUG when it's clearly an ERROR.

It's an error only on a very low-level layer, but not really an error in the big picture perspective. Anjay is attempting to resolve the hostname as an IPv6 address (that's what (avs_net_af_t) 2 is referring to), and this fails. It then proceeds to resolve the same hostname as IPv4, and that apparently succeeds. That's also why it's logged on the DEBUG level.

The most relevant log message seems to be this one:

2023-08-03 16:01:13.543408 ERROR [avs_net] [/cygdrive/c/mydev/pr_anjay/Anjay/deps/avs_commons/src/net/mbedtls/avs_mbedtls_socket.c:1311]: handshake failed: -26624

I agree that those handshake errors can be cryptic, but the -26624 code refers to a timeout. You can find that by grepping Mbed TLS sources:

kfyatek@kfyatek-pc:/usr/include/mbedtls$ printf '0x%x\n' 26624
0x6800
kfyatek@kfyatek-pc:/usr/include/mbedtls$ grep -r 0x6800
ssl.h:#define MBEDTLS_ERR_SSL_TIMEOUT                           -0x6800

Handshake timeout may mean, well, literally anything ;) but in my experience, the most probable cause is that the DTLS credentials are not recognized by the server. Please double-check that the identity and key are matching on both sides. Please also check that they are in the same format on both sides - since you're using --key-as-string, please make sure that on the server side, the key is also treated as a literal string, as opposed to e.g. encoded as hex or base64.

What kind of server are you trying to connect to? Is it an installation of Coiote DM, or maybe Leshan? We may be able to provide hints on configuring the server in that case.

If you're sure that everything matches and you're still getting this error, then please provide a packet capture (PCAP). It might be helpful in further debugging the issue.

from anjay.

Hi @kFYatek

Thank you for that explanation. 💯
Indeed the client was also compiled with IPv6.

From that it seem that some corporate firewall is blocking connections to the coap/s ports, as we're using a CoioteDM provided server.

from anjay.