Andrew Perrin wrote: > > Yes, you're doing it wrong. > > 1.) You don't need two ssh sessions; just one, from xserver_machine to > work_linux_box: > ssh -C -X work_linux_box from xserver_machine > > 2.) When you set the display to ipmasq_box:0.0, you're asking the remote > host to display X apps on the main display of your ipmasq_box - which, > luckily, your ipmasq_box refuses to do. What you want to do is route X > packets through your ssh tunnel. Most ssh servers set $DISPLAY > appropriately, so before doing the export DISPLAY part, do: > > echo $DISPLAY > > DISPLAY should contain the name of the *remote* host, followed by a colon, > then x.0 where x>1. Mine contains: > > [EMAIL PROTECTED]:~$ ssh -X isis.unc.edu > [EMAIL PROTECTED] ~ >echo $DISPLAY > login2.isis.unc.edu:11.0 > > If you don't get that, I'm not entirely sure how to figure out which > display will tunnel for you (the 11.0 in this case). Maybe others can help > there. > > The theory is this: you open a connection from your firewalled machine to > your work machine. You do this in a secure way, using ssh, that is > permitted by both firewalls. You then use this secure channel to funnel X > packets through. X client apps on your work box "display" to a dummy > server on the same machine, so far as they know. That dummy server, > though, catches the packets and sends them over the pre-existing ssh > tunnel to your xserver_machine, where your ssh client grabs them back and > sends them to xserver_machine's local X server. > > Hope this helps. >
I'm very interested in have X11 ssh tunnel working !! but I have the same problem. How can I force ssh server to set DISPLAY variable? If DISPLAY variable is not set when I ssh the *remote* server, is it a sshd problem or an Xserver problem? thanks --xgnu
