Re: Can't use SSH X forwarding with DHCP

From: Nico Kadel-Garcia (nkadel@bellatlantic.net)
Date: 12/16/01 

From: "Nico Kadel-Garcia" <nkadel@bellatlantic.net>
Date: Sun, 16 Dec 2001 06:49:36 GMT

"Richard E. Silverman" <slade@shore.net> wrote in message
news:m1lofl1itcp.fsf@syrinx.oankali.net...
> >>>>> "Nico" == Nico Kadel-Garcia <nkadel@bellatlantic.net> writes:
>
> Nico> Yes, it is. This isn't an SSH problem per se, it's a "DISPLAY"
> Nico> and X forwarding issue. The local DISPLAY variable needs to be
> Nico> set to the real, DNS registered hostname or IP address before
> Nico> you ssh to the target machine.
>
> I'm not sure why you say that -- the remote DISPLAY setting is not derived
> from the local one at all.
>
> --
> Richard Silverman
> slade@shore.net

It has to be, Richard.

1: If there is no DISPLAY set on the ssh-client/X-server (ghods, I hate that
X-server mis-naming nonsense!), there is no information on an X session to
tell the ssh-server software about.

2: If the X session is already forwarded outside of SSH, the X windows are
transitively passed to the correct host (admittedly via X forwarding, which
links a local DISPLAY on the ssh server to an X display on the X client, but
there has to be a transitive link of some sort). This can be done through a
fairly large number of hosts.

3: I once spent a week going absolutely ape*** trying to get SSH working
with X forwarding in a particularly weird NIS/DNS mismatched domain names
piece of !@#$ that was only solved by actually setting the DISPLAY to
include the full fully qualified hostname (FQHN), as opposed to the DISPLAY
setting of ":0" which the console logins normally gave. I'm not sure of the
details of why it was failing, but it was the only solution I found that
worked.

Quantcast