GS1xxE and their PoE equivalents. Getting them an IP using DHCP on a specific vlan.

beardytechie  >  ultimately I will probably end up selling the GS108E and buy a different brand.

Unqualified judgment... It's not about a different brand (I can give you pointers to other brand switches with the same design and limitaiton). If you don't like this design, you must buy at least some GSxxxT (Smart Managed Pro) instead of the GSxxxE (Smart Managed Plus) - no need to change the brand.

Where are the real risks? The switch is a non-managed core, the controller for configuring (not managing!) a limited functionality switch core, so it could be abused for destroying your network config. The controller has as-is no access to the data flowing on your network. If you want to draw it very black: Granted, the very bad guys could extend or replace the controller code, installing malicious code, the same thing could happen if the controller would listen to the configured VLAN only. Jalla jalla ...

I have a very simple network at home with three vlans: a trusted network, a guest network and a test network. None of these are vlan1. My main switch is a GS724T, placed in the downstairs cupboard where my broadband comes in, with a firewall, separate wifi AP, a small server and cat5e to around the house. The guest network is used for guests, but also untrusted devices like cheap chinese IP cctv cameras and the like.

I just bought a GS108E as perfect for me needs, a simple but good quality switch ideal for extending my network into a home office space, so I set it up with the same vlans with a .1q port to link back to the "core" switch. And I quickly spotted the problem discussed here:
https://community.netgear.com/t5/Smart-Plus-and-Smart-Pro-Managed/GS108Ev3-Cannot-set-VLAN-for-management-interface/td-p/971240

that sent me here.

I want to be able to set my GS108E to have its management interface on any vlan. This seems to me to be a fairly trivial thing to want, sorry. It appears there are work-rounds to solve this, but ultimately I will probably end up selling the GS108E and buy a different brand. I definitely do NOT want the chance of having my switch visible on the guest network!

Same here - the management interface on the Smart Managed Plus does the DHCP handshake on any VLAN. Granted, we could use fixed IP addresses, this will leave other vectors (over different VLANs) still open.

bradleyv nice pleeeeeease here again, too!

While is it disgusting that this item is just sitting here, I would like to add this advice to others trying to use these switches:

Don't use these switches.  This problem will never be fixed.  After messing with the switch for a while, it is obvious this is a non-VLAN switch design that someone hacked basic VLAN support into.  Perhaps they got a new revision of the chip they use and it supported VLANs and they had some intern hack it together.  But it isn't a VLAN-ready switch, because significant parts of it are not VLAN-aware, like the administration system for example.    I returned mine as "doesn't support what it advertises" because these will never be worth my time (nor yours.)

You can get great results with GS110TP (which is a real VLAN switch) and GS108T hanging off of them where you need a second tier VLAN switch.

Trying to use the GS1xxE in a VLAN deployment is just wasting your time.

Same question here. Need a solution to this, or I'll need to switch to TP-Link instead. They seem to have a switch that does this (and much more) in TL-SG2210P. Slightly higher price, but still closer to the GS108PEv3 (which I currently have two of (unfortunately)) than that of Cisco/HPE etc.

This has been sitting here for quite some time now. Any update please?

Hi, I've the same request for GS108Ev2 and GS116Ev2. Best regards

It's almost been 2 years now.

These are the switches I buy most, not only for me but also for family and some small workplace installations.

This is the only painful  point in these switches. If you use DHCP the switch get's it's IP from the vlan that delivers it the fastest. Which is a huge problem for me since one of my vlans has an ISP cable modem on it. you can see the security issues from having a switch that requests and gets a WAN IP I bet...

If a fixed IP is used that fixed ip is approachable from any VLAN that has ip's in that range!! This is also a major security issue.

As it is now, I have to use a fixed class C public IP for configuration and change it to an unused subnet after use.

I'm not even sure my ISP drops class C public ip packets in it's first hop routers. If it doesn't any smartass that manually puts in a class c IP that's in the range I leave my switch in can start hacking it.

Please fix this. Please allow us to specify the VLAN the switch uses for configuration instead of using all VLANs.

This is not a detail. This is a major security flaw. Vlans are supposed to be isolated.

Thank you for taking the time to read this.

Yeah, how are VLANs managed on these switches? How comes the switches can get DHCP leases from any VLAN???? This cannot be by design, this is a designed fault! It's an improper implementation! Please fix it and introduce the management VLAN concept into the firmware! And please make sure the switch is not mixing up traffic between vlans! I got here investigating why I get DHCP leases from VLAN 2 delivered on VLAN 1, now I suspect it's just a broken firmware and product line!!!