For those who don't know, one can run X applications remotely by using ssh:
ssh -CX server
C is compression, X is enable X forwarding. X forwarding must be enabled in the ssh
config file on the ssh server.
Without ssh -X, in order to run remote X applications, you must do something like the
2nd example below (export display..) where the remote X server connects to your local
computer to display graphics. Then you have to mess around with X permissions using
xhost or xauth.
Dennis, so you are trying something like this?:
sasha(private wks) ----- emma-firewall ------ external internet server
On sasha:
ssh -X external
dennis@external password: *****
$ xterm
<error message, can't open emma:0.0>
Is this correct? Or are you doing something like this:
ssh external
export display="emma:0.0"
xterm
<error>
This message
> _X11TransSocketINETConnect: Can't get address for emma
> xterm Xt error: Can't open display: emma:0.0
Tells me the server "external" is being told to forward the X display to "emma"
Obviously it doesn't not know who emma is because it can't get her address. Thus it
can't open the display. The display emma:0.0 is actually ipaddress:0.0 where 0.0 has
to do with which display and such on the machine.
So you do have a uofo account. Here's what I'm doing:
$ alias |grep cs
alias cs='export TERM=xterm ; ssh cs.uoregon.edu -X -C -l coryp'
$ cs
[EMAIL PROTECTED]'s password:
You have 2 unread article(s) in newsgroup uo.cs.announce.
<snip>
coryp@ix:~$ xcalc
<xcalc loads on my laptop (I'm at home connected through cable, running X4.)>
coryp@ix:~$ export|grep -i display
declare -x DISPLAY="ix:17.0"
coryp@ix:~$ export|grep -i ssh
declare -x SSH_CLIENT="24.12.251.176 33186 22"
declare -x SSH_TTY="/dev/pts/36"
declare -x XAUTHORITY="/var/run/ssh-pRa13560/cookies"
coryp@ix:~$ exit
logout
Connection to cs.uoregon.edu closed.
Your firewall shouldn't matter, as long as you can connect via ssh to somewhere.
Cory
>
> emma.clipper.net is my home firewall, with a static IP address. The box I'm trying
>to run the X session from is sasha.localdomain, with a private IP address given by
>the DHCP server running on my firewall. I'm assuming there is some sort of error in
>my router config or in my IPF rules. The firewall is running OpenBSD, and as far as
>I've seen everything else has been working fine for the past year or so. I also
>haven't found any messages indicating a problem in my firewall or other confiurations.
>
> Any ideas?
>
> Cheers,
> Dennis
