NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GS308E Access Management Site
Hello,
I currently used two GS305e at different locations at home. Between the switches I used a trunc-connection with VLAN 101 (192.168.2.0/24) and VLAN 200 (192.168.10.0/24) on Port 5. Port 5 is set as VLAN-Member 101 (tagged) and 200 (tagged), to prevent untagged traffic on this Ports I also set VLAN 2 only to this Ports (tagged) and PVID also to VLAN 2. All other Ports are untagged on VLAN 101 or VLAN 200.
At this config I can manage both switchs from devices they are connectet to any other port (untagged VLAN 101) at any switch. Now I swaped one of the GS305e to a GS308e, I setting up the same VLAN/Port configuration, but I can manage the GS308e only from local connected devices now.
Some tests later it seems that incomming management traffic on tagged Port, from GS308e respond as untagged traffic. If I set the PVID on correspondending Port at GS305e from 2 to 101, its allows manage the GS308e over devices they connected to GS305e.
This behavior cannot be correct.
The switchs are config with static IP (192.168.2.132 ; .133).
Sascha
16 Replies
- It's not the first time reading about this suspect button the GS308E and probably the similar EP and EPP variants, while the GS305E work as expected.
For completeness, please add the exact model and the current firmware installed on the two switch models.
Will try to create some awareness with Netgear again. In case the switches are newer, also create a support ticket please, too. Hello,
short update:
My case in processing since 4 weeks. A lot of posts later the supporter has not yet managed to configure the switches as I specified to reproduce the problem. 🙄
I do not give up 🙂
Sascha
Final State:
from Support ...
"We have received an update from the Engineering team, who could reproduce the issue and find the root cause.
The root cause is GS308E chip can't reply to ARP with the tag however, GS305E can send the reply to ARP with the tag.""It is a Hardware limitation. It cannot be fixed by software updates." ☹️
Workarround should be use PVID (@GS305E) to retagging packets from GS308E, but it's no solution for direct connections from other hardware with 802.1Q.
Ticket is closed.
That is beyond ridiculous... So they're saying that the chip supports tagging all other traffic, but is unable to tag its own? And what about the second issue when the replies are broadcast on all ports? Is it another "hardware limitation"? I think I'm done with Netgear...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
