From: Mohamed Eldesoky <eldesoky.lists@gmail.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: physdev match
Date: Wed, 22 Sep 2004 14:44:42 +0300 [thread overview]
Message-ID: <1403218a04092204446c0f798d@mail.gmail.com> (raw)
In-Reply-To: <200409221217.11787.gdh@acentral.co.uk>
Well, the patch had some failures.
I saw it has the physdev in the patch !!
patching file include/linux/netfilter_ipv4/ipt_physdev.h
Will this patch add the physdev match ??
I am thinking about going with a stock kernel !!
On Wed, 22 Sep 2004 12:17:11 +0100, Gavin Hamill <gdh@acentral.co.uk> wrote:
> On Wednesday 22 September 2004 12:01, Mohamed Eldesoky wrote:
> > ummm
> > I was looking at the possibilities.
> > Also, what if I don't want to use ebtables !!
>
> 'ebtables' is just a round-all term for what became of the 'bridge
> firewalling' code. You don't need to use the 'ebtables' binary at all if all
> you want to do is apply firewall rules on a bridged system.
>
> However, it remains to be seen whether the ebtables code would even patch
> successfully on an RHEL kernel source, plus if using a 'Real' Red Hat kernel
> is important to you, then you'll obviously not want to recompile at all.
>
> Unless RHEL already contains the support (look for 'Bridge firewalling
> registered' in the 'dmesg' output from boot time) then you're a bit stuck.
>
> Of course, all this talk of ebtables is now off topic =)
>
> Cheers,
> Gavin.
>
>
--
Mohamed Eldesoky
www.eldesoky.net
RHCE
next prev parent reply other threads:[~2004-09-22 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 10:53 physdev match Mohamed Eldesoky
2004-09-22 10:58 ` Gavin Hamill
2004-09-22 11:01 ` Mohamed Eldesoky
2004-09-22 11:17 ` Gavin Hamill
2004-09-22 11:44 ` Mohamed Eldesoky [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-23 14:03 Mohamed Eldesoky
2004-09-23 14:21 ` Aleksandar Milivojevic
2004-09-23 14:47 ` Mohamed Eldesoky
2004-09-27 7:52 ` Mohamed Eldesoky
2005-02-25 1:06 Axel Christiansen
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=1403218a04092204446c0f798d@mail.gmail.com \
--to=eldesoky.lists@gmail.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox