Re: Connecting to a modern Xserver with an old client

2023-07-25 Thread Dave Howorth
On Sat, 22 Jul 2023 10:05:33 +0100 Carsten Haitzler wrote: > On Sat, 22 Jul 2023 01:18:29 + (UTC) Michael K > said: > > > I'm trying to connect an old HP logic analyzer (circa 1998) to a > > modern Xorg server. The error message I get is ... > > > > Xlib: connection to "192.168.1.1:1.0"

Re: Connecting to a modern Xserver with an old client

2023-07-24 Thread Carsten Haitzler
On Mon, 24 Jul 2023 20:56:30 +1000 Peter Hutterer said: > On Mon, Jul 24, 2023 at 10:56:13AM +0100, Dave Howorth wrote: > > On Sun, 23 Jul 2023 14:14:37 -0700 > > Alan Coopersmith wrote: > > > > > On 7/23/23 13:48, Carsten Haitzler wrote: > > > >> So as per the man page I added 

Re: Connecting to a modern Xserver with an old client

2023-07-24 Thread Carsten Haitzler
On Sun, 23 Jul 2023 14:14:37 -0700 Alan Coopersmith said: > On 7/23/23 13:48, Carsten Haitzler wrote: > >> So as per the man page I added +byteswappedclients to the Xorg command line > >> and it works! > > > > wow... i've never encountered that before. in all these decades... well > > well. :)

Re: Connecting to a modern Xserver with an old client

2023-07-24 Thread Ulrich Sibiller
On Mon, Jul 24, 2023 at 12:56 PM Peter Hutterer wrote: > And logging every access from a client is not great either - and logging > it once will likely just make it disappear in the rest of the server log. Well, you just need to log _failing_ clients. Those clients will not produce many

Re: Connecting to a modern Xserver with an old client

2023-07-24 Thread Peter Hutterer
On Mon, Jul 24, 2023 at 10:56:13AM +0100, Dave Howorth wrote: > On Sun, 23 Jul 2023 14:14:37 -0700 > Alan Coopersmith wrote: > > > On 7/23/23 13:48, Carsten Haitzler wrote: > > >> So as per the man page I added +byteswappedclients to the Xorg > > >> command line and it works! > > > > > >

Re: Connecting to a modern Xserver with an old client

2023-07-24 Thread Dave Howorth
On Sun, 23 Jul 2023 14:14:37 -0700 Alan Coopersmith wrote: > On 7/23/23 13:48, Carsten Haitzler wrote: > >> So as per the man page I added +byteswappedclients to the Xorg > >> command line and it works! > > > > wow... i've never encountered that before. in all these decades... > > well well.

Re: Connecting to a modern Xserver with an old client

2023-07-23 Thread Alan Coopersmith
On 7/23/23 13:48, Carsten Haitzler wrote: So as per the man page I added +byteswappedclients to the Xorg command line and it works! wow... i've never encountered that before. in all these decades... well well. :) It was only added a few months ago:

Re: Connecting to a modern Xserver with an old client

2023-07-23 Thread Carsten Haitzler
On Sun, 23 Jul 2023 20:22:18 + (UTC) Michael K said: > OK, I got xtrace to work ("$ x11trace -n -D 192.168.1.1:10.0" & have the > instrument connect to display 10.0) and it was more instructive... > > Got connection from 192.168.1.16:6144 > 000:<: am msb-first want 11:0 authorising with ''

Re: Connecting to a modern Xserver with an old client

2023-07-23 Thread Michael K
OK, I got xtrace to work ("$ x11trace -n -D 192.168.1.1:10.0" & have the instrument connect to display 10.0) and it was more instructive... Got connection from 192.168.1.16:6144 000:<: am msb-first want 11:0 authorising with '' of length 0 000:>: Failed, version is 11:0 reason is '  Prohibited

Re: Connecting to a modern Xserver with an old client

2023-07-23 Thread Michael K
Yes, xtrace looks just like what I need but I cant't get it to work on remote connections. If I run "xterm -display :9.0" from the machine where X server and xtrace (x11trace on Fedora) runs it works (and I see X11 conversations) but If I try from another machine on the network (xterm -display

Re: Connecting to a modern Xserver with an old client

2023-07-23 Thread Carsten Haitzler
On Sat, 22 Jul 2023 20:47:03 + (UTC) Michael K said: > > To answer Grant's question. Yes, I had added the X ports but I've now turned > off the firewall just to be sure. Here is the wireshark conversation.  I'm > not knowledgeable enough to recognize the issue.. > > 10.0

Re: Connecting to a modern Xserver with an old client

2023-07-22 Thread Grant Taylor
On 7/22/23 3:47 PM, Michael K wrote: To answer Grant's question. Yes, I had added the X ports but I've now turned off the firewall just to be sure. ACK I generally don't like disabling the firewall. -- I'm currently tilting at RPC for NFS to get it to work through a firewall. But

Re: Connecting to a modern Xserver with an old client

2023-07-22 Thread Michael K
To answer Grant's question. Yes, I had added the X ports but I've now turned off the firewall just to be sure. Here is the wireshark conversation.  I'm not knowledgeable enough to recognize the issue.. 10.0192.168.1.16192.168.1.1TCP606915 → 6001 [SYN] Seq=0

Re: Connecting to a modern Xserver with an old client

2023-07-22 Thread Grant Taylor
On 7/22/23 4:05 AM, Carsten Haitzler wrote: :1.0 (:1) is your problem i think. your X will be on :0 (port 6000). the above error indicates it'd after something on :1 (port 6001). also double check something is listening on 192.168.1.1 as opposed to only on 127.0.0.1 I had wondered about

Re: Connecting to a modern Xserver with an old client

2023-07-22 Thread Carsten Haitzler
On Sat, 22 Jul 2023 01:18:29 + (UTC) Michael K said: > I'm trying to connect an old HP logic analyzer (circa 1998) to a modern Xorg > server. The error message I get is ... > > Xlib: connection to "192.168.1.1:1.0" refused by server > Unable to open window on "192.168.1.1:1.0" > > I have

Re: Connecting to a modern Xserver with an old client

2023-07-21 Thread Grant Taylor
On 7/21/23 8:18 PM, Michael K wrote: I'm trying to connect an old HP logic analyzer (circa 1998) to a modern Xorg server. ... What might be the issue with this old X client authenticating with a modern X server? I would assume that `xhost +` would disable almost all security checking. I'd

Connecting to a modern Xserver with an old client

2023-07-21 Thread Michael K
I'm trying to connect an old HP logic analyzer (circa 1998) to a modern Xorg server. The error message I get is ... Xlib: connection to "192.168.1.1:1.0" refused by server Unable to open window on "192.168.1.1:1.0" I have executed "xhost +" to allow access by any client and I am able to