Watershed

Hi guys Sorry I was out a few days due to public holidays and long weekend. I'll get back to the lab later today and we can continue via PM. Thanks.

Well, the first thing I did try when I first installed the switch, was only to check the box vlan trunking on port 25/26, which did not work. Now, I removed all VLAN config and only kept vlan trunking for these 2 ports and exclude them also from vlan 1 as you can see below. This is also not working.

Actually, I want to forward all packets without touching the VLAN tag at all if possible. I understand the configuration I was showing you might not be logical due to the fact I wasn't sure how the vlan tag was handled. The ingress packets when they reach the switch are all VLAN tagged and I want the egress packets to keep…

Thanks Zyxel_Lucious It's more clear what it does. Ingress packets tagged with VLAN 2 can ONLY communicate between port 25 & 26, and will be tagged-out from port 25 & 26. That's my problem. I don't want the packets to be tagged out from ports 25/26. I need to find a way to re-tag the egress packet so they keep the VLAN…

Now, for the time being it is crucial that vlan2 traffic from/to R1 and R2 makes it through. On R1, the config is this: interface vlan 2 encapsulation dot1q trunk 1 ip address XXX.XXX.XXX.XXX 255.255.255.240 end interface vlan 4 encapsulation dot1q trunk 1 ip address XXX.XXX.XXX.XXX 255.255.255.224 interface vlan range…

Hello Zyxel_Lucious When you mention "unknown VLAN groups to pass through the Switch (with tagged-out)", do you mean by there untagged traffic ? What if all the traffic coming from the trunk ports on R1 and R2 is tagged ?

Hi Thank you for the quick response. We are in lab environment. It's only for troubleshooting and mirroring purpose. Fiber taps are unfortunately lot more expensive. I tried many config thall failed. First thing was to indeed to enable trunking on the two 10GE fiber ports connected to R1 and R2 (I verified the link state…