Tim, try 'ssh -X' emphasis on the capital X. From the ssh --help page:
-X Enable X11 connection forwarding.
-x Disable X11 connection forwarding (default).
I use this method all the time. In fact I've aliased ssh to always
forward my X connections. I connect on my local lan at the office, or I
connect to the university servers from either the office or home or
anywhere on campus, or I connect to my linux servers from the office, at
home or on campus via a freeswan vpn. I don't ever want to bother with
x commands, I like to just type in a command on my console that has a
gui attached and have it come up. This is how I primarily operate
locally (my screen has three buttons on afterstep: netscape, terminal,
quit). All programs are started on the command prompt. I don't want
there to be any difference to whether I start a java gui program locally or
running on a CS server, whether I'm in the computer lab on my laptop or
at home or at the office. I've got my laptop and my network setup so
that everywhere works the same and its great.
The speed is fine with cable at home (1536k), 768k at work and internet2
at UO.
Here's my alias:
alias ssh='ssh -c blowfish -X -C'
-C means compress before sending it over the line, a good idea!
-X forward X, if no X on the server then it doesn't do it
-c blowfish means use a different cipher rather than 3des.
so 'ssh cs.uoregon.edu' is what I type, but this happens:
'ssh -c blowfish -X -C cs.uoregon.edu'
One other note, X forwarding works whether X is running on the server or
not. I never use [xgk]dm and can't stand it. On some systems I have
part of X installed so I can install X programs that use X libraries,
however X is neither running nor even configured on those servers.
However I can connect via ssh -X and run those X programs just fine.
Example: ethereal running on a remote system with X installed but not
running.
Cory
On Sun, Oct 06, 2002 at 12:01:08AM -0500, Timothy Bolz wrote:
> Thank you, Bob
>
> Yes you were right in how I wanted to use it. I followed your direction and
> to I had an xterm and Mozilla up on Boyle. Your directions were simple and
> easy to follow. I search the web for debian remote x windows and tried to do
> some of the things they said. They didn't work. Your example was right to
> the point. Anyone who hasn't tried this should just follow your directions.
> I found that if you log out of tesla you have to go thru the whole procedure
> all over again. I think I should be able to put it in a script which I can
> call.
>
> I tried the ssh -x and got an error. Your first suggestion should be fine.
>
> I use gdm , so I can set Tesla up as a server for x terminal box ( a system I
> have without a hard drive).
>
> I Thought about vnc but I think it would be impractical. Especially when my
> wife is using the machine I want to access.
>
> Again Thanks
> Tim
>
>
> On Saturday 05 October 2002 18:54, you wrote:
> > Timothy Bolz wrote:
> > > I have two machines and would like to try running x windows
> > > remotely. The one machine (Tesla) has all my files on it. The
> > > other (Boyle) and is just used when my wife wants to use Tesla. I
> > > thought why can't I just log into Tesla via Boyle using X. From
> > > what I've read you have to have xdmcp set to true in gdm.conf. This
> > > will allow remote logins. Now how do I remotely log in if Boyle
> > > runs it's own gdm? Can I run gdm on both machines and log in from
> > > the other? Can you restrict access to local machines? How secure
> > > is it? I've read you can run it over ssh. Has anyone tried running
> > > x remotely on their own home network?
> >
> > There are several ways to run X remotely. If I understand right, you
> > want to sit at Boyle's keyboard and screen. If that's wrong, please
> > switch Tesla <-> Boyle in everything I say below.
> >
> > 1. You can run one or a few X clients remotely. To do that,
> > you log into Tesla using telnet/rlogin/ssh, then set
> > some environment variables, and launch programs that display
> > on Boyle. Like this.
> >
> > boyle> xauth list
> > boyle:0 MIT-MAGIC-COOKIE-1 1234567890abcde.....f
> > boyle> ssh tesla
> > Linux tesla 2.4.18 blah blah
> > tesla> export DISPLAY=boyle:0
> > tesla> xauth add boyle:0 MIT-MAGIC-COOKIE-1 1234567890abcde......f
> > tesla> xterm &
> > (at this point a new xterm window should appear.)
> > tesla> mozilla &
> > (etc.)
> >
> > If you're on a secure network, this is the way to go. It's fast
> > and easy. You can have windows open on many machines at once.
> >
> > 2. You can do basically the same thing, but tunneling the X Window
> > System protcol through ssh. That way, it's encrypted and
> > authenticated. Like this.
> >
> > boyle> ssh -X tesla
> > Linux tesla 2.4.18 blah blah
> > tesla> xterm &
> > (a new xterm window should appear. etc.)
> >
> > This is the way I do most of my remote computing within the house.
> > It's still too slow to run across an IDSL line this way, but
> > it's dandy on Ethernet.
> >
> > 3. You can set up Boyle so it's a XDM client of Tesla. This way,
> > you'll get a login screen from Tesla when you log in, and you
> > won't be able to (easily) run programs on Boyle at all.
> > Specifically, your window manager, session manager, and other
> > desktop software will run across the net, and everything will
> > be a little bit sluggish, compared to running locally.
> >
> > Also, keep in mind that your whole session is running across the
> > ethernet, unencrypted, so if you type your password or your credit
> > card number, anyone on the local network can read it. (This is
> > probably not an issue at your house, but just so you're aware...)
> >
> > It sounds like this is what you're trying to set up. I haven't
> > set this up in years, so I don't remember all the details.
> >
> > To answer your specific questions, you need to turn off xdm/gdm/kdm
> > on Boyle. Instead, start the X server directly from
> > /etc/init.d/something. Add boyle:0 to the list of displays
> > that xdm on tesla watches for. I think that's just a matter
> > of adding "boyle:0" to /etc/X11/xdm/Xservers if you use xdm,
> > or to /etc/kde2/kdm/Xserver if you use kdm, or someplace else
> > if you use gdm. (Sorry, I don't have gdm installed.)
> >
> > I'm not familiar with tunneling XDMCP across ssh, but it sounds
> > like a good idea. (-:
> >
> > 4. Finally, you can use vnc. Virtual Network Computing. It's
> > cross-platform, so if you want to remotely use a Macintosh
> > or that other OS that a few people use (I forget its name --
> > Microsomething W-something), you can use VNC.
> >
> > VNC is dead, VNC is resurrected, and TightVNC is currently the
> > preferred fork of VNC. www.tightvnc.com TightVNC is fast enough
> > that I can just barely stand to run a remote display from TiVo at
> > home. I often share a desktop with engineers in California, and
> > tightVNC is what we use.
>
> _______________________________________________
> Eug-LUG mailing list
> [EMAIL PROTECTED]
> http://mailman.efn.org/cgi-bin/listinfo/eug-lug
_______________________________________________
Eug-LUG mailing list
[EMAIL PROTECTED]
http://mailman.efn.org/cgi-bin/listinfo/eug-lug
