From: Cameron Schaus <cam@schaus.ca>
To: bridge@linux-foundation.org
Subject: [Bridge] VLAN header accounting for packets leaving bridge
Date: Mon, 30 Jul 2007 10:48:40 -0600 [thread overview]
Message-ID: <46AE1668.9070804@schaus.ca> (raw)
I have been working on an ebtables module to insert an 802.1Q (VLAN)
tags into network packets leaving the bridge, via the POSTROUTING NAT
chain. To insert the VLAN tag the ethernet header size needs to be
increased by 4 bytes. I noticed that after increasing the size of the
ethernet header that the ethernet header in packets on the wire was
incorrect.
I think it is because the br_dev_queue_push_xmit function does not take
the VLAN header into account when it moves the data pointer in the skb
to the start of the ethernet header. The following patch corrects this.
Does this make sense to do? I plan to do more extensive testing passing
vlan and non-vlan traffic across a bridge, and will report back with the
results.
diff --git a/net/bridge/br_forward.c b/net/bridge/br_forward.c
index ada7f49..f30dc56 100644
--- a/net/bridge/br_forward.c
+++ b/net/bridge/br_forward.c
@@ -43,6 +43,8 @@ int br_dev_queue_push_xmit(struct sk_buff *skb)
kfree_skb(skb);
else {
skb_push(skb, ETH_HLEN);
+ if(skb->protocol == htons(ETH_P_8021Q))
+ skb_push(skb, VLAN_HLEN);
dev_queue_xmit(skb);
}
next reply other threads:[~2007-07-30 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 16:48 Cameron Schaus [this message]
2007-07-30 17:11 ` [Bridge] VLAN header accounting for packets leaving bridge Stephen Hemminger
2007-07-30 17:30 ` Ben Greear
2007-07-30 17:36 ` Cameron Schaus
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=46AE1668.9070804@schaus.ca \
--to=cam@schaus.ca \
--cc=bridge@linux-foundation.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