kamikaze2002261 / connectbot

Automatically exported from code.google.com/p/connectbot
Apache License 2.0
0 stars 0 forks source link

Post-Login automation does not pass command to another shell #554

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

I am trying to do a Wake-on-WAN on my Pirelli PRGAV4202N-Router.

1. Set up the SSH-Connection to my Router properly and confirm it's working

2. I set the following in Post-Login automation:

system shell 
ether-wake -b -i br0 [MY MAC-ADRESS]
[IMAGINE A LINEBREAK HERE]

3. Connect

What is the expected output? What do you see instead?
"system shell" calls a downgraded busybox shell inside the routers firmware. 
This works properly via automation. The ether-wake command should then be 
executed, but isn't. The Problem is that all further commands after "system 
shell" are not executed nor are they written.
They simply do not "survive" the call of another shell.

The command works when typed in manually!

The Output is:
----------------------------------------------------------
OpenRG> valu [***PASSWORD***]

Returned 0
OpenRG>
OpenRG>
OpenRG> system shell
Temporary setting log_level off

BusyBox v1.01 (2005.09.07-07:38+0000) Built-in shell (lash)
Enter 'help' for a list of built-in commands.

/ #
----------------------------------------------------------

What version of the product are you using (you can see this by using Menu
-> About in the Host List)?
ConnectBot 1.7.1-pslib (Just because of the PW-autosave function).
The original version doesn't work either.

What type of system are you trying to connect to?
Pirelli PRGAV4202N Wireless Router

If you are able to connect, what is the output of "echo $TERM", "uname -a",
and any other relevant information on the host?

ECHO $TERM: "VT102"
uname -a: "uname: No such file or directory"

The Router uses something like a "Jungo OpenRG"-Software
I can not determine, what the system exactly is.

Please provide any additional information below.

Original issue reported on code.google.com by c-stei...@gmx.net on 4 Feb 2012 at 1:50