Hello,

I have 3 machines:

yoda: A4000T running netBSD 1.3.2 and using kdm

altair: P133 running Red hat linux 5.1, using xdm

jabba: P60 running FreeBSD 2.2.7, using xdm

I run xdm from the rc on all tree machines, and then start the Xserver with the
"-indirect localhost" options, to get the chooser window.

At this point if I choose any machine except the local one the *BSD stations
try to connect to 127.0.0.1, instead of the ip of the machine which is asking
session management.

Altair, instead responds properly, I can log into it from yoda(the amiga) but
not from jabba...

this is the significant parto of a kdm -debug on yoda(I've also tried xdm but
it's identical):


WaitForSomething
select returns 1.  Rescan: 0  ChildReady: 0
ProcessRequestSocket
header: 1 4 11
Forward respond 11
Forward client address (port 1031) 127 0 0 1
ConvertAddr returning 0 for family 2
all_query_respond: conntype=0, addr=7f, len=4
Send willing  Willing to manage
WaitForSomething
select returns 1.  Rescan: 0  ChildReady: 0
ProcessRequestSocket
header: 1 4 11
Forward respond 11
Forward client address (port 1031) 127 0 0 1
ConvertAddr returning 0 for family 2
all_query_respond: conntype=0, addr=7f, len=4
Send willing  Willing to manage
WaitForSomething
select returns 1.  Rescan: 0  ChildReady: 0
ProcessRequestSocket
header: 1 4 11
Forward respond 11
Forward client address (port 1031) 127 0 0 1
ConvertAddr returning 0 for family 2
all_query_respond: conntype=0, addr=7f, len=4
Send willing  Willing to manage
WaitForSomething
select returns 1.  Rescan: 0  ChildReady: 0
ProcessRequestSocket
header: 1 4 11
Forward respond 11
Forward client address (port 1031) 127 0 0 1
ConvertAddr returning 0 for family 2
all_query_respond: conntype=0, addr=7f, len=4
Send willing  Willing to manage

What am I doing wrong? Is it perhaps a bug in xdm?

Thanks in advance.

Guido Falsi <mad_pilot@usa.net>