Best Of
Re: Flex H Models Routing Protocols e.g. BGP
>The feature implementation schedule is based on user requirements. We created idea posts to
>gather votes and comments from the community
This way it's not going to work.
It makes sense about new features: it's ok to ask if users are interested in something new, something they don't have at the moment.
It's not ok to ask if users are interested in something that worked in previous models and it has been removed in current one.
Users take for granted that new model is something better than old one. At least equal.
If someone that creates development / marketing plans, thinks that this workflow is possible:
- Customer buys a new product
- Customer finds that something is missing
- Customer joins to polls and votes for that feature back
- Customer lives without the feature, and waits
- After an year, the feature is released and the customer is happy
is completely wrong.
At point 3, user is unhappy: the feature is needed now. From his or her point of view, it's like the device is broken.
Reality is: customer looks for another brand. Is this what Zyxel aims to?
Re: confused about access and trunk ports
Ok, when i have some time, i will make an clean configuration (now we use an template with many settings). to see if i have the issues still. If so, i will send the complete configuration.
Dpj
Re: out of production usg flex 200
If you browse sub-forums (one specific for "H series" and one "security ideas") you can find what others have discovered.
The latest I found:
The following (about FQDN object) has been fixed in November 2024, but I keep on thinking "and before?"
Who had been using these objects in previous version, how could do in the meantime?
I had a 200, I buyed a 200H, I was using FQDN… and until November 2024?
It's ok to continue development of a product after release, but it should be mainly for new features.
Basic ones should be completed before release.
As a user pointed out about missing routing protocols, when you buy a new car you don' check if it has axles, you take for granted that it has.
Re: Saving one click when launching firewall Remote Configurator
Hi @QuiteSmart,
We appreciate your input. Our product team will monitor the comments and votes on this idea for evaluation.
If anyone likes this idea, please feel free to leave your comment and give it a vote.
Re: WAX650S WPA3, older Macs with WPA2 dont want to connect
Hello, when you select WPA 3 or WPA2/WPA3 mode (mixed at the point), clients that do not support it connect in compatibility mode via WPA2, but older devices may not support it. Alternatively, create a separate SSID with WPA2 for older devices.
Re: AP Throttling?
I didn't mess it with it any further and just returned it to Amazon for a refund. I don't want a product that places default restrictions on anything with a way to turn it off.
Re: Device and config for port failover setup for two identical pcs controller
Hi,
I tried the Flex Link setup in Zyxel GS2200-10HP and every thing works fine.
Thanks for your great support.
Thanks bye,
Max
Re: Can’t seem to access network using LAN port on NWA130BE.
Hi @Andrew_em,
I have disabled smart steering, but please tell me if that is likely to cause issues?
I don't think there will be any issue.
Also - am I right that if I set my IoT SSID to NAT mode, then by default the devices connected to that SSID will not be able to see any LAN devices outside of that SSID, or do I still need to use Layer 2 filtering for that?
NAT mode allows devices under the same SSID and AP to see each other. And it doesn't support layer 2 isolation. For more details, you may check this FAQ:
[NEBULA] How to use NAT mode on AP? — Zyxel Community
Since you asked this question, may I know if your purpose is to prevent the IoT devices from finding each other?
Re: Register new unmanaged switches in portal.myzyxel.com
Hi @GiuseppeR,
If you're worried about the warranty, our RMA system will check your serial number for the warranty status. You don't need to register the device to have a warranty. "portal.myzyxel.com" is to assign licenses for on-premise/standalone devices, not for warranty service.