From: Visham Ramsurrun <vishamr2000@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: netfilter Digest, Vol 9, Issue 12
Date: Thu, 7 Apr 2005 10:56:06 +0400 [thread overview]
Message-ID: <9927912d05040623567adba676@mail.gmail.com> (raw)
In-Reply-To: <425453ee.52656c03.5f63.ffff9ee0SMTPIN_ADDED@mx.gmail.com>
Hi to all,
I wanted to know abt the following:
do we always have to set up ebtables as a bridge or bridge router to
be able to use ebtables commands. Is it possible to have only a normal
firewall using ebtables (just like with iptables). It's just that
almost all examples I've come across talk abt building only bridges,
bridgefirewalls or bridge routers. I just need a confirmation of this.
Also, I want to make the packets move from the link layer right after
ebtables NAT PREROUTING to iptables. I have not set up my PC as a
bridge or bridge router.. I just want to set up a normal firewall that
makes use of both ebtables and iptables.
How do i go about it? do i use br-nf code?Does anyone have any sample
script using br-nf code? If yes. pls send it to me.
Thx in advance..
Best regards,
Visham Ramsurrun
parent reply other threads:[~2005-04-07 6:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <425453ee.52656c03.5f63.ffff9ee0SMTPIN_ADDED@mx.gmail.com>]
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=9927912d05040623567adba676@mail.gmail.com \
--to=vishamr2000@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