Broken the connectivity check for FLEX200H

PeterUK

FLEX200H V1.30(ABWV.0)ITS-m6149

Port 4335 which I believe is the checker packets are being sent out by FLEX200H but no reply as of yet.

Now working seems to take some hours before it works again not that accurate

From what I can tell the IP its sending SYN too was waiting for the FLEX200H to send RST to then allow the SYN

GiuseppeR

Hi, I saw similar issues until yesterday.

Same hardware, 200H linked to a Nebula Organization:

Zyxel_Kay

Hi @PeterUK & @GiuseppeR

Could you let us know if the device continued working properly on your end when it lost connection with Nebula CC?

It seems the device connection on PeterUK’s site has returned to normal. GiuseppeR, is yours back to normal as well? If the issue persists, could you please enable Zyxel Support access and share your organization and site name with us?

PeterUK

Yes the device continues to work properly but when is disconnected from the internet for like 10 minutes then back up which of cause will mean offline for that time but the connectivity check does not re-establish when its back online.

like a show the FLEX200H is sending SYN to port 4335 but the server is not accepting it at least not right away may take a hour or When the server allows the SYN.

GiuseppeR

Hello @Zyxel_Kay

on site everything was nice, the secretaries were working smoothly, anyway I received all the notifications regarding a false WAN connection/disconnections from Nebula. Adding to that I was unable to launch firewall UI from Nebula, also because I did NOT set open ports from WAN to protect the firewall access so it is mandatory to have Nebula to trigger remote UI. To verify and manage this problem I connected remotely to Org internal PC and then from that local browser went to firewall UI.

Zyxel_Kay

Hi @PeterUK and @GiuseppeR

After discussing this case with our development team, we confirmed that Nebula CC had a maintenance period affecting the USG FLEX 200H during that time. The issue was fully resolved on Oct. 31 at 02:52 UTC+0.

Thank you for bringing this to our attention, and we appreciate your understanding!