From: "Peter Palúch" <Peter.Paluch@fri.uniza.sk>
To: netdev@vger.kernel.org
Subject: [RFC] VLAN aux info for AF_PACKET available only with ETH_P_ALL
Date: Thu, 14 Apr 2016 17:17:34 +0200 [thread overview]
Message-ID: <570FB48E.2060108@fri.uniza.sk> (raw)
Greetings,
When using AF_PACKET sockets with PACKET_AUXDATA socket option to access
the VLAN TCI information of received frames, I have noticed that the
VLAN information in struct tpacket_auxdata, namely,
- tp_vlan_tci
- tp_vlan_tpid
- TP_STATUS_VLAN_VALID and TP_STATUS_VLAN_TPID_VALID flags
is filled in only when the socket is bound to htons (ETH_P_ALL). If the
socket is bound to any specific protocol, the VLAN information fields in
struct tpacket_auxdata are set to 0 even if the datagram of the specific
protocol was received in an 802.1Q-tagged frame.
As the VLAN tag is being stripped off the frame soon in the receive
path, using PACKET_AUXDATA is the only way for an application over an
AF_PACKET socket to know what VLAN did a particular frame arrive in;
yet, the current behavior forces the application to listen to all
received traffic to get the actual VLAN info.
Is this behavior intentional, or is this lack of VLAN info a bug? I am
running vanilla Linux kernel v4.4.6.
Thanks!
Best regards,
Peter
reply other threads:[~2016-04-14 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570FB48E.2060108@fri.uniza.sk \
--to=peter.paluch@fri.uniza.sk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox