1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
dxpc for Debian
---------------
For dxpc to be useful, you need to have a compatible version of dxpc
running on another computer. Versions 3.9.0 and above are not
compatible with the 3.8 or earlier versions. A version of 3.9.0
backported to sarge can be found at backports.org. If you the other
computer does not have version 3.9.0 or newer of dxpc installed, you
may need to obtain the dxpc archive and compile it yourself on the
non-debian computer. Precompiled binaries for many systems are
available from http://www.vigor.nu/dxpc/.
For more information, see http://www.vigor.nu/dxpc/.
dxpc is a very useful tool, but it can be complex to figure out the
setup from the documentation. For applications in which both machines
can access each other's IP addresses, the examples in the manual page
should be sufficient. Here's a simple recipe for using it from a host
behind a firewall to access another host, tunneling dxpc through ssh.
This assumes you are sitting in front of 'local' and are logging into
'remote' with ssh.
# Get the xauth key for your current local display for later use
local% xauth list localhost.localdomain/unix:0 | awk '{print $NF}'
# Map local port 4000 to remote-host's port 4000
local% ssh remote -x -L 4000:localhost:4000
# On the remote host:
remote% dxpc -f
remote% xauth add :8 . <key-from-above>
remote% export DISPLAY=:8
# In another window on the local host:
local% dxpc -f localhost
Now you are ready to run X applications on 'remote' displaying on
local with reasonable performance even on a slow link.
-- Jay Berkenbilt <qjb@debian.org>, Mon Jun 19 19:24:40 2006
|
