flottmedia  Ally Member

Thanks for detailled explanation, @Zyxel_Joslyn. The setting you describe in the last paragraph is exactly what we would like to achieve. However, we have one (of two) WAX-650S connected by wire directly to a switch that changes the uplink without any visible reason to WIRELESS after a certain while (mur-sp-ap-ost),…

Thanks, @Zyxel_Richard, I used the search before my post, but didn't come across the other (very helpful) post. We currently observe a PoE power of around 10 to 12 from both APs on the switch. Do you have an estimate number of clients causing a power consumption > 30 W (leading to a reboot of the APs in that non…

Thanks for clarification @Nebula_Jonas. Was quite a bit of manual work to get the lost names back, but at least I can confirm that the naming mechanism now seems to be consistent between GW, AP and SW clients.

Thanks for the follow-up, @Nebula_Jonas. I'm not sure, if I understand your "editing question" completely, but to clarify (2): yes, both MACs had been edited and have shown their correct name before the bug, but did not get their name back after the fix. Regarding (3): correct, we are talking about 30 days, but the DHCP…

OK, @Nebula_Jonas, support user nebula.cso@zyxel.com.tw is now activated for the organization (identical to our username). Indeed, most of the devices meanwhile have their name back, but we see several MACs that had been renamed and seem to have lost their description, e.g. XX:XX:XX:8B:70:AC, XX:XX:XX:6B:8B:38…

Thanks for the follow-up, @Nebula_Jonas. As "next week" is already over and we still face this issue, are there any updates about the fix?

As far as I can see, there are two issues at the moment: 1. (Still) a name change via "Edit Name" in AP / Switch is only reflected in AP > Clients and SW > Clients, but NOT in GW > Clients and vice versa. For me this is clearly a bug and I don't see any reason for this behavior, because it simply leads to inconsistencies.…

It's been a while since we talked about this issue / suggettion, @Nebula_Freda, @Nebula_CSO, but with one of the latest Nebula CC / firmware updates the client alias (description field) seems to have been messed up again. At least, a lot our our formerly manually "named" devices now have their MAC / submitted device name…

Thanks for the follow-up, @Nebula_Bayardo, and good to hear that some of the features are already on the roadmap. Regarding your questions: (2) Especially the client pages would be very helpful here. Maybe a login-based profile setting for the default "to display" settings could also be a sustainable option. (3) Maybe…

Thanks! Are there any plans for something like a "Hybrid Upgrade" for http://www.zyxel.com/products_services/12-port-10GbE-Smart-Managed-Switch-XS1920-Series/, so that we could already use a Zyxel Switch for smaller settings, that will later (e.g. Q2/20) be able to talk to Nebula with a new Firmware?

BTW, what happened to the Mesh option for APs? At least under Site-wide >Configuration >General there is no more configuration option for that. Furthermore, any news or updated schedules on support for NWA1123-AC HD for Mesh?

Look and feel is nice, however here a few pain points: 1. IP column Sorting should respect .1 < .2 < .1XX < .2XX. 2. User specific defaults for "Results per page" and "Last X hours / days" is still not configurable or at least "remembered" by e.g. a cookie. 3. Are there any quick filtering options for colums or at least…

As we see growing need for higher end to end speeds, are there any plans to get other / smaller 10Gbe-Switches into Nebula, e.g. XS1920? XS3800 might be a good choise for bigger network cores / aggregation settings, but for other use cases, e.g. server / NAS connections in smaller offices it's definitely too expensive and…

Maybe one further addition: we already tried the capture / display filter(s) from https://wiki.wireshark.org/LinkAggregationControlProtocol on ALL NICs simultaneously without ANY LACP packet beeing captured by Wireshark on both servers. @Nebula_Jason: Could you perhaps try that with your Windows Server from the screenshot…

In general it would be helpful to have more detailled information on certain events. E.g. "STP topology changes" could also display an added / changed / removed MAC and Port or "Port X - PortX link down" also the MAC, IP, name of the device in the log details similar to the detail field of some NAP log entries.