Great Circle Associates Firewalls
(March 1993)

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: WAIS: an overview
From: Brent Chapman <brent @ GreatCircle . COM>
Date: Mon, 01 Mar 93 10:54:24 -0800
To: Jonny Goldman <jonathan @ Think . COM>
Cc: firewalls @ GreatCircle . COM
In-reply-to: Your message of Thu, 25 Feb 93 20:22:19 PST

Jonny Goldman <jonathan @
 Think .
 COM> writes:

# Server forwarding is built into every WAIS server, so if you can run a
# server on your firewall host, you can tunnel to external servers using it.
# Server forwarding uses the database-name field of the source description to
# encode a remote server/port/database, of the form:
#  db @
# You can easily modify the source description, replacing the :ip-name with
# the name of your firewall, the :tcp-port with the port the server is using,
# and the :database-name with the encoded name.  If your firewall can connect
# to the remote server, you're done.  This is what the automatic forwarding
# client code does.

I assume that the forwarding server uses a random TCP port above 1024
for its end of the conversation with the real server?  In other words,
the forwarding server uses port 210 to talk to the internal client,
and some random TCP port above 1024 to talk to the "real" server on
the outside world?

Brent Chapman                                   Great Circle Associates
Brent @
 GreatCircle .
 COM                           1057 West Dana Street
+1 415 962 0841                                 Mountain View, CA  94041

Indexed By Date Previous: Re: Appletalk through firewalls.
From: davidl @ Newbridge . COM (David Law)
Next: Re: Appletalk through firewalls.
From: Mark Verber <verber @ parc . xerox . com>
Indexed By Thread Previous: Re: Appletalk through firewalls.
From: johng @ weema . chi . uwa . edu . au (John Gibbins)
Next: WAIS: an overview
From: Jonny Goldman <jonathan @ Think . COM>

Search Internet Search