From: Ralf Spenneberg <lists@spenneberg.org>
To: SBlaze <dagent.geo@yahoo.com>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Need help have some questions...
Date: 25 Aug 2003 22:30:28 +0200 [thread overview]
Message-ID: <1061843428.1507.86.camel@kermit> (raw)
In-Reply-To: <20030825200507.25987.qmail@web40207.mail.yahoo.com>
Am Mon, 2003-08-25 um 22.05 schrieb SBlaze:
> > Now, what does the circuit relay do? Does it just amplify the signal? Or does
> > it terminate, reconstruct and forward the information?
> >
> Ralf seems to disagree that the second layer is a bridge... I never though of a
> bridge as a dumb proxy...but thats essentially what it is right?? Anyway this
> isn't really the focus of what I want to know...
Circuit Relay operates on Application layer. A typical circuit relay is
socks. It just forwards connections.
> So if I understand what Ramen is saying. It is possible to do this with a
> module that could be loaded into iptables. Aside from the CPU argument is
> there any other reason why this isn't being done? It seems to come up time and
> time again.
>
You could, if you would write the module. But this is better done in
userspace.
> > >
> Again no one really shed any light on what I'm supposed to do here. What proxy
> am I supposed to use? Everyone is saying use a proxy but no one is giving any
> specifics as to what kind or what software?.
Sure, I did: Use Apache. Apache can work as a webserver for you on your
Linux box and at the same time as a proxy for the Windows box.
Cheers,
Ralf
--
Ralf Spenneberg
RHCE, RHCX
Book: Intrusion Detection für Linux Server http://www.spenneberg.com
IPsec-Howto http://www.ipsec-howto.org
Honeynet Project Mirror: http://honeynet.spenneberg.org
next prev parent reply other threads:[~2003-08-25 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1061192932.1915.10.camel@kermit>
2003-08-18 20:13 ` Need help have some questions SBlaze
2003-08-18 20:52 ` Ramin Dousti
2003-08-23 20:51 ` SBlaze
2003-08-25 3:24 ` Ramin Dousti
2003-08-25 20:05 ` SBlaze
2003-08-25 20:30 ` Ralf Spenneberg [this message]
2003-08-25 20:39 ` SBlaze
2003-08-25 20:57 ` Ralf Spenneberg
2003-08-25 22:40 ` Ramin Dousti
2003-08-25 22:53 ` SBlaze
2003-08-25 23:02 ` Ramin Dousti
2003-08-25 22:35 ` Ramin Dousti
2003-08-25 5:54 ` Ralf Spenneberg
2003-08-18 20:53 ` Wallwork, Nathan
2003-08-18 21:09 ` Ralf Spenneberg
2003-08-18 21:14 ` Frank Smith
2003-08-15 9:29 SBlaze
2003-08-15 10:02 ` Ralf Spenneberg
2003-08-15 22:09 ` SBlaze
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=1061843428.1507.86.camel@kermit \
--to=lists@spenneberg.org \
--cc=dagent.geo@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 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.