openssh unix dev - Sep 2000 - Binding to specific IPs/ports

Sorry if this is the wrong place to post, I'm not a developer.

OpenSSH seems to be capable of binding to any given list of IP
addresses, on any given list of ports. What it can't seem to
do, however, is be given any combination of these.

Lets say I want to bind to 1.1.1.1:22 as well as 2.2.2.2:80.
(I choose 80 knowing it is the http port, just for that purpose,
because some people are behind firewalls and cannot get out
on ports other than 80.)

The only way to do this would require also listening on 1.1.1.1:80,
and if I'm running something else there (like a web server :),
it doesn't work.


It seems to me this is just an issue regarding how openssh loads
its conf file, and would not be too hard to implement in future
versions, for one of you developers :)

Please let me know.
-- 

-*% % % % % % % % % % % % % % % % *-
  -*    xercist                 *-
  -*    xercist at mindless.com    *-
-* % % % % % % % % % % % % % % % %*-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url :
http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20000920/abda8c30/attachment.bin

On Wed, 20 Sep 2000, xercist wrote:
> Date: Wed, 20 Sep 2000 16:25:54 -0600
> From: xercist <xercist at lammah.com>
> To: openssh-unix-dev at mindrot.org
> Subject: Binding to specific IPs/ports
> 
> Sorry if this is the wrong place to post, I'm not a developer.
> 
> OpenSSH seems to be capable of binding to any given list of IP
> addresses, on any given list of ports. What it can't seem to
> do, however, is be given any combination of these.
> 
> Lets say I want to bind to 1.1.1.1:22 as well as 2.2.2.2:80.
> (I choose 80 knowing it is the http port, just for that purpose,
> because some people are behind firewalls and cannot get out
> on ports other than 80.)
> 
> The only way to do this would require also listening on 1.1.1.1:80,
> and if I'm running something else there (like a web server :),
> it doesn't work.
> 
Couldn't you just start two instances of OpenSSH, e.g. using two separate
configuration files?

Or am I missing somthing?
> 
> It seems to me this is just an issue regarding how openssh loads
> its conf file, and would not be too hard to implement in future
> versions, for one of you developers :)
> 
> Please let me know.
> -- 
> 
> -*% % % % % % % % % % % % % % % % *-
>   -*    xercist                 *-
>   -*    xercist at mindless.com    *-
> -* % % % % % % % % % % % % % % % %*-
> 
Best regards,

Wojtek