NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ckruijntjens
Mar 26, 2026Tutor
GS308EPP new firmware bug
Hi all, I updated my firmware from 2.0.0.5 to 2.0.0.11 on 2 of 4 switches. On both switches i can not acces the web ui, And the switch is not responding on ping.... Anyone else having the sam...
ckruijntjens
Mar 26, 2026Tutor
Hi,
Thanks for your reply. Well i think it has to do something with the vlan config. I resett one switch and it came back online. I use vlan advance 802.1Q
The default vlan 0 i did not mess with.
I use vlan ids 10,11,20,40,50,60,100
The switch has a static ip adress.
You Menton that in the new firmware the management uses a vlan. What vlan does it use in the new firmware?
schumaku
Mar 27, 2026Guru - Experienced User
ckruijntjens wrote:The default vlan 0 i did not mess with.
The switch WebUI should not allow VLAN 0. The VID 0 is designated in Dot1q for special use only, specifically for adding a Priority Code Point (PCP) for signalling a class of traffic towards the next bridge.
ckruijntjens wrote:You mention that in the new firmware the management uses a vlan. What vlan does it use in the new firmware?
The management VLAN is - according to the Web UI at least - not predefined. It can be set in the advanced VLAN mode controls.
This does ring a bell to me: Never had the VID 1 undefined on my playground switches here - I was never involved in any kind of Beta testing the last years, or specifically on these GS108EP, GS108EPP, GS308EP, GS308EPP switches, too.
Might be Netgear does have a default management VID 0 (unlikely), or implicitly using VID 1 - this is what switch makers are using on models with Spanning Tree Protocol (STP) with the standards defined Common Spanning Tree (CST) that only assumes one spanning tree instance for the entire bridged network, regardless of the number of VLANs.
So "what-if" there is a VLAN config like yours not including VID 1?
Might happen they implicitly using VLAN 1 in the default value for the management VLAN as introduced with 2.0.0.10/.11 firmware - and you had no VID 1 in the config, so the complete IP stack became inaccessible.
Maybe MarcinS has some further ideas what went wrong, starting from a random existing VLAN config, not covering VID 1, before the update. Probably worth a remark in the release notes for defining a working and accessible VLAN 1 before deploying the update?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!