From: David Miller <davem@davemloft.net>
To: greearb@candelatech.com
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org,
j.borsboom@erasmusmc.nl
Subject: Re: [PATCH] allow VLAN interface on top of bridge interface
Date: Thu, 12 Apr 2007 15:01:05 -0700 (PDT) [thread overview]
Message-ID: <20070412.150105.45898545.davem@davemloft.net> (raw)
In-Reply-To: <461EA863.9020702@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Thu, 12 Apr 2007 14:45:07 -0700
> Andrew Morton wrote:
> >
> > Begin forwarded message:
> >
> > Date: Thu, 12 Apr 2007 21:50:00 +0200 (CEST)
> > From: Jerome Borsboom <j.borsboom@erasmusmc.nl>
> > To: linux-kernel@vger.kernel.org
> > Subject: [PATCH] allow VLAN interface on top of bridge interface
> >
> >
> > When a VLAN interface is created on top of a bridge interface and
> > netfilter is enabled to see the bridged packets, the packets can be
> > corrupted when passing through the netfilter code. This is caused by the
> > VLAN driver not setting the 'protocol' and 'nh' members of the sk_buff
> > structure. In general, this is no problem as the VLAN interface is mostly
> > connected to a physical ethernet interface which does not use the
> > 'protocol' and 'nh' members. For a bridge interface, however, these
> > members do matter.
>
> Why only do this inside that if clause? I can see only setting
> nh.raw in that clause, but it seems like the protocol should be set
> regardless.
Because outside the if clause we are making the packet look
like a normal ethernet frame to the rest of the stack, and
only adding the VLAN tag at the very last moment in
->hard_start_xmit().
next prev parent reply other threads:[~2007-04-12 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 21:34 Fw: [PATCH] allow VLAN interface on top of bridge interface Andrew Morton
2007-04-12 21:45 ` Ben Greear
2007-04-12 22:01 ` David Miller [this message]
2007-04-12 21:59 ` David Miller
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=20070412.150105.45898545.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=greearb@candelatech.com \
--cc=j.borsboom@erasmusmc.nl \
--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;
as well as URLs for NNTP newsgroup(s).