spiras

Hello; attached are 3 screenshots from wireshark capturing DNS activity from FNet dns client. The first packet is a regular dns query for www.google.com The second packet is the regular response from the server. For the purpose of this test, the response has been blocked, to force retries from the client. The third packet is a malformed retry from the client with FNET_CFG_DNS_RETRANSMISSION_MAX = 3 All retries are malformed; it looks like query retries are sent with 'response' flag set. Following...

Hello; attached are 3 screenshots from wireshark capturing DNS activity from FNet dns client. The first packet is a regular dns query for www.google.com The second packet is the regular response from the server. For the purpose of this test, the response has been blocked, to force retries from the client. The third packet is a malformed retry from the client with FNET_CFG_DNS_RETRANSMISSION_MAX = 3 All retries are malformed; it looks like query retries are sent with 'response' flag set. Following...

Hello; attached are 3 screenshots from wireshark capturing DNS activity from FNet dns client. The first packet is a regular dns query for www.google.com The second packet is the regular response from the server. For the purpose of this test, the response has been blocked, to force retries from the client. The third packet is a malformed retry from the client with FNET_CFG_DNS_RETRANSMISSION_MAX = 3 All retries are malformed; it looks like query retries are sent with 'response' flag set. Following...

Yes, it works for me. Thank you

Hello, I'm creating this topic after another post about a DNS problem, https://sourceforge.net/p/fnet/discussion/920346/thread/0748178cb3/#ad76 Now I'm seeing a different problem: all messages rejected by the client in fnet_dns.c function _fnet_dns_poll , case FNET_DNS_STATE_RX: when checking the "is response" flag in header->flags, the received message contains a correct response value (bytes 0x81 and 0x00 equal to 0x8100) but the machine evaluates the value as 0x0081 so the check always fails....

yes it was related to that same issue; the value of received was not actually 0; it receives a CNAME as rejects it thanks for the hint

thanks; I'm afraid it's not related, because: I tracked down to _fnet_dns_poll it goes into FNET_DNS_STATE_RX received is always 0 I'm still investigating

Hello, using 4.7.1 we have a case where DNS resolution fails; the DNS server is pingable from the device; in tcpdump we see the correct query packet and the response from the server, but the device does not receive the response. Any idea? I enabled the FNET_DEBUG_DNS macro, this is the output: resolving apps.xyz.com Sending query... Sending query... Sending query... Sending query... Sending query... Sending query... Timeout not resolved On the same device, telnet service is working normally. Here...