Support remote connectivity with phindows and phditto clients
phrelay [-eGx] [-b number] [-D debugfile] [-g port] [-k delay,interval,retry] [-V...]
The phrelay utility supports remote user interface clients on other nodes.
When you specify a modem (using the -m option to phditto or phindows), the remote client first acts as a simple text terminal emulator so you can interact with the modem, dial up a remote QNX machine, and log in.
Once you're logged in, you can start a Photon session by entering the following command:
The remote client synchronizes with phrelay and starts to function as a Photon graphics terminal.
When you specify a TCP/IP connection (using the -t option to phditto or phindows), the inetd program running on the remote QNX host automatically launches phrelay for you, provided phrelay and inetd have been configured properly (see below).
There are several configuration issues that need to be taken care of before you can use phrelay over TCP/IP.
First, the QNX host must have TCP/IP installed and running. In addition, inetd must be running with the following items specified in the inetd configuration file /etc/inetd.conf:
phrelay stream tcp nowait root /usr/bin/phrelay phrelay
Note that the descriptions in the default inetd.conf file are commented out; uncomment the ones that you want to use.
The file /etc/services file must include the following line (it's in the default file):
These two entries cause inetd to listen for incoming requests to establish a new Photon session. When a request is detected (from a remote phindows or phditto client), inetd automatically establishes a full TCP/IP connection and launch phrelay on that connection. The remote phindows or phditto client is then fully connected to a local Photon session.
You can use phrelay to connect a machine running phindows (on Windows) or phditto (on Neutrino) to a Neutrino self-hosted development machine acting as a target via the machines' serial ports.
Use a null modem cable to connect COM1 on a Windows or Neutrino development host to /dev/ser1 on a QNX6 development machine acting as a target. Here are two similar procedures that can be used to connect phditto/phindows to phrelay:
You should see the phrelay connect sequence automatically resume. Another way to connect to the target is as follows:
The -s command-line option of phditto and phindows is provided to simplify the task of creating shortcuts to Photon applications within the MS-Windows desktop.
By using the -s option, you can create an icon or shortcut on the MS-Windows desktop to start up a Photon application automatically (within a private phindows session). With proper specification of the remote Window Manager options, it's possible to make that Photon application look like it's a native MS-Windows application.
When phrelay runs on the QNX host machine, it looks up the Photon service specified with the -s parameter in a configuration file (/etc/config/phrelay[.node]). If a matching service is found, then phrelay launches the specified Photon command instead of the default Photon desktop. You can specify optional window-manager options, but the default mode is to start the remote Photon application so that it looks and behaves as if it were a native MS-Windows application.
The phditto/phindows -U option is often used with the -s option to specify a QNX userid to use when running the remote Photon command. If no userid is given, and the phrelay service doesn't specify a default userid, then Photon pops up the QNX Photon Login dialog requesting the QNX userid before proceeding. By specifying a userid with the -U option, you can avoid this login dialog.
For example, if a MS-Windows shortcut were created as follows:
phindows -tx.x.x.x -svpoker -Ujoe
where the IP address x.x.x.x specified the TCP/IP address of QNX node 2, and the phrelay configuration file on node 2 (/etc/config/phrelay.2) contained the following line:
vpoker % /usr/photon/bin/vpoker
then Joe could directly launch a Photon vpoker session (running as QNX userid joe) on his MS-Windows desktop by clicking on the shortcut icon.
The phrelay utility processes requests for service according to the contents of a configuration file. If phrelay is running on QNX node n, then the file /etc/config/phrelay.n is used. If this file doesn't exist, then the default file /etc/config/phrelay is used.
The format of each service entry in the phrelay configuration file is as follows:
service user [-W pwm_options] command
service is the symbolic name of the Photon service (matches the -s phindows or phditto parameter).
user defines how to process userids that may be specified on the phindows or phditto command line (-U option).
user can be one of:
pwm_options can be one or more of the following Photon Window Manager options:
The default Window Manager options are PWRcbtfr.
command is the Photon command to launch instead of the default command, which starts the Photon desktop.
The phrelay utility supports one of three data compression options that the client can request:
The phrelay utility makes very extensive use of data caching techniques to minimize the amount of data that needs to be transmitted from the host to the client machine. Thanks to this intensive data caching, phditto/phindows can operate over modem-link speeds as low as 9600 baud.
Most “large” static data objects in Photon are “tagged” with a unique 32-bit ID (tag). Tagged objects include bitmap data, image data, and color palettes. These objects are generally tagged when first created by the Photon program developers. This process is accomplished automatically by the Photon development tools, so the program developer is, for the most part, not even aware that this is taking place.
Photon passes these tags along with the data objects as they flow through the Photon event space. The end result is that Photon graphics drivers (such as phrelay) almost always have available a small, unique, precalculated tag to identify the larger Photon graphical objects.
The phrelay utility supports encrypted connections with Phindows versions 3.09 and later.
When Phindows requests an encrypted connection (by specifying a key using the -K commandline option), phrelay looks for a matching key in the /etc/config/phkeys file. Each line of the file has this format:
Keys can be up to 31 characters long.
The line that starts with the * character applies to connections that don't specify a Photon service and user ID. For Phindows connections that specify a service (-s), a user ID can also be specified using -U. In this case, phrelay finds the user in the /etc/config/phkeys, and checks that the specified key matches the key sent by Phindows. If a matching key isn't found, phrelay doesn't allow the connection, and Phindows displays a “Error: Permission problem on host” message.
Both Phindows and phditto allow a user to connect to an existing Photon session, which displays the contents of the Photon session on the remote client's screen. You can disable this option by creating an /etc/system/config/noditto file on your target. When this file exists, remote clients can still connect to your target machine using their own private Photon session, but they can't view an already running Photon session.
From a remote phindows or phditto session, type:
Using the Photon microGUI in the Neutrino User's Guide