Skip to content
This repository has been archived by the owner on Nov 4, 2022. It is now read-only.

VLAN tags #211

Open
hosom opened this issue Aug 21, 2019 · 3 comments
Open

VLAN tags #211

hosom opened this issue Aug 21, 2019 · 3 comments

Comments

@hosom
Copy link
Contributor

hosom commented Aug 21, 2019

When Stenographer records traffic, it appears to strip the outermost VLAN tag. I don't know if I would consider this a bug, but I definitely wasn't expecting this. I am aware of several environments that use QinQ tagging to signal which taps traffic is coming from and it would be convenient to make this a configurable setting.

@aeppert
Copy link
Collaborator

aeppert commented Sep 7, 2019

When Stenographer records traffic, it appears to strip the outermost VLAN tag. I don't know if I would consider this a bug, but I definitely wasn't expecting this. I am aware of several environments that use QinQ tagging to signal which taps traffic is coming from and it would be convenient to make this a configurable setting.

I am assuming this is due to Stenographer using AF_PACKET. The VLAN tags are stripped at a lower layer and, unfortunately with my work on a few other things using AF_PACKET, it isn’t trivial to put them back together. It is possible, but with a decent performance impact as they have to be, per packet, re-applied. It is, perhaps, possible and may make sense to maintain a small state-store that could be built overtime and thus the performance penalties would smooth over the running time of stenographer.

@capton586
Copy link

Is there any way to avoid this issue?

@satta
Copy link
Contributor

satta commented Sep 17, 2021

Maybe it could help disabling the NIC's VLAN offloading so the VLAN tags make it into AF_PACKET?

sudo ethtool -K <interface> rxvlan off 

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants