All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dawid Ciezarkiewicz <dpc@asn.pl>
To: netdev@vger.kernel.org
Subject: Re: [PATCH][ebtables][vlan] ebt_vlan_t target
Date: Thu, 6 Jul 2006 13:34:40 +0200	[thread overview]
Message-ID: <200607061334.41012.dpc@asn.pl> (raw)
In-Reply-To: <200607061315.17109.netdev@axxeo.de>

On Thursday, 6 July 2006 13:15, Ingo Oeser wrote:
> First of all: 
> 	You should not implemented "--vlan-target". 
> 	Always return EBT_CONTINUE. That saves a lot of (duplicated) code
> 	(you can express the same using some more rules) while keeping 
> 	the same flexibility level. Rules for transforming/mangling 
> 	and decision rules should be seperate.

OK. I've been doing everything looking how ebt_mark.c is written. I thought about dropping 
it (iptables has nothing like this and works), but I havent't been sure if I should.

> > diff -Nur linux-2.6.17.orig/net/bridge/netfilter/Kconfig 
> > linux-2.6.17/net/bridge/netfilter/Kconfig
> > --- linux-2.6.17.orig/net/bridge/netfilter/Kconfig	2006-06-18 
> > 03:49:35.000000000 +0200
> > +++ linux-2.6.17/net/bridge/netfilter/Kconfig	2006-06-28 20:48:27.000000000 
> > +0200
> > @@ -165,6 +165,15 @@
> > 
> >  	  To compile it as a module, choose M here.  If unsure, say N.
> > 
> > +config BRIDGE_EBT_VLAN_T
> > +	tristate "ebt: vlan target support"
> > +	depends on BRIDGE_NF_EBTABLES
> > +	help
> > +	  This option adds the vlan target.
> > +
> > +	  To compile it as a module, choose M here.  If unsure, say N.
> > +
> > +
> 
> Please put your nice explanations "to change vlan ids in fly" from your email here.

OK.

> I cannot comment on rest of the patch and hope other people will do :-)

I hope they do, too. Thanks. :)

      reply	other threads:[~2006-07-06 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05 19:49 [PATCH][ebtables][vlan] ebt_vlan_t target Dawid Ciężarkiewicz
2006-07-06 11:15 ` Ingo Oeser
2006-07-06 11:34   ` Dawid Ciezarkiewicz [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=200607061334.41012.dpc@asn.pl \
    --to=dpc@asn.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.