All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Bridge Transparent Proxy
Date: Tue, 22 May 2007 13:30:28 -0500	[thread overview]
Message-ID: <465336C4.5060600@riverviewtech.net> (raw)
In-Reply-To: <C2787F66.1C272%robert@leblancnet.us>

On 05/22/07 12:07, Robert LeBlanc wrote:
> Thanks, I wasn't aware of this option as I haven't done much with 
> bridging since I had lots of trouble with trying to bridge and NAT on 
> the same network (use allow the same physical network after my linux 
> gateway to carry my public network and the NATed private network). I 
> will have to look into it again, this option may have been a cause of 
> some of my issues.

*nod*  Bridging Routers can be interesting critters to work with.

Brouters are usually used to allow globally routable systems IP 
addresses to be used in front of and behind a firewall (of sorts).  I.e. 
a small block of IP addresses that the brouter uses for its external IP 
address as well as internal public servers use IP addresses from to be 
directly accessible from the net with out any sort of NAT.

(INet) --- (Cable / DSL modem) --- (BRouter) --- (Server(s)
                                              --- (Workstation(s))

To pull this off usually you bridge the internal and external NICs 
together and multi home the bridge interface for your internal and 
external IP addresses.  I.e. bri0 = A.B.C.D and bri0:1 = 192.168.144.254 
are your IP addresses.

In this case, you only bridge traffic to / from the A.B.C.x network and 
route any thing else.  You can even serve DHCP on the internal LAN with 
out a problem.

In this scenario, you can use either EBTables or IPTables to do your 
filtering.  The only thing you need to remember is to not bridge (DROP 
in the brouting table / BROUTE chain) any internal traffic and force it 
to be routed.  Another way to say it is to only bridge traffic to / from 
your globally routable IP addresses.  Remember that you will need to 
pass some ARP traffic too.




Grant. . . .


  reply	other threads:[~2007-05-22 18:30 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
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 [this message]
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=465336C4.5060600@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=gtaylor+reply@riverviewtech.net \
    --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 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.