uzg-01 zigstar wireguard vpn client not working

[toloomierz]

Describe the bug
wireguard not working over wifi

Device information
Model UZG-01
Firmware 20240707
Hardware ESP32-D0WDQ6

Role Coordinator
Firmware 20240710

[xyzroe]

Have you checked that config over LAN ?

[toloomierz]

No only via wifi , and i watched tcpdump and there was no traffic at all

[xyzroe]

Please make one more test but using wired connection to check your configuration.

[toloomierz]

I'll let U know

[toloomierz]

It's working via ethernet but not with wifi alone , and I would appreciate it if VPN over WiFi would work

[toloomierz]

it works when i connect to vpn via eth and wifi on and when i disconnect eth, connection over wifi is still enabled and working , but wifi mode is changing from client to AP, as below

"Mode AP
SSID XZG-B1BB
DHCP Enabled
IP 172.16.2.111
Subnet 255.255.255.0 (Access point)
Gateway 192.168.1.1 (this device)
DNS 172.16.1.101
RSSI
noConn dBm
MAC 94:B9:7E:E2:27:9C"
when i reboot the device, the problem is back and no traffic is going through the wifi interface

[xyzroe]

Ok. Thanks for investigation. I'll try to fix it and let you know

[toloomierz]

thx.

[Oliviakrkk]

I guess this is the bug I was hitting when I reported #78 . I always tested using WIFI.

I have the same problem.

[Oliviakrkk]

Is there a way to enable debug logs, check routing table or just check the initalization order? I wanted to check if wifi is connected first, then the wg.begin is called.

[1166] | [ZB] Chip: CC2652P7
[1167] | [ZB] IEEE: 00:12:4B:00:2E:0E:1C:75
[1177] | [ZB] Flash size: 704 KB
[2290] | [Time] Sat Jul 27 13:33:40 2024
[2291] | [UPD_CHK] cron 4 0 1 * * *
[2395] | WG was initialized
[5207] | [DNS] Saved WiFi - 1.1.1.1
[8577] | [ZB] FW: 20240710

[Oliviakrkk]

Hi @xyzroe ,

Is there any test which I could do to help you solve this problem?

[xyzroe]

No, thanks.
I need just some free time and motivation 😀
Someday it will happen.

[Oliviakrkk]

Today I did rollback to reenable zigbee network, as I really need my humidity monitoring back :-). The new guide how to configure it helped.

Looks like the last working version is 20240531 and it stopped working in 20240602.

2024053...2024060

[toloomierz]

@Oliviakrkk , thx for info, I'll do the rollback to 20240531

[toloomierz]

it is solved now . thx

[Oliviakrkk]

@toloomierz on which firmware? I installed 20240914 and are unable to connect.

[toloomierz]

@toloomierz on which firmware? I installed 20240914 and are unable to connect.

20241001