Ethernet shows disconnected after update to 0.6.8

[tmaniac]

After the update the status for my Ethernet connection says it's not connected.

However, I am browsing the web interface on the IP address i configured on the Ethernet port.

I can ping the unit on both the Ethernet IP and the WIFI IP

see screenshot for details:

[xyzroe]

I have tested on 3 pcs wt32 and 2 pcs ttgo. All goes as it must be. Ethernet showing connected.

You should check your network setup or try to disable ping check in Ethernet section of settings.

[tmaniac]

hmm; I tried it all.

The weird thing is; i'm connected via the IP address I configured on the Ethernet port; everything seems to be working fine.

My HA-Zigbee2MQTT client talks to the gateway via that IP and I browse the web-interface via that IP.

I can also reach the GW via the WIFI-IP without any problem.

Only the main page states my Ethernet is not connected.

[Back71]

I am in the same situation as Tmaniac. Only the main page states my Ethernet is not connected.
The gateway works fine!

[xyzroe]

@tmaniac @Back71 Could you install 0.6.6 and confirm that ethernet shows successful connected?

https://github.com/xyzroe/ZigStarGW-FW/releases/tag/0.6.6

[tmaniac]

@tmaniac @Back71 Could you install 0.6.6 and confirm that ethernet shows successful connected?

https://github.com/xyzroe/ZigStarGW-FW/releases/tag/0.6.6

Sure;
on v0.6.6 it shows everything connected.

[xyzroe]

Are you sure on using a static address with the same gateway in both cases?

[tmaniac]

WIFI is DHCP; I have a reservation in my router for the WIFI mac.
The Ethernet has a static IP address in case my router doesn't work. (then at least my lights will :) )

[xyzroe]

Wi-Fi settings do not affect the state of the wired network connection.

So let's go back to the wired network.
I see that you are using static addresses, that's ok. But I can't be sure that the same default gateway address is being used because of the blur.

Why is it important?
To determine the network connection status, ZigStar pings the address that is specified as the default gateway, and if the ping is successful - the connection is ok, there is no - an error, there is no connection.

[tmaniac]

I see.

The gateway settings for both adapters (Ethernet and WiFi) are the same.

Upon your comment i checked the 'disable gateway check' box. (for the ethernet adapter)

lo and behold: after a reboot everything lights up as connected.

[Back71]

@tmaniac @Back71 Could you install 0.6.6 and confirm that ethernet shows successful connected?

https://github.com/xyzroe/ZigStarGW-FW/releases/tag/0.6.6

yes, i tried with ver. 0.6.6, it's ok

instead with version 0.6.6.8

I checked the 'disable gateway check' box. (for the ethernet adapter) but nothing to do.

IF i uncheck 'Enable Wi-Fi client mode'

It's ok!

I also have the WT32-ETH01 version and it is the same thing on my home wifi network.

[xyzroe]

Ok guys thanks for the info.
I will try to repeat your problem and then find a solution.

[rea-ducks]

I also noticed the behaviour noted here after moving my LilyZig to a newly created IoT VLAN on my router. Everything was working as it should but the UI still stated No Ethernet and the emergency WiFi spun up.

Just before writing a me too here I checked reachability of my GW for ICMP and – nothing. So enabled pinging of my GW in the firewall, restarted the ESP and no emergency WiFI anymore.

Just wanted to write about my experience as a note it's worth to be checked.

[xyzroe]

I also noticed the behaviour noted here after moving my LilyZig to a newly created IoT VLAN on my router. Everything was working as it should but the UI still stated No Ethernet and the emergency WiFi spun up.

Just before writing a me too here I checked reachability of my GW for ICMP and – nothing. So enabled pinging of my GW in the firewall, restarted the ESP and no emergency WiFI anymore.

Just wanted to write about my experience as a note it's worth to be checked.

@rea-ducks You are absolutely right. As I wrote earlier - "To determine the network connection status, ZigStar pings the address that is specified as the default gateway, and if the ping is successful - the connection is ok, there is no - an error, there is no connection." So your firewall should not block ping packets to the address specified as the default gateway.

@Back71 Unfortunately, I have not yet been able to repeat the situation as you have.
Do you still have this problem on new firmware?

[Back71]

Hi, I have updated to ver. 0.6.10 but it always doesn't show ethernet ip.