Great Circle Associates Firewalls
(December 1995)
 

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

Subject: Re: Poking a hole in the firewall
From: "Chris Liljenstolpe (Swanson) - SSDS" <Chris . Liljenstolpe @ SSDS . com>
Date: Thu, 07 Dec 1995 07:50:39 -0600
To: Garry Garrett <GARRYG @ omaha . abii . com>
Cc: "'firewalls list from GreatCircle'" <firewalls @ GreatCircle . COM>

Greetings,

        Well, this is the same problem with ftp.  You should REALLY look at
something more sturdy than router filters.  If, for example, you went with a
TIS FWTK firewall, you could do a plug GW between the two machines.  With a
socks firewall, and socksified client (it takes one aditional line in the
make file for the application) you could use socks to communicate with your
server.

        Regards,
        -=Chris

At 10:15 AM 12/6/95 PST, the sage, Garry Garrett, uttered these words:
(>
(>I have a Web server.  This web server needs to get some data off
(>of another machine, inside my firewall.  My programmer wants to write
(>his own little home grown TCP/IP application to communicate between
(>his program on my web server and his program on my interal machine.
(>He tests it internally, and it works fine.  He puts his application on the
(>web server and I poke a hole in the router and the application does
(>not work.
(>
(>Here's what I've found.  I am opening up one TCP port for him to use,
(>but the unix function calls that he's using (the only ones he really knows
(>of) operate like this:  Client calls the server on port X.  Server responds
(>to Client on port X, giving it a high port number that is available.  Client
(>calls the server on that high port number to communicate.  This allows
(>for multiple client programs to be fired off.
(>
(>My reaction is, hey, I can poke a hole at some known port number for
(>your application, but I can't just allow some random port number through
(>the router (can I?).  His reaction is, hey, I can't just choose the port 
(>number
(>that the client is going to use once it's connected.
(>
(>How are these things normally accomplished?  I need to have my Web
(>server serve up data that is on an internal machine.  What data I need
(>from the internal machine depends upon the search criteria that the Web
(>user entered on their form.  Is there some range of port numbers that
(>connect() and accept() are going to use that it's safe for me to allow
(>through my firewall, or better yet, is there a way I can control what port
(>number is assigned to the client so that I can only poke holes for the
(>clients I expect, etc.  The web server and the internal machine are
(>both unix boxes.
(>
(>Am I barking up the wrong tree?  Is there a better way to be doing this?
(>I've considered a NULL modem cable between the 2 machines, but
(>I'm not sure it can handle the load like TCP/IP can.
(>
(>Garry
(>Garry .
 Garrett @
 abii .
 com
(>
(>
--
    ( (   | (               Chris Liljenstolpe <Chris .
 Liljenstolpe @
 ssds .
 com>
     ) ) (|  ), inc.        SSDS, Inc; 8400 Normandale Lake Blvd.; Suite 993
    business driven         Bloomington, MN  55437; 
  technology solutions      TEL 612.921.2392  FAX 612.921.2395   Um Yah Yah!


Indexed By Date Previous: RE: NT Security and NTFS
From: jwojn @ telxon . mis . telxon . com (Wojno, Jim)
Next: Re: Poking a hole in the firewall
From: Eric Pederson <Eric_Pederson . RISD @ notes . mdor . state . mn . us>
Indexed By Thread Previous: Re: Poking a hole in the firewall
From: Brent @ GreatCircle . COM (Brent Chapman)
Next: Re: Poking a hole in the firewall
From: Eric Pederson <Eric_Pederson . RISD @ notes . mdor . state . mn . us>

Google
 
Search Internet Search www.greatcircle.com