All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] FTP transparent proxying
Date: Thu, 22 Mar 2001 02:43:32 +0000	[thread overview]
Message-ID: <marc-lartc-98522903417298@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98516856629759@msgid-missing>

On Wed, Mar 21, 2001 at 09:31:46PM -0500, John Anthony Kazos Jr. wrote:
> What does that have to do with anything? One could probably adapt the
> ideas used in masquerading into transparent proxying. Transparent proxying
> of HTTP has noething to do with "host" either; that's multihoming.
> 
Ahh, but you are missing something.

IP masq doesn't know what site is being viewed.  It only knows
www.something.org port 80.

To get transparent proxying of http, you need to get squid to read the
"Host" header in http.

The best you could get out of ftp on initial connection would be
destination.  You could watch the traffic go by, and keep track of current
directory.  Now that I think of it, if you process the entire control
connection conversation, you may be able to trans proxy it.

So how do you deal with a cache hit?  Don't let that request hit the outside
server? or block the incomming ftp-data connection and slink your cached
copy in?

Anyway, the probelm would be much bigger than ip masq, as all it has to do
is sniff for "port" commands and send that incomming connection inside...

Mike

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  parent reply	other threads:[~2001-03-22  2:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21  9:58 [LARTC] FTP transparent proxying RoMaN SoFt / LLFB!!
2001-03-22  2:20 ` Mike Fedyk
2001-03-22  2:31 ` John Anthony Kazos Jr.
2001-03-22  2:43 ` Mike Fedyk [this message]
2001-03-22  4:52 ` John Anthony Kazos Jr.

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=marc-lartc-98522903417298@msgid-missing \
    --to=mfedyk@matchmail.com \
    --cc=lartc@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.