Jason
See how you've made an impact in Zyxel Community this
year!
https://bit.ly/Your2024Moments_Community
Zyxel VLANs not passing through
Hi,
(images attached for reference)
I am trying to configure a Zyxel to recieve/pass VLANs and it is not working.
All VLANs needed are declared.
Trunk port is #24, so all VLANs on that port ar TAGGED.
UNTAGGED VLANs are set-up as needed.
The trunk port does not comunicate with the next switch, VLANs are not passing through no matter is I tag or untag them on the trunk port.
I have tried communicating it with: HP switch, Ubiquity switch, Huawei switch and the main Mikrotik router on their trunks and nothing works. Even an untagged port does not communicate with another untagged port of any other switch.
All other switches and router have no issues passing VLANs between their trunks.
Another odd issue is when changing the management VLAN on the Zyxel, I absolutely loose communication with the device, it will only work with VLAN1 as the management interface. It does not matter if I connect un an untagged port of the VLAN I declared as the new management.
Is there some special VLAN non-standard configuration needed on Zyxel that I am unaware of?
(images attached for reference)
I am trying to configure a Zyxel to recieve/pass VLANs and it is not working.
All VLANs needed are declared.
Trunk port is #24, so all VLANs on that port ar TAGGED.
UNTAGGED VLANs are set-up as needed.
The trunk port does not comunicate with the next switch, VLANs are not passing through no matter is I tag or untag them on the trunk port.
I have tried communicating it with: HP switch, Ubiquity switch, Huawei switch and the main Mikrotik router on their trunks and nothing works. Even an untagged port does not communicate with another untagged port of any other switch.
All other switches and router have no issues passing VLANs between their trunks.
Another odd issue is when changing the management VLAN on the Zyxel, I absolutely loose communication with the device, it will only work with VLAN1 as the management interface. It does not matter if I connect un an untagged port of the VLAN I declared as the new management.
Is there some special VLAN non-standard configuration needed on Zyxel that I am unaware of?
0
All Replies
-
As a side comment: I have updated the switch to the latest fw (V2.60(ABTP.4) | 05/24/2021) and the issue persists.
0 -
Hi @wolkenrgh,
Welcome to Zyxel Community!
From your description, I summarize your current VLAN settings on ports with text:
Port 1-10 : VLAN 108, Untagged
Port 13 : VLAN 1, Untagged
Port 14, 21-22: VLAN 99, Untagged
Port 15 : VLAN 100, Untagged
Port 24 : VLAN 1, 96, 99, 100, 108, Tagged
You configure the ports with untagged, so I assume those ports are connecting to an end device which doesn't recognize VLAN tag.
Port 24 is configured as tagged for all VLANs, so I assume it is the uplink port of GS1900-24HP.
For those untagged ports, you will need to configure corresponding PVID. Ex: Port 1-10 is PVID 108.
BTW, I notice that VLAN 96 is only fixed on the uplink port 24, may I know if there is any special purpose?
Thank.0 -
Hi,
So, if I understand correctly: besides configuring the forbidden/excluded/tag/untag on the "Vlan Port" tab, I must also go to the "Port" tab and change the PVID to the vlan I with to be untag on the port? (as image below)
0 -
Jason
See how you've made an impact in Zyxel Community this year!
https://bit.ly/Your2024Moments_Community0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 151 Nebula Ideas
- 98 Nebula Status and Incidents
- 5.7K Security
- 271 USG FLEX H Series
- 274 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 42 Wireless Ideas
- 6.4K Consumer Product
- 250 Service & License
- 389 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 74 Security Highlight