Re: 'Redirecting' a socket connection?

From: Jerry Coffin (jcoffin_at_taeus.us)
Date: 06/02/04 

Date: Tue, 1 Jun 2004 20:43:36 -0600

In article <OONn4iESEHA.556@TK2MSFTNGP10.phx.gbl>, cabadam@tamu.edu
says...
> No no - this isn't for a website. Its just that port 80 happens to be the
> one port that the firewall will allow incoming connections on.

Okay -- well, in that case it's perfectly possible. You simply
require the use to send _something_ that allows you to sort out which
application s/he wants. Given that, you already outlined a
reasonable strategy: a front-end application that looks for that
flag, and the forwards the data through to the chosen application. 

-- 
    Later,
    Jerry.
The universe is a figment of its own imagination.

Relevant Pages

  • Re: All these open ports
    ... > debian package and you don't believe you put it there yourself - its ... commercial firewall products can't detect such attempts to "phone home". ... outward, it by definition must be legitimate, so it gets granted a port, ... (Okay, now, everybody yell in unison: ...
    (Debian-User)
  • Re: port forwarding, ssh, nat
    ... The ssh client, like all TCP clients, will use unpredictable port ... narrowed the problem down to my firewall, which only has 22, 67, 80, ... So long as incoming connections to port 22 are permitted, ...
    (comp.unix.bsd.freebsd.misc)
  • Re: ISP keeps connecting to my port 445
    ... > no valid reason an ISP might automatically scan this port that I can ... > explanation. ... > which as you say your firewall already does. ...
    (comp.security.firewalls)
  • Re: Redirecting a socket connection?
    ... one port that the firewall will allow incoming connections on. ... > out which web site responds to a given request. ...
    (microsoft.public.vc.mfc)
  • FC2 samba...
    ... The windows clients cannot connect to samba. ... It seems all okay. ... The firewall doesn't run. ... The port 139 is avaiable. ...
    (Fedora)
Loading