QinQ 802.1Q I think I am not understanding it

[merrittr]

Hi All

I have set up one port (packets ingress) at the dot1Q tunnel all the packets are test generated so I know they will all egress via another port set up as the trunk port  so what I am seeing is all the packets captured via tcpdump on the ingress port have a vlan tag 1-4095 (I generate 4095 pkts all with a vlan tag 1-4095 in order. now on the egress port I have another computer tcpdumping that interface and i see the same 1-4095 vlan tags even though the qinq is supposed to be additionally taging them into vlan 20 ... am I missing something? 

[Peter Paluch]

Hi,

Would you mind posting the complete configuration of the ingress and egress port?

Best regards,
Peter

[merrittr]

ok Ill post it 

its from that non cisco switch hope thats ok cli commands are very similar ...I am waiting on that 3550 which I belives needs some licensing to run QinQ

Ill post the config in a sec just reseting it

[merrittr]

ok here is the config

this is not a CISCO config , so if you could just outline what i would need to do on a CISCO 3550 command wise to QinQ , double tag, all tagged packets coming in in the dot1q port so that they have 2 vlanid inner and outer (outer ==333) when they leave the egress port which is set up as a trunk port, and all untagged packet will just get the 1 tag 333 as they leave the trunk port

[merrittr]

Aaaaagghhh please disregard this post my PIC in win7 was stripping the outer tag for me

a chance reboot into ubuntu reveals the truth on the qinq.

Sorry Paul

[Peter Paluch · Accepted solution]

Hi,

Oh... Very well, then.

To anyone intending to do some serious network experiments: Avoid Windows, use Linux instead.

Best regards,
Peter

[merrittr]

Yes I heartily agree ..I booted into my win7 image to fill in my time sheet (its a windows forms app) after doing so I thought id just continue on doing my testing work .... I marked your above statement as a correct anwswer

[Peter Paluch]

Hello,

The configuration of the 3550 would be similar to this:

vlan 333
 name Customer
!
interface FastEthernet0/1
 description => Ingress Dot1Q Tunnel Port Toward a Customer <=
 switchport mode dot1q-tunnel
 switchport access vlan 333
!
interface FastEthernet0/2
 description => Egress Trunk <=
 switchport trunk encapsulation dot1q
 switchport mode trunk

Best regards,
Peter