Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

ssh ports



On Fri, May 04, 2007 at 04:21:09PM -0400, Boland, John wrote:
> i've been setting up an ssh server behind a firewall and only allowing
> port 22 through.
> ssh works like a champ. however, scp and sftp give stalled messages
> during transfers.  the files do eventually transfer but the time is a
> little less than waiting for the next ice age!
> it appears as though there is a back connection established for the
> transfer after ssh is setup.
> with ftp, i'd use the pasv command for the clients and set the max and
> min passive ports in the ftpd config file.  is there a similar thing in
> ssh?  if not, is there someway to know what set of ports to limit ssh to
> use for this back connection?

No, and no. SSH only uses one port pair (22 by default).

Where does it stall when you up the verbosity level (-vvv)?

-dsr-

-- 
.. .----. --   .-. . .- -.. .. -. --.   -.-- --- ..- .-.   -- .- .. .-.. .-.-.-   .-- .... ---   . .-.. ... .   .. ... ..--.. 
http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org