From: Julian Lyndon-Smith <asterisk@dotr.com>
To: bridge@lists.osdl.org
Subject: [Bridge] transparent bridge and proxies
Date: Thu, 24 Aug 2006 18:31:05 +0100 [thread overview]
Message-ID: <44EDE259.4050009@dotr.com> (raw)
I want to be able to install a box that is a transparent bridge, but
that is also running a transparent proxy, but with a twist ..
i am a newbie in all things linux, so bear with me :)
So far I have managed to install centos 4.3, and following various
guides on the net, created a bridge between eth1 (connected to lan) and
eth0 (connected to router). That works great.
I also managed to install squid, get it running transparently and added
a rule to iptables to make all that work just fine. So now, all my
clients attached to the lan run through the squid proxy without them
knowing.
Now, for the twist. For development and testing, I assigned an ip
address and gateway to the bridge. I need to be able for a "non-it"
person to install this box without having to set it up at all , so it
cannot have an ip address assigned, as it *may* be in use somewhere else
on the lan or router.
So, I changed the ip address to 0.0.0.0. Everything except squid still
worked. I presume that's because it does not know how to route the data
to get stuff.
Can I add a rule to iptables or something to say "anything that's come
from eth1 into the local box, after processing send to eth0" and
vice-versa ?
Julian.
next reply other threads:[~2006-08-24 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 17:31 Julian Lyndon-Smith [this message]
2006-08-24 18:20 ` [Bridge] transparent bridge and proxies Marek Kierdelewicz
2006-08-24 20:17 ` Benny Amorsen
2006-08-24 22:42 ` Etienne Pretorius
2006-08-24 20:17 ` Melissa Meyer
2006-08-24 22:05 ` Julian Lyndon-Smith
2006-08-24 22:34 ` Melissa Meyer
2006-08-24 22:20 ` Marek Kierdelewicz
-- strict thread matches above, loose matches on Subject: below --
2006-08-25 10:53 Skept
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=44EDE259.4050009@dotr.com \
--to=asterisk@dotr.com \
--cc=bridge@lists.osdl.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