[Bug] TC_IDM_1_2 and TC_OPCRED_3_1 failing when TH is connected over wlan

[chirag-silabs]

Describe the bug

The docker test cases TC_IDM_1_2 and TC_OPCREDS_3_1 fails when the TH is connected over WLAN but passes when the device is connected over Ethernet LAN.

Failure when connected over WLAN TC_IDM_1_2-different-ap.log write_default_logs_DUT.txt

Passed when connected over Ethernet tc_idm_1_2_ethernet.txt

Steps to reproduce the behavior

Just running TC_IDM_1_2 in docker while TH connected over wlan

Expected behavior

Pass on the docker automation case

Log files

No response

PICS file

No response

Screenshots

No response

Environment

No response

Additional Information

No response

[antonio-amjr]

Hey @cecille,

Can you help with this issue? It's a DNS-SD resolution timeout. Since it's calling the TC_IDM_1_2 script directly, maybe it's something from the SDK's side.

[cecille]

DNS-SD resolution timeout when connected over a different interface sounds like a genuine failure, possibly related to networking.

[fabiowmm]

@chirag-silabs this looks like an environment issue and thus we need you to dig deeper to try to isolate the source. It could be a problem in your wifi network/router, in the device platform, or in the raspi platform. Please try to swap those elements in turns to try to isolate the source element of the issue.

[chirag-silabs]

@fabiowmm we have tested it on 2 setups, seen the same behavior. connecting the pi over ethernet works fine always but seeing a issue when it is connected on WLAN. Could be related to docker networking? I can share the details of my setup if needed

I have tried with raspberrypi over like 3-4 networks noticed the same

[antonio-amjr]

Hi @chirag-silabs,

Please do share more details of the setup and any additional information, like the project configuration. Also, share as well the output of the following:

• $ ./certification-tool/scripts/th/th-doctor.sh --complete
• $ docker ps
• $ docker images
• $ docker network inspect chip-default
• $ docker network inspect certification-tool_traefik-public

We'll see if we spot anything.

[chirag-silabs]

Here you go with the output of the above commanders

th_docker_issue.txt

[cecille]

Any chance you could grab a packet capture? It looks like the TH is attempting a connection, but not seeing a response from the dut. There are a number of wifi related issues that could cause this. These tests expect that all addresses advertised are reachable.

[chirag-silabs]

Sure let me capture the packets and share