Bug in Untagged trunks when a Q is set?

[giannici]

I have the following VLAN settings:



In ports 1 and 2 there are two backhauls done with AirFibers. They works as trunk ports with VLAN 1 Untagged and everything else Tagged. AirFiber are reachable with VLAN 1. Everything works OK.

If I try to transform port 5 (VLAN 13) from U to Q, the AirFibers in the ports 1 and 2 (VLAN 1) are no longer reachable!



Why a change in a port in VLAN 13 changes the behaviour of a port in VLAN 1?

Thanks.

P.S. Firmware is 1.4.5.

[giannici]

I suspect that when the port 5 in VLAN 13 is changed from U to Q, then traffic of VLAN 1 in ports 1 and 2 is no longer passed Untagged but Tagged.

Is this true?
Is this a bug?
How can I avoid it?

Thanks.

[Eric Stern]

I've set this up in my lab by I am unable to duplicate the problem. I've tried to recreate it exactly, and several variations of it and it always works fine.

Maybe double check your configuration. Also if you can create a simple lab setup that recreates the problem I can look into it further.

[giannici]

I have shown the VLAN configuration. What else can have an influence?

The ONLY thing that I change is the U in Q in port 5. NOTHING ELSE.

The traffic in port 1 and 2 continue to flow correctly. In port 1 is attached a couple of AirFibers and then another switch with a specular configuration. Traffic here arrives correctly with both configuration, both VLAN1 and VLAN2. The ONLY thing that changes is that the AirFibers are no longer accessible (but continue to work). So the only explanation for me is that VLAN 1 is passed Tagged, so the AirFibers don't recognize it, but at the other side is it "seen" by the switch because it accept VLAN1 both Taggend and Untagged.

Do you see any other explanation?

If you want, I can send you the configuration file (tell me the email).

[Eric Stern]

You can send it to eric@netonix.com