Project

General

Profile

Actions
Copy link

Feature #814

closed

QinQ tag flow support

Added by Peter Manev almost 11 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Victor Julien
Target version:
2.0rc1
Effort:
Difficulty:
Label:

Description

A proper QinQ(including decoding) tag flow support - is very important on high traffic end ISP carrier lines.

QinQ pcaps privately available if needed.

Actions
Copy link
 #1

Updated by Victor Julien over 10 years ago

  • Target version set to TBD
Actions
Copy link
 #2

Updated by Victor Julien about 10 years ago

Both vlan id's are used in flows right now. Does that address the issue?

Actions
Copy link
 #3

Updated by Peter Manev about 10 years ago

I am not sure I understand - we have QinQ support right now in git? Example a "vlan tagged vlan flow"?

Actions
Copy link
 #4

Updated by Victor Julien about 10 years ago

Both vlan id's are used to keep flows separate from each other.

Actions
Copy link
 #5

Updated by Peter Manev about 10 years ago

I will run some tests and confirm.

Actions
Copy link
 #6

Updated by Peter Manev about 10 years ago

vlan id's are not properly used to keep flows separate as of 2.0dev (rev 7726cec).
pcaps shared privately.

Actions
Copy link
 #7

Updated by Victor Julien about 10 years ago

  • Status changed from New to Closed
  • Assignee set to Victor Julien
  • Target version changed from TBD to 2.0rc1
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF