netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Bart De Schuymer <bdschuym@pandora.be>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH -next] netfilter: bridge: optionally set indev to vlan
Date: Thu, 5 Apr 2012 21:40:48 +0200	[thread overview]
Message-ID: <20120405194048.GA28425@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <4F7DD464.4020405@pandora.be>

Bart De Schuymer <bdschuym@pandora.be> wrote:
> > +static int brnf_pass_vlan_indev __read_mostly = 0;
> >   static int brnf_filter_pppoe_tagged __read_mostly = 0;
> >   #else
> >   #define brnf_call_iptables 1
> > @@ -503,6 +504,19 @@ bridged_dnat:
> >   	return 0;
> >   }
> 
> You should also provide a macro in case the proc file system isn't 
> enabled: currently it won't compile with your patch.

You're right, of course.
Thanks for spotting this, I'll fix it.

> >   	struct nf_bridge_info *nf_bridge = skb->nf_bridge;
> > -	struct net_device *realoutdev = bridge_parent(skb->dev);
> > +	struct net_device *realoutdev = brnf_get_logical_dev(skb, out);
> I think it's best to keep the bridge_parent as output device in the 
> FOWARD and POSTROUTING chain: only change the input device. Do you have 
> a reason for changing the output device?

Consistency.  (locally generated packet is '-o br0.X, forwarded br0).
OTOH, we could call it a feature ;-)

I have no special requirements for the outdev; we can keep it as-is.

Regards,
Florian

      reply	other threads:[~2012-04-05 19:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 19:57 [PATCH -next] netfilter: bridge: optionally set indev to vlan Florian Westphal
2012-04-05  1:09 ` Pablo Neira Ayuso
2012-04-05  7:30   ` Florian Westphal
2012-04-05 11:09     ` Pablo Neira Ayuso
2012-04-05 17:20 ` Bart De Schuymer
2012-04-05 19:40   ` Florian Westphal [this message]

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=20120405194048.GA28425@Chamillionaire.breakpoint.cc \
    --to=fw@strlen.de \
    --cc=bdschuym@pandora.be \
    --cc=netfilter-devel@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).