I finally got annoyed enough with that "X tunneling doesn't work with an FC[23] ssh server -sometimes-" problem to track down its source. It appears that sometimes FC3's (and probably FC2's) sshd will only attempt to set up X11 tunneling on IPV6, instead of both IPV[46]. This seems to work around it well enough for the time being: 1) Put "OPTIONS=-4" in /etc/sysconfig/sshd 2) Run "service restart sshd" A more long-term solution -might- be to rebuild sshd with "--with-4in6". On Mon, 2004-12-13 at 14:07 -0800, Dan Stromberg wrote: > On Thu, 2004-12-09 at 09:29 -0500, Craig Thomas wrote: > > On Wed, 2004-12-08 at 21:49 -0800, Dan Stromberg wrote: > > > The FC3 host is the sshd server. Same for FC2: the sshd server. > > > > <snip> > > > > > Yes. It seems to say everything is fine, but then it still doesn't work > > > most of the time. > > > > <snip> > > > > > tesuji-strombrg> xterm > > > X connection to tesuji.nac.uci.edu:12.0 broken (explicit kill or server > > > shutdown). > > > > I'm late to this thread, so maybe I missed this but are you sure X > > forwarding is enabled for the FC3 server? the default behavior changed > > from FC2 to FC3 WRT X forwarding in openssh. > > > > http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/os/RELEASE-NOTES-en.html > > Thanks for the tip. Does it appear that this is saying that FC3's > client-side ssh behavior changed? > > I'm ssh'ing from RHEL 3 to FC2 and FC3, and having problems with that. > RHEL 3 doesn't seem to have the new -X behavior yet > > > > > > HTH, > > > > -- > > Craig Thomas <cjtinhp@xxxxxxxxxxxxx> > > >
Attachment:
signature.asc
Description: This is a digitally signed message part
