Page 1 of 1
Passing Q-in-Q
Posted: Thu May 07, 2015 4:56 pm
by keefe007
Has anyone tried passing q-in-q(double tagged) frames through a Netonix switch? We replaced another switch with a Netonix and now it seems that double-tagged frames wont pass.
Re: Passing Q-in-Q
Posted: Fri May 08, 2015 4:12 pm
by mike99
Look at road map, QinQ is suppose to be introduced in current dev firmware.
Re: Passing Q-in-Q
Posted: Sun May 10, 2015 9:41 am
by adairw
I said this on the wispa list already, but shouldn't it pass the traffic even if it can't deal with it, so long as the mtu is big enough?
Re: Passing Q-in-Q
Posted: Sun May 10, 2015 10:40 am
by sirhc
I will discuss this with Eric
Re: Passing Q-in-Q
Posted: Sun May 10, 2015 12:10 pm
by sirhc
So I talked Eric into making me a v1.2.1 today that will allow double tagged frames so it will behave like the ToughSwitch in this situation and just pass the frames and not filter them.
Who wants to test it for me and I will email you a copy.
v1.3.0 will support QinQ which is what Eric was working on before I disturbed him.
Some other neat features of v1.3.0
Radius Authentication with fall back to static credentials
Fix Port(s) Mirror to IP
Last known IP in MAC table
Change VLAN Trunk Port (allow all VLANs) to an allowed VLANs list
Add ignore logging for IP monitoring software under Device/Config Tab
QinQ VLANs
IGMP Snooping
QOS
IPERF
Option to require password on console
Add optional second NTP source
Re: Passing Q-in-Q
Posted: Mon May 11, 2015 12:55 pm
by keefe007
What did this change do exactly?
Adam is right, changing the MTU from 1518 to 1522 allowed Q-in-Q frames to be passed without firmware 1.2.1.
Keefe