In answer to a question I posted the other day,
I'm uploading to Sunsite a couple of
program sources. The major work, not mine, is
"xforward", from the DEC Cambridge labs. See the
README in the sources for more information.

Background: 
Well, I finally got "term" working, along with
"txconn". Hopwever, I do most of my work on a color xterminal
attached to box on which "term" runs, via ethernet.
I wanted my x stuff received via the "txconn"
remapping to display on the color termminal.
I looked around and found the "xforward" program which does
the right thing with tcp connections.

Unfortunately, txconn does its magic by connecting to
a unix family socket on the X-server instead of a
internet socket.

Solution:

This was a quick hack on the xforward source
so that I could redirect an incoming (term socket) request
for a local X-server on a unix socket
to a remote X-server connected via
an internet socket.

It's meant to be used together with the term utility
txconn.

Usage:

Let me give the way I use it:

0) Kill any Xervers on local "term" machine hopf2.
1) From local machine hopf2, connect to remote machine
   hopf via pcomm
2) From login on hopf, start "term -l ./.termrc/hopf2.log "
3) In pcomm, ^A-up and select "term" as my upload utility.
   ( I had previous installed term as an external protocol in 
   pcomm).
4) switch to another window on hopf2, and do
   "yforward -display color:0 -n 0 -t 360 &
   Hopf2 should respond with a message like
  "display is hopf2.math.purdue.edu:/tmp/.X11-unix/X0"
5) Now trsh back to hopf:
   "trsh "
   and on hopf, "trsh"
   hopf will give you a message giving the display number, 
   probably hopf:9.
   Now on hopf, do "setenv DISPLAY hopf:9 "
   and you X applications should dislay back on "color:0"
6) This will prompt you for each attempted connections.
   Some X-app open several connections, so this is a minor
   pain.

The theory one more time:

hopf:9 ---(via term)-->hopf2:0 ---(via yforward)--> color:0

Good luck.

Clarence Wilkerson