All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gáspár Lajos" <swifty@freemail.hu>
To: "bldrnorth@gmail.com" <bldrnorth@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Transparent bridge and proxy - with only lo?
Date: Tue, 14 Apr 2009 17:22:25 +0200	[thread overview]
Message-ID: <49E4AA31.1000807@freemail.hu> (raw)
In-Reply-To: <127d8b5e0904061249h4426b860n14cfcb6f3299a0ee@mail.gmail.com>

Hi!

bldrnorth@gmail.com írta:
> Hi:
>
> While there is no shortage of documentation on setting up a
> transparent bridge with Squid proxy, I have only seen examples that
> assign an IP address to the bridge interface.  In my circumstances,
> the bridge is between the ISP's bridge and our own router, such as:
> (ISP Bridge) <--->(Our Bridge)<--->(Our router).  Typical I'm sure,
> but Our router is assigned only 1 IP address so I really don't have an
> IP address to assign the bridge interface.  Here's how I'm setup:
>
>   
What about a private IP on the brigde?

> # Normally, would assign an IP address to br0 and a default route
>   
(nod)
> I was thinking I should be able to re-direct to the localhost
> interface 127.0.0.1, or perhaps assign an address like 127.0.0.2 to
> br0, but then could not figure out the appropriate iptables and route
> command.  I'm sure I could assign br0 a private ip address, but then
> wouldn't be sure how to tell it to route.  Here's all I have so far...
>
>   
127.0.0.1/8 is not this kind of playground :D

Swifty


  reply	other threads:[~2009-04-14 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 19:49 Transparent bridge and proxy - with only lo? bldrnorth
2009-04-14 15:22 ` Gáspár Lajos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-26 18:54 bldrnorth

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=49E4AA31.1000807@freemail.hu \
    --to=swifty@freemail.hu \
    --cc=bldrnorth@gmail.com \
    --cc=netfilter@vger.kernel.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.