Zyxel_Nami  Zyxel Employee

Hello @jojo42 Could you please let us know which model of Switch you are using? Besides, please enable Zyxel Support Access on Nebula for us to further investigate your issue, and please send me your Org/Site name via private message.

Hi @jojo42 The NWA50AX AP is generally not designed to filter out multicast packets. Could you please elaborate on how you observed that the AP is filtering multicast packets? This information will help us better understand your issue.

Hello @d_p We acknowledge your issue and are currently investigating it. We will update you as soon as we have any information. Thanks

Hello Pim, The Switch GS1200-8HPv2 model and AP itself couldn't act as a DHCP Server. The best way to set up DHCP is from the modem/router, which is the uplink of the switch as per your current topology. However, this shouldn't be the cause. Aside from the modem and the 2 APs, are there any other devices connecting to the…

Hi Pim @PimK82 Thank you for sharing the test results. Based on the results, it’s assumed that the end devices couldn't communicate with each other when they were on different APs. The issue has occurred sometimes, but not all the time. To proceed with further investigation and troubleshooting, please help clarify the…

Hi Pim, Thank you for the quick update. We'd like to examine the traffic between clients and APs. Could you please assist us by conducting the following tests? First, excluding the printer: PC A and PC B are connected to AP_01. Could PC A ping PC B and vice versa? PC A and PC B are connected to AP_02. Could PC A ping PC B…

Hello Pim, Could you please assist us by testing the ping when both the client and the printer are connected to the same AP? Besides, are these 2 APs still connected to the GS1200-8HP v2, as mentioned in this forum?

Hello @d_p Firstly, please make sure that the WDS SSID, Pre-Shared Key, VLAN, and even the WDS Profile name are the same on all APs. The behavior of AP 3 and AP 4 suggests that they couldn't establish a connection with their uplink APs. Have you tried adding the MAC address of the uplink APs? Then, please go to Monitor >…

Hello @hanlimburg We've reviewed your Nebula Site and found that several IoT devices are connected to the NWA210AX (Voorhuis) via the Limbohome SSID. Some of these devices are experiencing poor signal strength at -82 and -83 dBm. This suggests that the devices are too far from the AP. For a stable connection, we recommend…

Hello @PimK82 How has the connection been since enabling U-APSD? We've observed how the printer connects to the AP. It remains connected in the morning and gets disconnected in the evening, which appears to be a stable pattern. To help us investigate further, could you please check how your computer connects to the printer…

Hi @PimK82 We're in the process of thoroughly reviewing the diagnostic files and will provide you with further feedback as soon as our analysis is complete. Let's confirm the issue! It is that your co-worker's device can see the printer, and send print commands, but the printer cannot print out. When the device is brought…

Hello @hanlimburg Yes, the NWA210AX and NWA50AX models are fully compatible and capable of establishing a Mesh network. You mentioned that all three devices are wired to a router and have smart mesh enabled. This means that they will prioritize the wired connection for communication with their uplink (the router). If the…

Hello @PimK82 Thank you for updating. I received the diagnostic files. However, we also need to check the event log on Nebula, could you please enable Zyxel Support again?

Hello @hfr_dk To view the SSID name to which a client is connected, you can navigate to the Clients > Client List tab. Once there, select Access Point Clients and click on the icon located on the right side, as shown in the screenshots below. As for your query about the navigation sidebar, Nebula underwent a UI enhancement…

Hello @gumbosauce Thank you for sharing the details of your experience. It's indeed puzzling that the default credentials didn't work in regular Chrome but worked in Edge and Chrome's Incognito mode. Regarding Chrome, it's possible that some cached data or extensions might have interfered with the login process. As a…