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 19:25:56 -0500	[thread overview]
Message-ID: <46538A14.608@riverviewtech.net> (raw)
In-Reply-To: <465369AF.2060107@plouf.fr.eu.org>

On 5/22/2007 5:07 PM, Pascal Hambourg wrote:
> Now I see. But wouldn't it be worth subnetting A.B.C.x ?

If you have the option, yes.  However, that is seldom an option, even 
less so with out the providers support.

Consider a cable modem / DSL install where you get 4 IP addresses, 
having nothing to do with subnets.  I.e. .62, .63, .64, and .65.  You 
can not do any viable subnetting with this.

Even if you can viably do subnetting, you have to have the provider 
configure the remaining IPs available via the IP facing them.

It has been my experience that it is much easier to do BRouting in these 
cases.

> Do you mean that ARP proxy would not be a good way ? Ok, I guess it 
> would disrupt IP broadcasts a bit...

I have never actually used ARP proxy, so I can't say for sure.  However 
when I have read about ARP proxying in the past, it never sat very well 
with me.  It always seemed like it solved part of the problem but caused 
others.

> Anyway NAT is evil. Don't use unless you can't avoid it.

I'll have to disagree with you on that statement.  Now if you amend it a 
bit, I can live with it.  "NATing in the wrong locations is evil."  NAT 
in and of its self is a good tool to use.  However it is not the end 
all, be all tool that some would like it to be.  NATing a private 
network out to a single IP on the internet for outbound internet access 
is very good.  If you want to start having some inbound internet access 
it is not as good for very long.



Grant. . . .


  reply	other threads:[~2007-05-23  0:25 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
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 [this message]
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=46538A14.608@riverviewtech.net \
    --to=gtaylor@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.