openssh
Pierre Jelenc
several problems. The major ones are:
I don't seem to be able to enter extended ASCII characters. Most ALT-xxx
(with xxx > 127) combinations result in a very brief beep, and nothing
gets sent. Characters between 32 and 127, as well as CR, LF, BS can be
entered successfully from the keypad, anything above that does not work.
Another problem is that I have completely forgotten how to set up
tunneling. I would like to use Kermit as my terminal app, tunneling
through SSH, but I can't seem to find any help in the SSH package itself.
Is that described somewhere else?
Thanks,
Pierre
--
Pierre Jelenc
The Gigometer www.gigometer.com
The NYC Beer Guide www.nycbeer.org
Dave Saville
wrote:
> I am setting up OpenSSH from openssh-4.7p1-bin.zip but I'm encountering
> several problems. The major ones are:
>
> I don't seem to be able to enter extended ASCII characters. Most ALT-xxx
> (with xxx > 127) combinations result in a very brief beep, and nothing
> gets sent. Characters between 32 and 127, as well as CR, LF, BS can be
> entered successfully from the keypad, anything above that does not work.
>
Not sure but I *think* there might be something in the ssh daemi=on
config file.
> Another problem is that I have completely forgotten how to set up
> tunneling. I would like to use Kermit as my terminal app, tunneling
> through SSH, but I can't seem to find any help in the SSH package itself.
> Is that described somewhere else?
Here is my VNC over ssh calling script.
ssh.exe -l <login name> -i <key> -N -L 5900:127.0.0.1:5900 -p <port>
<host>
VNC daemon on <host> needs to be looking at 127.0.0.1 (localhost) on
port 5900
VNC Client on box ssh entered on needs to talk to 127.0.0.1 port 5900
HTH
--
Regards
Dave Saville
NB Remove nospam. for good email address
Pierre Jelenc
> On Sun, 21 Jun 2009 01:05:41 UTC, rc...@panix.com (Pierre Jelenc)
> wrote:
> > I don't seem to be able to enter extended ASCII characters. Most ALT-xxx
> > (with xxx > 127) combinations result in a very brief beep, and nothing
> > gets sent. Characters between 32 and 127, as well as CR, LF, BS can be
> > entered successfully from the keypad, anything above that does not work.
> >
>
> Not sure but I *think* there might be something in the ssh daemi=on
> config file.
I am connecting to a separate multiuser host, I don't control the daemon,
and nobody else seems to be having that problem, so I suspect it's on my
end.
> > Another problem is that I have completely forgotten how to set up
> > tunneling. I would like to use Kermit as my terminal app, tunneling
> > through SSH, but I can't seem to find any help in the SSH package itself.
> > Is that described somewhere else?
>
> Here is my VNC over ssh calling script.
>
> ssh.exe -l <login name> -i <key> -N -L 5900:127.0.0.1:5900 -p <port>
> <host>
OK, that seems to give me a tunnel (using the default port 22), I get
logged in and the window shows no activity.
Then, from another command line, "telnet <host> 5900" flashes something
and returns to the prompt, while the ssh window gives the error message:
channel 1: open failed: administratively prohibited: open failed
I tried different port numbers but the result is the same.
Dave Saville
wrote:
> Dave Saville <da...@nospam.deezee.org> writes:
> > Here is my VNC over ssh calling script.
> >
> > ssh.exe -l <login name> -i <key> -N -L 5900:127.0.0.1:5900 -p <port>
> > <host>
>
> OK, that seems to give me a tunnel (using the default port 22), I get
> logged in and the window shows no activity.
>
Correct. It will do nothing until you want to end the session when you
can control-C it.
> Then, from another command line, "telnet <host> 5900" flashes something
> and returns to the prompt, while the ssh window gives the error message:
> channel 1: open failed: administratively prohibited: open failed
>
Hmm, if the box is running sshd then I would expect the telnet daemon
not to be running. Have you tried with whatever app you want to tunnel
to? What do you expect to be listening on 127.0.0.1:<port> on the
remote end - and have you told it to listen on 127.0.0.1?
Pierre Jelenc
>
> Hmm, if the box is running sshd then I would expect the telnet daemon
> not to be running. Have you tried with whatever app you want to tunnel
> to? What do you expect to be listening on 127.0.0.1:<port> on the
> remote end - and have you told it to listen on 127.0.0.1?
I think it may be a quirk of Kermit: It has a "telnet" which is said to be
a replacement for the native telnet (i.e. a copy of the kermit executable
with built in TELNET options) but that does not seem to work properly.
However if I use the Kermit GUI "dialer" and input the tunnel port info
there, then it works properly. All's well.
Thanks,