AFAIK, you can't bind two sockets to the same port, at least on Linux. Can you send us the output of "netstat -anp --inet", and "ps -ef | grep ssh"? This is strange indeed!!! Kosala On Wed, May 27, 2009 at 9:46 PM, Ariel Burbaickij <ariel.burbaickij@xxxxxxxxx> wrote: > Would be strange topic for cheating, wouldn't it ?! ;-) > Yes, it is real. I can bind two times to the same local > port for better (or most probably) worse of it. > > /wbr > Ariel Burbaickij > > On Wed, May 27, 2009 at 8:34 PM, Greg Wooledge <wooledg@xxxxxxxxxxx> wrote: >> On Wed, May 27, 2009 at 10:52:30AM +0200, Ariel Burbaickij wrote: >>> >>> ssh -L 7777:localhost:7777 some_user_name1@system1 >>> >>> Then the second user comes and sets up the section in following way: >>> >>> ssh -L 7777:localhost:7777 some_user_name1@system2 >>> >>> He is successful in setting the second port forwarding session. >> >> Really? I get an error when I try to duplicate your results: >> >> imadev:~$ ssh -L 7777:localhost:22 vandev >> RSA host key for IP address '10.76.142.101' not in list of known hosts. >> wooledg@vandev's password: >> bind: Address already in use >> channel_setup_fwd_listener: cannot listen to port: 7777 >> Could not request local forwarding. >> >>> On attempt to connect to local port 7777 second user is forwarded to system1. >> >> Right, because the second user failed to set up the forward. So he's >> just using the successful first forward, which anyone on the client >> system can use. >> > -- Kosala -------------------------------------------- Disclaimer: Views expressed in this mail are my personal views and they would not reflect views of the employer. -------------------------------------------- blog.kosala.net www.linux.lk/~kosala/ www.kosala.net
