Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- can't start remote X programs
- Tomasz Chmielewski
June 4, 2005, 11:48 am
rate this thread
They are connect to each other through an OpenVPN tunnel.
If I connect from BROKEN to GOOD using ssh -X ..., I can start remote X
programs without problems (for example, xclock).
When I connect from GOOD to BROKEN, I can't start remote X programs:
$ ssh -l user BROKEN -v -X
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 1535
debug1: channel 1: new [x11]
debug1: confirm x11
And I can wait forever, but xclock is not started on my local machine.
I can't kill it with ctrl+C.
When I do "ps x" on BROKEN, it shows xclock is running.
When I kill it (killall xclock), I can't use the terminal on which I
Has anyone seen this before?
What should I look for?
I noticed that when I try to start "xclock" on BROKEN, there are some
packets going on lo interface (this is captured with iptraf):
localhost:1363 = 10 760 -PA- lo
localhost:6013 = 8 1016 --A- lo
Re: can't start remote X programs
Worth a try:
but my money is on this:
(Richard: perhaps add "PPPoE" and "VPN" as common contributors to this?)
I'll bet if you do a "netstat" on both ends and find you ssh connection
you'll see a constant or increasing number int he "Send-Q" at the ssh
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
- » Using Putty for the SSH tunnel AND the telnet program
- — Previous thread in » Secure Shell Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum