openssh unix dev - Mar 2004 - -R port:host:hostport - communication lost after some minutes

Hi

As this '-R' command initially works fine I guess it must be a bug.

I have to login at a computer which is hidden behind NAT. The user 
(joe) at the computer then connect to my server with the command:
  ssh -R 1234:localhost:22 test.com

Then I login to test.com and connect back to joes computer:
  ssh -p 1234 localhost

I get successfull connection every time but after a few minutes, 
typing some simple commands the communication just stops and I can 
type nothing. The only thing I can do is to ask joe to establish a new 
connection.

Am I doing something wrong?
How can I give a better bug report?

/hans
-- 
Hamletsgade 4 - 201, DK-2200 K?benhavn N, Phone: +45 3582 9079
Schou Industries ApS      http://schou.dk/    CVR: 26 13 44 39
--------------------------------------------------------------
Sprogrevsere vil have at semikolon bliver mere anvendt;
jeg er imod ;-)

Hello,


Hans Shou wrote :
> The user 
> (joe) at the computer then connect to my server with the command:
>   ssh -R 1234:localhost:22 test.com
> 
> Then I login to test.com and connect back to joes computer:
>   ssh -p 1234 localhost
> 
> I get  successfull  connection  every  time  but  after  a  few
> minutes, typing some simple  commands  the  communication  just
> stops and I can type nothing. The only thing I can do is to ask
> joe to establish a new connection.

I'm interested in tips to debug that kind of  problem  too.  I've
already  been  in  exactly  the  same   configuration   (ssh   -R
1234:localhost:22 and then ssh -p 1234) to bypass NAT,  and  I've
also had problems with it hanging up and me having to  ask  "joe"
to connect again. I must add that in my particular situation, joe
connected to "test.com" through "a lot"  (at least 3) of
internal
networks / firewalls / NAT... And that probably is  the  root  of
the problem.


Flavien.

On Thu, 4 Mar 2004, Flavien wrote:
> I must add that in my particular situation, joe connected to
> "test.com" through "a lot"  (at least 3) of internal
networks /
> firewalls / NAT... And that probably is the root of the problem.
I had exactly the same problem with "jane", and she is sitting behind 
a different router on another location. Both joe and jane has only one 
router in my setup.

I guess I can reproduce the bug witin 15 minutes.

/hans
-- 
Hamletsgade 4 - 201, DK-2200 K?benhavn N, Phone: +45 3582 9079
Schou Industries ApS      http://schou.dk/    CVR: 26 13 44 39
--------------------------------------------------------------
Sprogrevsere vil have at semikolon bliver mere anvendt;
jeg er imod ;-)