Re: port forwarding without the shell
From: Andrius Kurtinaitis (andrius.kurtinaitis_at_maf.vu.lt)
Date: 06/24/04
- Previous message: Perry L. Jones: "scp destination file has not data"
- In reply to: Andrius Kurtinaitis: "Re: port forwarding without the shell"
- Next in thread: Darren Tucker: "Re: port forwarding without the shell"
- Reply: Darren Tucker: "Re: port forwarding without the shell"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 24 Jun 2004 11:55:05 +0300 To: secureshell@securityfocus.com
Sorry, I made a mistake.
> ssh -v -1 -N -L 9999:localhost:80 192.168.42.6 2> err.txt >out.txt &
>
> then, it gets stopped (only with proto 2).
It gets stopped ([1]+ Stopped) only when using the protocol 1, and with
protocol 2 it runs happily in the background. How to find out why it stopps?
Andrius
Andrius Kurtinaitis wrote:
> Darren Tucker wrote:
>
>> You can use "ssh -N" to establish a tunnel without invoking a shell,
>> but if you want "one-shot" you'll have to background it and kill it
>> from the shell.
>
>
> Well, if I'm using the Protocol 2, then everything goes well, but with
> Protocol 1 (which I must use with my ssh server) I was not able to
> background the ssh process. If I start it with:
>
> ssh -v -1 -N -L 9999:localhost:80 192.168.42.6 2> err.txt >out.txt &
>
> then, it gets stopped (only with proto 2).
>
> if I add the -n option, the it exits immediately.
> ssh -v -1 -n -N -L 9999:localhost:80 192.168.42.6 2> err-n.txt >out.txt &
>
> I attach the output of the two calls at the end.
>
> Andrius
- Previous message: Perry L. Jones: "scp destination file has not data"
- In reply to: Andrius Kurtinaitis: "Re: port forwarding without the shell"
- Next in thread: Darren Tucker: "Re: port forwarding without the shell"
- Reply: Darren Tucker: "Re: port forwarding without the shell"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
