From: Jon Tim <lcguy229@yahoo.com>
To: netfilter@lists.netfilter.org
Subject: Re: Bridge Transparent Proxy
Date: Tue, 22 May 2007 22:56:55 -0700 (PDT) [thread overview]
Message-ID: <390179.89889.qm@web38509.mail.mud.yahoo.com> (raw)
In-Reply-To: <465314F4.1060007@plouf.fr.eu.org>
Hello,
Many thanks for all reply to my Bridge Transparent
Proxy post.
But, please let me know more how to enable "netfilter
Bridge Support" in kernel. Can I add a linke
CONFIG_BRIDGE_NETFILTER=y" in /etc/sysctl.conf ??
And, in the second iptables command what is physdev
and physdev-in?? Does this mean physdev= eth0 and
physdev-in = eth1??
Sorry for my quetion. I am newbie in iptables and
don't understand very well?
My another qutesion is, do I need to use NAT command
in iptables? As I have all public address and why I
have to use NAT to redirect?
Jon.
--- Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
wrote:
> Hello,
>
> Robert LeBlanc a écrit :
> > You will need to look at ebtables. Bridging will
> bypass iptables.
>
> Bridged IPv4 packets traverse the iptables chains if
> the kernel was
> compiled with Netfilter bridge support
> (CONFIG_BRIDGE_NETFILTER=y). It
> allows finer filtering than ebtables, for instance
> accepting only
> outgoing HTTP/HTTPS connections and related ICMP
> messages in both
> directions thanks to connection tracking, e.g. :
>
> iptables -A FORWARD -m state --state
> ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -m physdev --physdev-in eth1 -m
> state --state NEW \
> -p tcp -m multiport --dports 80,443 -j ACCEPT
>
>
____________________________________________________________________________________Luggage? GPS? Comic books?
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz
next prev parent reply other threads:[~2007-05-23 5:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 14:28 Bridge Transparent Proxy Jon Tim
2007-05-22 14:35 ` Robert LeBlanc
2007-05-22 16:06 ` Pascal Hambourg
2007-05-23 5:56 ` Jon Tim [this message]
2007-05-23 13:39 ` Gáspár Lajos
2007-05-22 16:09 ` Grant Taylor
2007-05-22 17:07 ` Robert LeBlanc
2007-05-22 18:30 ` Grant Taylor
2007-05-22 18:36 ` Pascal Hambourg
2007-05-22 18:51 ` Grant Taylor
2007-05-22 19:26 ` NAT addresses - RFC or tradition? Paul Blondé
2007-05-22 19:46 ` Andre Guimarães
2007-05-22 19:57 ` Tim Evans
2007-05-22 20:02 ` Marius-Iulian Corici
2007-06-18 17:27 ` R. DuFresne
2007-06-18 17:25 ` R. DuFresne
2007-05-22 20:02 ` Leonardo Rodrigues Magalhães
2007-05-22 20:22 ` Grant Taylor
2007-05-22 21:39 ` Bridge Transparent Proxy Petr Pisar
2007-05-22 22:07 ` Pascal Hambourg
2007-05-23 0:25 ` Grant Taylor
2007-05-22 18:39 ` Robert LeBlanc
-- strict thread matches above, loose matches on Subject: below --
2004-08-24 12:28 bridge + transparent proxy Jason Opperisano
2004-08-24 13:13 ` ArioS
2004-08-24 5:11 Multiple IPSEC VPNs through a firewall based on 2.4.2X kernel Roksana Boreli
2004-08-24 5:46 ` Ming-Ching Tiew
2004-08-24 7:32 ` Payal Rathod
2004-08-24 7:50 ` Ming-Ching Tiew
2004-08-24 8:53 ` bridge + transparent proxy ArioS
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=390179.89889.qm@web38509.mail.mud.yahoo.com \
--to=lcguy229@yahoo.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