Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Real Programmers don't eat quiche. They eat Twinkies and Szechwan food.

computers / comp.os.vms / Re: [7.3 VAX] XDM configuration

SubjectAuthor
* [7.3 VAX] XDM configurationJKB
`* Re: [7.3 VAX] XDM configurationMatthew R. Wilson
 `* Re: [7.3 VAX] XDM configurationchris
  `* Re: [7.3 VAX] XDM configurationJKB
   `* Re: [7.3 VAX] XDM configurationchris
    `- Re: [7.3 VAX] XDM configurationBill Gunshannon

1
[7.3 VAX] XDM configuration

<6376146b$0$7649$426a74cc@news.free.fr>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=25687&group=comp.os.vms#25687

  copy link   Newsgroups: comp.os.vms
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!cleanfeed1-b.proxad.net!nnrp1-1.free.fr!not-for-mail
Newsgroups: comp.os.vms
From: JKB...@hilbert.invalid (JKB)
Subject: [7.3 VAX] XDM configuration
Reply-To: <jkb@invalid>
User-Agent: slrn/1.0.3 (Linux)
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Date: 17 Nov 2022 11:00:59 GMT
Lines: 42
Message-ID: <6376146b$0$7649$426a74cc@news.free.fr>
Organization: Guest of ProXad - France
NNTP-Posting-Date: 17 Nov 2022 12:00:59 CET
NNTP-Posting-Host: 62.212.98.88
X-Trace: 1668682859 news-2.free.fr 7649 62.212.98.88:27583
X-Complaints-To: abuse@proxad.net
 by: JKB - Thu, 17 Nov 2022 11:00 UTC

Hello,

I have installed DECW (with SYS$UPDATE:DECW$TAILOR.EXE) on a
VAXserver (without graphic adapter) and started XDM.

XDM seems to run:

$ tcpip show service xdm
Service Port Proto Process Address State
XDM 177 UDP TCPIP$XDM 0.0.0.0 Enabled
$

On a remote workstation (Unix), nmap shows:

ORT STATE SERVICE
23/tcp open telnet
49152/tcp open unknown

XDM opens a tcp socket on port 49152 (not 177/TCP). I suppose I have
done a misconfiguration in SYS$SPECIFIC:[TCPIP$XDM]...

I only have a * in XACCESS.TXT. XSERVERS.TXT is cryptic for me and I
don't know if I have to add for example xxx.yyy.zzz:0 foreign. I
have tried with and without this line without different result.

On client side, I try to connect to this VAX with
Xephyr -query fermat :1

This last command runs fine as I can connect to another Unix station
with
Xephyr -query legendre :1

I suppose I have done a mistake somewhere, but where ?

Regards,

JKB

--
Si votre demande me parvient en code 29, je vous titiouillerai volontiers
une réponse.

Re: [7.3 VAX] XDM configuration

<slrntndebu.3ti6q.mwilson@daenerys.home.mattwilson.org>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=25693&group=comp.os.vms#25693

  copy link   Newsgroups: comp.os.vms
Path: i2pn2.org!i2pn.org!aioe.org!Y5XlPYve1KbSxuYrSEoB5w.user.46.165.242.75.POSTED!not-for-mail
From: mwil...@mattwilson.org (Matthew R. Wilson)
Newsgroups: comp.os.vms
Subject: Re: [7.3 VAX] XDM configuration
Date: Thu, 17 Nov 2022 22:45:18 -0000 (UTC)
Organization: Aioe.org NNTP Server
Message-ID: <slrntndebu.3ti6q.mwilson@daenerys.home.mattwilson.org>
References: <6376146b$0$7649$426a74cc@news.free.fr>
Injection-Info: gioia.aioe.org; logging-data="25362"; posting-host="Y5XlPYve1KbSxuYrSEoB5w.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: slrn/1.0.3 (Linux)
X-Notice: Filtered by postfilter v. 0.9.2
 by: Matthew R. Wilson - Thu, 17 Nov 2022 22:45 UTC

On 2022-11-17, JKB <JKB@hilbert.invalid> wrote:
> Hello,
>
> I have installed DECW (with SYS$UPDATE:DECW$TAILOR.EXE) on a
> VAXserver (without graphic adapter) and started XDM.
>
> XDM seems to run:
>
> $ tcpip show service xdm
> Service Port Proto Process Address State
>
> XDM 177 UDP TCPIP$XDM 0.0.0.0 Enabled
> $
>
> On a remote workstation (Unix), nmap shows:
>
> ORT STATE SERVICE
> 23/tcp open telnet
> 49152/tcp open unknown

I think the XDM port 177 doesn't show up because NMAP doesn't scan for
UDP ports by default.

> On client side, I try to connect to this VAX with
> Xephyr -query fermat :1
>
> This last command runs fine as I can connect to another Unix station
> with
> Xephyr -query legendre :1

I have vague memories of some problems when I last tried this:

1. The old version (and perhaps current versions) of the XDM/XDMCP
implementation on VMS has trouble when you're querying it from anything
other than X server display :0. I'm not sure you'll ever get it to work
using display :1 with Xnest or Xephyr. I think you'd need to move your
native X server to something other than :0 so that you can then have
Xephyr listen on :0.

2. Current/modern versions of X11 on Linux boxes are too new for OpenVMS
7.3. I've really only had luck if I intalled a backrev version of a
Linux distribution such as RHEL/CentOS 6.

-Matthew

Re: [7.3 VAX] XDM configuration

<tl6ggv$1p0b$1@gioia.aioe.org>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=25694&group=comp.os.vms#25694

  copy link   Newsgroups: comp.os.vms
Path: i2pn2.org!i2pn.org!aioe.org!jazQyxryRFiI4FEZ51SAvA.user.46.165.242.75.POSTED!not-for-mail
From: chris-no...@tridac.net (chris)
Newsgroups: comp.os.vms
Subject: Re: [7.3 VAX] XDM configuration
Date: Thu, 17 Nov 2022 23:35:59 +0000
Organization: Aioe.org NNTP Server
Message-ID: <tl6ggv$1p0b$1@gioia.aioe.org>
References: <6376146b$0$7649$426a74cc@news.free.fr>
<slrntndebu.3ti6q.mwilson@daenerys.home.mattwilson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Info: gioia.aioe.org; logging-data="58379"; posting-host="jazQyxryRFiI4FEZ51SAvA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101
Thunderbird/102.3.0
X-Notice: Filtered by postfilter v. 0.9.2
Content-Language: en-GB
 by: chris - Thu, 17 Nov 2022 23:35 UTC

On 11/17/22 22:45, Matthew R. Wilson wrote:
> On 2022-11-17, JKB <JKB@hilbert.invalid> wrote:
>> Hello,
>>
>> I have installed DECW (with SYS$UPDATE:DECW$TAILOR.EXE) on a
>> VAXserver (without graphic adapter) and started XDM.
>>
>> XDM seems to run:
>>
>> $ tcpip show service xdm
>> Service Port Proto Process Address State
>>
>> XDM 177 UDP TCPIP$XDM 0.0.0.0 Enabled
>> $
>>
>> On a remote workstation (Unix), nmap shows:
>>
>> ORT STATE SERVICE
>> 23/tcp open telnet
>> 49152/tcp open unknown
>
> I think the XDM port 177 doesn't show up because NMAP doesn't scan for
> UDP ports by default.
>
>> On client side, I try to connect to this VAX with
>> Xephyr -query fermat :1
>>
>> This last command runs fine as I can connect to another Unix station
>> with
>> Xephyr -query legendre :1
>
> I have vague memories of some problems when I last tried this:
>
> 1. The old version (and perhaps current versions) of the XDM/XDMCP
> implementation on VMS has trouble when you're querying it from anything
> other than X server display :0. I'm not sure you'll ever get it to work
> using display :1 with Xnest or Xephyr. I think you'd need to move your
> native X server to something other than :0 so that you can then have
> Xephyr listen on :0.
>
> 2. Current/modern versions of X11 on Linux boxes are too new for OpenVMS
> 7.3. I've really only had luck if I intalled a backrev version of a
> Linux distribution such as RHEL/CentOS 6.
>
> -Matthew
>

I would use wireshark or tcpdump to monitor the src and dest hosts, so
you can analyse the traffic. Used recently here to debug a vnc
connection, both network and local loopback, which xdmcp makes use of...

Chris

Re: [7.3 VAX] XDM configuration

<63773e37$0$3094$426a74cc@news.free.fr>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=25695&group=comp.os.vms#25695

  copy link   Newsgroups: comp.os.vms
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!cleanfeed1-b.proxad.net!nnrp2-1.free.fr!not-for-mail
Newsgroups: comp.os.vms
From: JKB...@hilbert.invalid (JKB)
Subject: Re: [7.3 VAX] XDM configuration
References: <6376146b$0$7649$426a74cc@news.free.fr>
<slrntndebu.3ti6q.mwilson@daenerys.home.mattwilson.org>
<tl6ggv$1p0b$1@gioia.aioe.org>
Reply-To: <jkb@invalid>
User-Agent: slrn/1.0.3 (Linux)
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Date: 18 Nov 2022 08:11:35 GMT
Lines: 49
Message-ID: <63773e37$0$3094$426a74cc@news.free.fr>
Organization: Guest of ProXad - France
NNTP-Posting-Date: 18 Nov 2022 09:11:35 CET
NNTP-Posting-Host: 62.212.98.88
X-Trace: 1668759095 news-3.free.fr 3094 62.212.98.88:20362
X-Complaints-To: abuse@proxad.net
 by: JKB - Fri, 18 Nov 2022 08:11 UTC

Le 17-11-2022, chris <chris-nospam@tridac.net> a écrit :
>
> I would use wireshark or tcpdump to monitor the src and dest hosts, so
> you can analyse the traffic. Used recently here to debug a vnc
> connection, both network and local loopback, which xdmcp makes use of...

Xephyr runs fine. I can access to legendre.systella.fr with:
Xephyr :1 -listen tcp -query legendre

If I tri to access to fermat (this VAX), I only obtain a black
screen. But it seems to answer to request:

Root hilbert:[~] > tcpdump -p -i eth0 -vvv host fermat
tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
09:06:58.114604 IP (tos 0x0, ttl 64, id 39927, offset 0, flags [DF], proto UDP (17), length 35)
hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [udp sum ok] UDP, length 7
09:06:58.246108 IP (tos 0x0, ttl 30, id 37659, offset 0, flags [DF], proto UDP (17), length 75)
fermat.systella.fr.xdmcp > hilbert.systella.fr.39124: [udp sum ok] UDP, length 47
09:06:58.246283 IP (tos 0x0, ttl 64, id 39952, offset 0, flags [DF], proto UDP (17), length 134)
hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp cksum 0x96a6 -> 0x899a!] UDP, length 106
09:06:59.483783 IP (tos 0x0, ttl 30, id 37660, offset 0, flags [DF], proto UDP (17), length 80)
fermat.systella.fr.xdmcp > hilbert.systella.fr.39124: [udp sum ok] UDP, length 52
09:06:59.483837 IP (tos 0x0, ttl 64, id 40214, offset 0, flags [DF], proto UDP (17), length 57)
hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp cksum 0x9659 -> 0xb434!] UDP, length 29
09:07:01.485945 IP (tos 0x0, ttl 64, id 40658, offset 0, flags [DF], proto UDP (17), length 57)
hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp cksum 0x9659 -> 0xb434!] UDP, length 29
09:07:05.488721 IP (tos 0x0, ttl 64, id 41488, offset 0, flags [DF], proto UDP (17), length 57)
hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp cksum 0x9659 -> 0xb434!] UDP, length 29
09:07:06.672721 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has fermat.systella.fr tell hilbert.systella.fr, length 28
09:07:06.702501 ARP, Ethernet (len 6), IPv4 (len 4), Reply fermat.systella.fr is-at 08:00:2b:7a:39:2e (oui Unknown), length 46
^C
9 packets captured
633 packets received by filter
0 packets dropped by kernel

Of course, xdm is running :

$ pipe show sys | search SYS$INPUT XDM
00000113 TCPIP$XDM_1 LEF 10 532 0 00:00:10.72 2123 2109 N

I suppose my xdm configuration is faulty somewhere.

Best regards,

JKB

--
Si votre demande me parvient en code 29, je vous titiouillerai volontiers
une réponse.

Re: [7.3 VAX] XDM configuration

<tl8b51$117k$3@gioia.aioe.org>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=25697&group=comp.os.vms#25697

  copy link   Newsgroups: comp.os.vms
Path: i2pn2.org!i2pn.org!aioe.org!jazQyxryRFiI4FEZ51SAvA.user.46.165.242.75.POSTED!not-for-mail
From: chris-no...@tridac.net (chris)
Newsgroups: comp.os.vms
Subject: Re: [7.3 VAX] XDM configuration
Date: Fri, 18 Nov 2022 16:16:33 +0000
Organization: Aioe.org NNTP Server
Message-ID: <tl8b51$117k$3@gioia.aioe.org>
References: <6376146b$0$7649$426a74cc@news.free.fr>
<slrntndebu.3ti6q.mwilson@daenerys.home.mattwilson.org>
<tl6ggv$1p0b$1@gioia.aioe.org> <63773e37$0$3094$426a74cc@news.free.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: gioia.aioe.org; logging-data="34036"; posting-host="jazQyxryRFiI4FEZ51SAvA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101
Thunderbird/102.3.0
X-Notice: Filtered by postfilter v. 0.9.2
Content-Language: en-GB
 by: chris - Fri, 18 Nov 2022 16:16 UTC

On 11/18/22 08:11, JKB wrote:
> Le 17-11-2022, chris <chris-nospam@tridac.net> a écrit :
>>
>> I would use wireshark or tcpdump to monitor the src and dest hosts, so
>> you can analyse the traffic. Used recently here to debug a vnc
>> connection, both network and local loopback, which xdmcp makes use of...
>
> Xephyr runs fine. I can access to legendre.systella.fr with:
> Xephyr :1 -listen tcp -query legendre
>
> If I tri to access to fermat (this VAX), I only obtain a black
> screen. But it seems to answer to request:
>
> Root hilbert:[~] > tcpdump -p -i eth0 -vvv host fermat
> tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
> 09:06:58.114604 IP (tos 0x0, ttl 64, id 39927, offset 0, flags [DF], proto UDP (17), length 35)
> hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [udp sum ok] UDP, length 7
> 09:06:58.246108 IP (tos 0x0, ttl 30, id 37659, offset 0, flags [DF], proto UDP (17), length 75)
> fermat.systella.fr.xdmcp > hilbert.systella.fr.39124: [udp sum ok] UDP, length 47
> 09:06:58.246283 IP (tos 0x0, ttl 64, id 39952, offset 0, flags [DF], proto UDP (17), length 134)
> hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp cksum 0x96a6 -> 0x899a!] UDP, length 106
> 09:06:59.483783 IP (tos 0x0, ttl 30, id 37660, offset 0, flags [DF], proto UDP (17), length 80)
> fermat.systella.fr.xdmcp > hilbert.systella.fr.39124: [udp sum ok] UDP, length 52
> 09:06:59.483837 IP (tos 0x0, ttl 64, id 40214, offset 0, flags [DF], proto UDP (17), length 57)
> hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp cksum 0x9659 -> 0xb434!] UDP, length 29
> 09:07:01.485945 IP (tos 0x0, ttl 64, id 40658, offset 0, flags [DF], proto UDP (17), length 57)
> hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp cksum 0x9659 -> 0xb434!] UDP, length 29
> 09:07:05.488721 IP (tos 0x0, ttl 64, id 41488, offset 0, flags [DF], proto UDP (17), length 57)
> hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp cksum 0x9659 -> 0xb434!] UDP, length 29
> 09:07:06.672721 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has fermat.systella.fr tell hilbert.systella.fr, length 28
> 09:07:06.702501 ARP, Ethernet (len 6), IPv4 (len 4), Reply fermat.systella.fr is-at 08:00:2b:7a:39:2e (oui Unknown), length 46
> ^C
> 9 packets captured
> 633 packets received by filter
> 0 packets dropped by kernel
>
> Of course, xdm is running :
>
> $ pipe show sys | search SYS$INPUT XDM
> 00000113 TCPIP$XDM_1 LEF 10 532 0 00:00:10.72 2123 2109 N
>
> I suppose my xdm configuration is faulty somewhere.
>
> Best regards,
>
> JKB
>

Looks like you are getting a reply from the third enquiry, then the last
three enquiries are being ignored by the xdmcp host. First thing I would
do is to temporarily disable all X security, as that may be enabled by
default. Other than that, no idea, other a config issue. Also, wireshark
to look at packet contents in depth...

Chris

Re: [7.3 VAX] XDM configuration

<jtptcdFfrfdU2@mid.individual.net>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=25698&group=comp.os.vms#25698

  copy link   Newsgroups: comp.os.vms
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!lilly.ping.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: bill.gun...@gmail.com (Bill Gunshannon)
Newsgroups: comp.os.vms
Subject: Re: [7.3 VAX] XDM configuration
Date: Fri, 18 Nov 2022 12:23:25 -0500
Lines: 87
Message-ID: <jtptcdFfrfdU2@mid.individual.net>
References: <6376146b$0$7649$426a74cc@news.free.fr>
<slrntndebu.3ti6q.mwilson@daenerys.home.mattwilson.org>
<tl6ggv$1p0b$1@gioia.aioe.org> <63773e37$0$3094$426a74cc@news.free.fr>
<tl8b51$117k$3@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net wWK5KySpETQtwREEop9SkgelmZFWaqmdFIC1hdWEUC67h6EOhB
Cancel-Lock: sha1:7+BC56+/KyOdKgzWLh5jLjP8ePU=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.2.2
Content-Language: en-US
In-Reply-To: <tl8b51$117k$3@gioia.aioe.org>
 by: Bill Gunshannon - Fri, 18 Nov 2022 17:23 UTC

On 11/18/22 11:16, chris wrote:
> On 11/18/22 08:11, JKB wrote:
>> Le 17-11-2022, chris <chris-nospam@tridac.net> a écrit :
>>>
>>> I would use wireshark or tcpdump to monitor the src and dest hosts, so
>>> you can analyse the traffic. Used recently here to debug a vnc
>>> connection, both network and local loopback, which xdmcp makes use of...
>>
>>     Xephyr runs fine. I can access to legendre.systella.fr with:
>>     Xephyr :1 -listen tcp -query legendre
>>
>>     If I tri to access to fermat (this VAX), I only obtain a black
>>     screen. But it seems to answer to request:
>>
>> Root hilbert:[~] > tcpdump -p -i eth0 -vvv host fermat
>> tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot
>> length 262144 bytes
>> 09:06:58.114604 IP (tos 0x0, ttl 64, id 39927, offset 0, flags [DF],
>> proto UDP (17), length 35)
>>      hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [udp sum
>> ok] UDP, length 7
>> 09:06:58.246108 IP (tos 0x0, ttl 30, id 37659, offset 0, flags [DF],
>> proto UDP (17), length 75)
>>      fermat.systella.fr.xdmcp > hilbert.systella.fr.39124: [udp sum
>> ok] UDP, length 47
>> 09:06:58.246283 IP (tos 0x0, ttl 64, id 39952, offset 0, flags [DF],
>> proto UDP (17), length 134)
>>      hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp
>> cksum 0x96a6 -> 0x899a!] UDP, length 106
>> 09:06:59.483783 IP (tos 0x0, ttl 30, id 37660, offset 0, flags [DF],
>> proto UDP (17), length 80)
>>      fermat.systella.fr.xdmcp > hilbert.systella.fr.39124: [udp sum
>> ok] UDP, length 52
>> 09:06:59.483837 IP (tos 0x0, ttl 64, id 40214, offset 0, flags [DF],
>> proto UDP (17), length 57)
>>      hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp
>> cksum 0x9659 -> 0xb434!] UDP, length 29
>> 09:07:01.485945 IP (tos 0x0, ttl 64, id 40658, offset 0, flags [DF],
>> proto UDP (17), length 57)
>>      hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp
>> cksum 0x9659 -> 0xb434!] UDP, length 29
>> 09:07:05.488721 IP (tos 0x0, ttl 64, id 41488, offset 0, flags [DF],
>> proto UDP (17), length 57)
>>      hilbert.systella.fr.39124 > fermat.systella.fr.xdmcp: [bad udp
>> cksum 0x9659 -> 0xb434!] UDP, length 29
>> 09:07:06.672721 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
>> fermat.systella.fr tell hilbert.systella.fr, length 28
>> 09:07:06.702501 ARP, Ethernet (len 6), IPv4 (len 4), Reply
>> fermat.systella.fr is-at 08:00:2b:7a:39:2e (oui Unknown), length 46
>> ^C
>> 9 packets captured
>> 633 packets received by filter
>> 0 packets dropped by kernel
>>
>>     Of course, xdm is running :
>>
>> $ pipe show sys | search SYS$INPUT XDM
>> 00000113 TCPIP$XDM_1     LEF     10      532   0 00:00:10.72
>> 2123   2109  N
>>
>>     I suppose my xdm configuration is faulty somewhere.
>>
>>     Best regards,
>>
>>     JKB
>>
>
>
> Looks like you are getting a reply from the third enquiry, then the last
> three enquiries are being ignored by the xdmcp host. First thing I would
> do is to temporarily disable all X security, as that may be enabled by
> default. Other than that, no idea, other a config issue. Also, wireshark
> to look at packet contents in depth...
>
> Chris
>
>

On another note...

Unless your running a lab full of X-terminals why do you even
need XDM? Why not just set the VAX to start sessions as soon
as it sees the remote end appear?

bill

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor