NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AlmostATech
Jun 25, 2023Aspirant
M4300-24x
VLANs not going across fiber connection
When I tag them, it becomes untagged even though others are tagged.
Also tried a Trunk and that did not work
3 Replies
Afraid, the crystal ball is not available here.
Provide much more information what you had tried to configure, being from screenshots or from CLI example.
Start with the firmware version, the SFP module versions, the fiber technology, wavelength, ...
- AlmostATechAspirant
I have a single-mode fiber between two buildings connected over the SFP ports. M4300-24x24 port 22 and M4300-52G port 51
I have setup VLANs, 220, 230, 240, 260, 270 on both switches. I tag port 51 with the VLANs no issue, when I tag port 22 with the VLANs it switches it to untagged.
In short, just trying to pass tagged traffic across the fiber.
AlmostATech wrote:
I have a single-mode fiber between two buildings connected over the SFP ports. M4300-24x24 port 22 and M4300-52G port 51
Tell us a little bit more about the set-up. Firmware in place, SFP modules involved, ...
AlmostATech wrote:
I have setup VLANs, 220, 230, 240, 260, 270 on both switches. I tag port 51 with the VLANs no issue, when I tag port 22 with the VLANs it switches it to untagged.
The device Web UI does change the config from trunk to an access port probably? A Stack config in place? Using the IT UI or the AV UI, or missed to apply/save the config changes? Reads to me like there is anther management entity in this set-up, like an active Netgear Engage Controller software for example.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!