All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Amin Azez <azez@ufomechanic.net>
Cc: l7-filter-developers@lists.sourceforge.net,
	netfilter-devel@lists.netfilter.org
Subject: Re: lots of oopses
Date: Fri, 18 Aug 2006 20:23:29 +0200	[thread overview]
Message-ID: <44E605A1.5000007@trash.net> (raw)
In-Reply-To: <44E56D39.50806@ufomechanic.net>

Amin Azez wrote:
> Patrick McHardy wrote:
> 
>> BTW, what is ipt_vlan?
>>   
> 
> I think I posted it here a year ago, but I'll do so again if you want it.
> It matches on vlan-id.
> 
> It was said that strictly this is a layer 2 thing and not for iptables;
> I find it useful though;-
> which iptables rules should be applied may depend on vlan stuff, and
> sometimes it seems like there isn't enough mark to go around...
> 
> I like the iptables/ebtables seperation but sometimes it seems like they
> should be able to share each-others matches, like one big happy table
> with a few extra points of inspection. Anyway...

Agreed. It should be possible for ebtables to use all iptables matches
looking only at packet data, but not necessarily the other way around.
Unfortunately ebtables is in large parts a copy of iptables, with just
enough differences to prevent it from using x_tables.

  reply	other threads:[~2006-08-18 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 16:28 lots of oopses Amin Azez
2006-08-17 17:04 ` Patrick McHardy
2006-08-18  7:33   ` Amin Azez
2006-08-18 18:23     ` Patrick McHardy [this message]
     [not found]       ` <44E6C247.9010704@ufomechanic.net>
2006-08-21 23:09         ` Patrick McHardy
2006-08-18 13:55   ` ipt_vlan Amin Azez
2006-08-18 18:18     ` ipt_vlan Patrick McHardy

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=44E605A1.5000007@trash.net \
    --to=kaber@trash.net \
    --cc=azez@ufomechanic.net \
    --cc=l7-filter-developers@lists.sourceforge.net \
    --cc=netfilter-devel@lists.netfilter.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.