TELNET-TERMINAL launcher edit dialog
1. General Information
2. TELNET-TERMINAL launcher
3. COM-PORT-TERMINAL launcher
4. SHELL-TERMINAL launcher
5. Execution of TERMINAL launcher (to create and connect new terminal window)
6. AUTOLOGIN
7. Show current launcher for terminal window, Re-connect terminal window using current launcher, Re-connect terminal window using another launcher
There are 3 types of launchers to create terminal windows of the Proxy32 built-in terminal and(/or) (re-)connect them (TELNET-TERMINAL, COM-PORT-TERMINAL, SHELL-TERMINAL).
To create new connection launchers (TELNET-TERMINAL, COM-PORT-TERMINAL, SHELL-TERMINAL) user has to add them on the LauncherTree either by right-clicking on the LauncherTree and selecting “Add TreeNode” menu or by clicking on the “New” button (flashing green) on the toolbar of the LauncherTree window.
In the process of creating new connection launchers user provides some essential information needed for execution of such launchers.
Every launcher has a tooltip field that allows to supply text that will be shown when user hovers the mouse pointer over the launcher. The rest of the launcher fields will depend on the type of the launcher.
For creation of TELNET-TERMINAL launcher user has to supply information about TELNET server to which new terminal will be connecting. This info includes three parts: hostname/IP-address of the TELNET server, TCP port number and encryption mode (TLS on/off) used by the server.
TELNET-TERMINAL launcher edit dialog
For creation of COM-PORT-TERMINAL launcher user has to supply information about COM-PORT (serial port on Windows) to which new terminal will be connecting. This info includes multiple parts: local COM-PORT number, speed, number of data bits, number of stop bits, parity and flow control modes.
COM-PORT-TERMINAL launcher edit dialog
For creation of SHELL-TERMINAL launcher user has to supply command line to start local interactive text mode process which new terminal will be running.
SHELL-TERMINAL launcher edit dialog
For example:
command line proxycygterm.exe -s '/usr/bin/bash -i -l' will start local CYGWIN bash shell on the CYGWIN TTY created by interface program "proxycygterm.exe".
command line proxycygterm.exe -s '/usr/bin/ssh -o StrictHostKeyChecking=no -o Port=22 -o User=sshuser 192.168.1.9' will start local CYGWIN OpenSSH ssh client on the CYGWIN TTY created by interface program "proxycygterm.exe" and connect this ssh client to host 192.168.1.9 on the port 22 with user name "sshuser".
command line proxycygterm.exe -s '/usr/bin/sftp -o StrictHostKeyChecking=no -o Port=22 -o User=sftpuser 192.168.1.9' will start local CYGWIN OpenSSH sftp client on the CYGWIN TTY created by interface program "proxycygterm.exe" and connect this sftp client to host 192.168.1.9 on the port 22 with user name "sftpuser".
command line proxycygterm.exe -s '/usr/bin/ftp 192.168.1.9 21' will start local CYGWIN ftp client on the CYGWIN TTY created by interface program "proxycygterm.exe" and connect this ftp client to host 192.168.1.9 on the port 21.
command line proxycygterm.exe -s '/usr/bin/telnet 192.168.1.9 23' will start local CYGWIN telnet client on the CYGWIN TTY created by interface program "proxycygterm.exe" and connect this telnet client to host 192.168.1.9 on the port 23.
command line plink.exe -ssh -P 22 -l sshuser -pw <PROXYPASSWORD=my ssh password> 192.168.1.9 will start local plink (putty's command line friend) ssh client and connect it to host 192.168.1.9 on the port 22 with user name "sshuser" and password stored in proxy32 protected parameter named "my ssh password".
command line psftp.exe -P 22 -l sftpuser -pw <PROXYPASSWORD=my sftp password> 192.168.1.9 will start local psftp (putty's command line friend) sftp client and connect it to host 192.168.1.9 on the port 22 with user name "sftpuser" and password stored in proxy32 protected parameter named "my sftp password".
command line proxycygterm.exe -s '/usr/bin/screen -s bash' will start local CYGWIN "screen" application (for multiplexing multiple virtual vt100 terminals into one physical terminal) on the CYGWIN TTY created by interface program "proxycygterm.exe". Use "^aS" then "^aTAB" then "^ac" to split window, switch to newly created split, create second virtual vt100 terminal and start new shell in the second virtual terminal. Then you can use both virtual terminals and switch keyboard input between them with "^aTAB" (means "press Ctrl-a first, then press TAB"). Further use of "^aS" then "^aTAB" then "^ac" will create more virtual terminals. This mode is convenient to control multiple connections from single terminal window under control of single script. Such operation allows to simulate functionality of "cluster" (or "vector") terminal when multiple connections (for example, to several network nodes working in redundant load sharing cluster) are established in one shot and under control of single script. Issuing command '^a:caption always "%w"' will force status line under the screen of every virtual terminal.
command line proxycygterm.exe -s '/usr/bin/mc' will start local CYGWIN "Midnight Commander" application (similar to Norton Commander for DOS) on the CYGWIN TTY created by interface program "proxycygterm.exe".
command line cmd will start local windows shell.
command line proxywinconsole.exe will start MS Windows powershell on hidden windows console.
command line proxywinconsole.exe cmd will start "cmd" on hidden windows console, so some other programs called from cmd prompt will start working.
command line proxywinconsole.exe powershell will start MS Windows powershell on hidden windows console.
After they are created and visible on the LauncherTree, to use (execute) connections, user has to double-click them on LauncherTree. Double click on the new “connection” (SHELL-TERMINAL, TELNET-TERMINAL, COM-PORT-TERMINAL launcher) will create new Terminal window in the current workspace and connect it according to the connection info that is stored in the launcher (SHELL-TERMINAL, TELNET-TERMINAL, COM-PORT-TERMINAL) itself.
If there is a PLUGIN or I-SCRIPT launcher located on LauncherTree directly under executed TERMINAL launcher, such PLUGIN or I-SCRIPT launcher will be executed automatically on the "connect" of the terminal. This is done to let PLUGIN/I-SCRIPT to catch user/password prompt sent from remote host on "connect" and to let PLUGIN/I-SCRIPT interact with remote host to finish terminal login sequence automatically. More details on this is in AUTOLOGIN documentation.
Right click on green light button in terminal window shows (highlights/selects on LauncherTree) TERMINAL launcher that is keeping current connection info for this terminal window.
Green light button in terminal window allows to connect/disconnect terminal window (left click on green button to toggle connect/disconnect). This is because terminal window remembers the TERMINAL launcher from which it took connection info last time (current Terminal launcher). Re-connect via left click on green light button includes AUTOLOGIN sequence if there is a PLUGIN or I-SCRIPT launcher located on LauncherTree directly under current TERMINAL launcher.
Terminal window can be re-connected to another remote host using information stored in any existing TERMINAL launcher. To connect terminal window using connection info from another TERMINAL launcher:
Re-connect via middle click on green light button includes AUTOLOGIN sequence if there is a PLUGIN or I-SCRIPT launcher located on LauncherTree directly under highlighted TERMINAL launcher.
1. General Information
2. TELNET-TERMINAL launcher
3. COM-PORT-TERMINAL launcher
4. SHELL-TERMINAL launcher
5. Execution of TERMINAL launcher (to create and connect new terminal window)
6. AUTOLOGIN
7. Show current launcher for terminal window, Re-connect terminal window using current launcher, Re-connect terminal window using another launcher