Unable to obtain IP address for vtrust-flash for aoycocr mini Wi-Fi switch

Before opening a new issue, please read the following

Are you reporting a successful flash? Please add it to the wiki instead!

Do you have a question about configuring your newly flashed device? Please ask in your alternative firmware’s support channel instead!

Did you have issues getting a device to flash? Please be sure to include your device name, model, and firmware version as well as your logs!

Please remember to close your issue when the problem has been addressed!

Running tuya-convert in a kali docker image on a nuc and using an Android device to try to connect to vtrust-flash and tries to obtain an IP address but never succeeds. The tuya device is an aoycocr mini-Wi-Fi switch ([https://www.amazon.com/gp/product/B07N1JPPXK]).

CLI output:

Checking for network interface wlp3s0... Found.
Checking UDP port 53... Available.
Checking UDP port 67... Available.
Checking TCP port 80... Available.
Checking TCP port 443... Available.
Checking UDP port 6666... Available.
Checking UDP port 6667... Available.
Checking TCP port 1883... Available.
Checking TCP port 8886... Available.
======================================================
  Starting AP in a screen.............................

smarthack-wifi.log:

Stopping NetworkManager...
network-manager: unrecognized service
Configuring AP interface...
RTNETLINK answers: File exists
RTNETLINK answers: File exists
Starting DNSMASQ server...
Starting AP on wlp3s0...
Configuration file: /dev/stdin
Using interface wlp3s0 with hwaddr a0:c5:89:63:87:ba and ssid "vtrust-flash"
wlp3s0: interface state UNINITIALIZED->ENABLED
wlp3s0: AP-ENABLED 
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-DISCONNECTED 54:14:fd:01:7c:b9
wlp3s0: AP-STA-CONNECTED 54:14:fd:01:7c:b9

[kueblc]

It’s come up in some other issues that a firewall might interfere with dnsmasq. Try checking if ufw or firewalld is running.

[compactcode]

Had the same issue with docker running on a NixOS host machine. Disabling the default host firewall sorted this issue for me, thank you!