Re: "automatic" port forwarding

From: Jacob Nevins (jacobn_at_chiark.greenend.org.uk)
Date: 02/24/05

  • Next message: Martin: "Re: SCP failing" 
    Date: 24 Feb 2005 17:57:06 +0000 (GMT)

    Lucio Crusca <lcml@pixel.it> writes:
    >$ ssh -R someport:127.0.0.1:22 -l portfwuser servername
     [...]
    >The problem is that the user at the client side does not know which port to
    >use on the server (which is, BTW, a dynamic port above 49152). So the port
    >forwarding should be activated by the server itself (maybe in the script
    >used as default shell), because it knows the correct port number. Is there
    >a way to do that?

    This should be possible in principle with the SSH-2 protocol; the client
    can request a port number of 0, which should cause the server to
    allocate a port and tell the client what it was. Whether implementations
    support it is a different matter, of course; I don't know of any that do
    (but I've not looked very hard).

    I don't think this is possible even in principle with SSH-1.

  • Next message: Martin: "Re: SCP failing"

    Relevant Pages

    • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
      ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
      (Debian-User)
    • Re: Remote Connection Issue
      ... through port number 3389 and a workstation on the LAN through port number ... I understand that you want to allow a LAN client ... and you have configured server publishing rule ... > By default Terminal Server and Windows 2000 Terminal Services uses TCP ...
      (microsoft.public.windows.server.sbs)
    • Re: RealVNC
      ... Default listening port for RealVNC server that runs on the machine on which ... Then there is default Java listening port on port 5800 on the client machine ...
      (microsoft.public.windows.server.sbs)
    • Re: Redirecting data sent to a local printer to another host and port on the network
      ... All client workstations have access to the ... simply redirecting netcat traffic on port 9100 to port 515 on ... Only LPR clients talk to LPD print server daemons. ... >workstation at the branch site where the print job originated. ...
      (comp.unix.sco.misc)
    • Re: thin client com ports
      ... I'm glad that you got at least one more client working! ... MCSE, CCEA, Microsoft MVP - Terminal Server ... the COM port settings? ... I am testing several thin clients. ...
      (microsoft.public.windows.terminal_services)