activating xdmcp in suse-8.1
Question about the activation of xdmcp in kde and its login manager. After enabling xdmcp in suse-8.1 in kdmrc in the file: /opt/kde3/share/config/kdm/kdmrc, nothing shows up in kde login manager. Does anyone have succesfully activated this functionality in suse-8.1? /opt/kde3/share/config/kdm/kdmrc [X-:0-Greeter] EnableChooser=true LogSource=/dev/xconsole ShowLog=true [Xdmcp] Enable=true Willing=/etc/X11/xdm/Xwilling Xaccess=/etc/X11/xdm/Xaccess -- Richard Bos Without a home the journey is endless
On Saturday 01 March 2003 22:30, Richard Bos wrote:
Question about the activation of xdmcp in kde and its login manager.
After enabling xdmcp in suse-8.1 in kdmrc in the file: /opt/kde3/share/config/kdm/kdmrc, nothing shows up in kde login manager. Does anyone have succesfully activated this functionality in suse-8.1?
/opt/kde3/share/config/kdm/kdmrc [X-:0-Greeter] EnableChooser=true LogSource=/dev/xconsole ShowLog=true
[Xdmcp] Enable=true Willing=/etc/X11/xdm/Xwilling Xaccess=/etc/X11/xdm/Xaccess
I once experimented with this, but with earlier SuSE-versions. So I try to help you a bit on your way and give a few hints. 1. Not quite sure but: a. YaST -> Security and Users -> Security settings b. [Local security configuration] Choose "Custom settings", click "Next" c. [Password settings] click "Next" d. [Boot settings] click "Next" ** e. [Login settings] Enable "Allow remote graphical login", click "Next" f. [Adding user settings" click "Next" g. [Miscellaneous settings" click "Finish" AFAIK now you should be able to login remotely, without a firewall. YaST (actually: SuSEconfig) will take care of the needed changes in the config files. 2. With a firewall: a. open ports tcp/udp 6000-6063 (x11), tcp/udp 177 (xdmcp) b. I remember vaguely an issue with broadcasts. I solved it with editing /etc/sysconfig/scripts/SuSEfirewall2-custom, 1st or 2nd function, allowing the broadcast (or so...). You don't need to open the full range of 6000-6063. A few will do, e.g. 6000-6003 or so. Watch the firewall logs (on both the client and the server). Hope this will get you on your way, Cheers, Leen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is an exerpt of /etc/sysconfig/displaymanager: - -------------------------------------------------------------------- # # Here you can set the default Display manager (kdm/xdm/gdm/wdm/console). # DISPLAYMANAGER="kdm" # # Allow remote access to your display manager (kdm only for now) # DISPLAYMANAGER_REMOTE_ACCESS="yes" - -------------------------------------------------------------------- The last line is what you want. Don't forget to run 'SuSEconfig --module xdm' after changing the file. BTW, /opt/kde3/share/config/kdm/kdmrc is not really used. I have also stumbled around some time to find that. Suse have decided to use /etc/opt/kde3/share/config/kdm/kdmrc instead. Torsten On Saturday 01 March 2003 22:30, Richard Bos wrote:
Question about the activation of xdmcp in kde and its login manager.
After enabling xdmcp in suse-8.1 in kdmrc in the file: /opt/kde3/share/config/kdm/kdmrc, nothing shows up in kde login manager. Does anyone have succesfully activated this functionality in suse-8.1?
/opt/kde3/share/config/kdm/kdmrc [X-:0-Greeter] EnableChooser=true LogSource=/dev/xconsole ShowLog=true
[Xdmcp] Enable=true Willing=/etc/X11/xdm/Xwilling Xaccess=/etc/X11/xdm/Xaccess -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+YZp8wicyCTir8T4RAk+8AKC2qrAzV8kVZepLt6Ad3LDkQtncawCfXQF0 AvG+UnkOVVt0ygCqriWyIzA= =nQDI -----END PGP SIGNATURE-----
Thorsten and Leendert, thank you both for your reply, but the problem persist. I must admit after receiving your replies that the description of what I had done was a little scarse... It seems that "allow remote access" is enabled by default. I exactly did not use the DISPLAYMANAGER_REMOTE_ACCESS variable, but enabled the settings in the config files in stead.... A "grep DISPLAYMANAGER_REMOTE_ACCESS *" in /sbin/conf.d shows what it confirms that I did the right thing (pfff ;). What I expect to appear here now, is an option at the login manager in the order of "remote login". However, the only option I get under the "menu" button is "restart X server". How disappointing :(( Is this a bug in kde, or is it something else?? <<== It would be nice to get this confirmed.... Op zondag 2 maart 2003 06:45, schreef Torsten Foertsch:
This is an exerpt of /etc/sysconfig/displaymanager: -------------------------------------------------------------------- # # Here you can set the default Display manager (kdm/xdm/gdm/wdm/console). # DISPLAYMANAGER="kdm"
# # Allow remote access to your display manager (kdm only for now) # DISPLAYMANAGER_REMOTE_ACCESS="yes" --------------------------------------------------------------------
The last line is what you want. Don't forget to run 'SuSEconfig --module xdm' after changing the file.
BTW, /opt/kde3/share/config/kdm/kdmrc is not really used. I have also stumbled around some time to find that. Suse have decided to use /etc/opt/kde3/share/config/kdm/kdmrc instead.
Torsten
On Saturday 01 March 2003 22:30, Richard Bos wrote:
Question about the activation of xdmcp in kde and its login manager.
After enabling xdmcp in suse-8.1 in kdmrc in the file: /opt/kde3/share/config/kdm/kdmrc, nothing shows up in kde login manager. Does anyone have succesfully activated this functionality in suse-8.1?
/opt/kde3/share/config/kdm/kdmrc [X-:0-Greeter] EnableChooser=true LogSource=/dev/xconsole ShowLog=true
[Xdmcp] Enable=true Willing=/etc/X11/xdm/Xwilling Xaccess=/etc/X11/xdm/Xaccess
-- Richard Bos Without a home the journey is endless
On Sunday 02 March 2003 22:52, Richard Bos wrote:
Thorsten and Leendert,
thank you both for your reply, but the problem persist. I must admit after receiving your replies that the description of what I had done was a little scarse...
It seems that "allow remote access" is enabled by default.
I exactly did not use the DISPLAYMANAGER_REMOTE_ACCESS variable, but enabled the settings in the config files in stead....
A "grep DISPLAYMANAGER_REMOTE_ACCESS *" in /sbin/conf.d shows what it confirms that I did the right thing (pfff ;).
Ok. (Thorsten was right)
What I expect to appear here now, is an option at the login manager in the order of "remote login". However, the only option I get under the "menu" button is "restart X server". How disappointing :((
Is this a bug in kde, or is it something else?? <<== It would be nice to get this confirmed....
You won't find anything changed there... ;-P Execute X. Rtfm: man X! Now you have 3 options: X :1.0 -once -broadcast X :1.0 -indirect otherhost.otherdomain X :1.0 -once -query otherhost.otherdomain :1.0 <- opens at vt8 (<Ctrl>+<Alt>-<F8>) -indirect starts a chooser If you fail, and have a firewall running, try it without the firewall. (See my other mail for my xdmcp & firewall problem) Cheers, Leen
Op maandag 3 maart 2003 00:19, schreef Leendert Meyer:
Is this a bug in kde, or is it something else?? <<== It would be nice to get this confirmed....
You won't find anything changed there... ;-P
Well, I was told by the kdm maintainer.... And it seems obvious that something must change to allow people, remote access. With that "remote Login" button, one get a "remote login" interface. Are you not getting that either Leendert? -- Richard Bos Without a home the journey is endless
On Monday 03 March 2003 09:22, Richard Bos wrote:
Op maandag 3 maart 2003 00:19, schreef Leendert Meyer:
Is this a bug in kde, or is it something else?? <<== It would be nice to get this confirmed....
You won't find anything changed there... ;-P
Well, I was told by the kdm maintainer.... And it seems obvious that something must change to allow people, remote access.
I agree. I have a "Start New Session" menu entry in my K-menu. That is to start a local X login session. Another button to start remote X login sessions. For now we have to do it the old fashioned way. ;-)
With that "remote Login" button, one get a "remote login" interface.
Huh? What "remote login" button? Where can I find it? (Or did you mean it as a wish for future KDE versions?)
Are you not getting that either Leendert?
Not sure what you mean. BTW, any luck with remote X login sessions like I suggested in my previous mail? Cheers, Leen
Op maandag 3 maart 2003 09:48, schreef Leendert Meyer:
On Monday 03 March 2003 09:22, Richard Bos wrote:
Op maandag 3 maart 2003 00:19, schreef Leendert Meyer:
Is this a bug in kde, or is it something else?? <<== It would be nice to get this confirmed....
You won't find anything changed there... ;-P
Well, I was told by the kdm maintainer.... And it seems obvious that something must change to allow people, remote access.
I agree. I have a "Start New Session" menu entry in my K-menu. That is to start a local X login session. Another button to start remote X login sessions.
No it is not in the user session/kmenu. It is in the login manager screen.
For now we have to do it the old fashioned way. ;-)
With that "remote Login" button, one get a "remote login" interface.
Huh? What "remote login" button? Where can I find it? (Or did you mean it as a wish for future KDE versions?)
No no. It should be there now.
Are you not getting that either Leendert?
Not sure what you mean.
See above.
BTW, any luck with remote X login sessions like I suggested in my previous mail?
Still the same story. I now checked with ethereal and I know for sure that XDMCP protocal is established and I would say even works. I e.g. see an Xwilling pkg that shows the load of the machine. I've seen this in an Xwilling script. After that an xdmcp manage message is sent (so no firewall problems too). So the Xsession seems to be transferred to from the remote machine to the local machine, but no more. Could it be that startkde is not run (also because to the local machine I obtain the grey Xsession background, the bg when X is started). -- Richard Bos Without a home the journey is endless
On Monday 03 March 2003 10:14, Richard Bos wrote:
Op maandag 3 maart 2003 09:48, schreef Leendert Meyer:
On Monday 03 March 2003 09:22, Richard Bos wrote:
Op maandag 3 maart 2003 00:19, schreef Leendert Meyer:
Is this a bug in kde, or is it something else?? <<== It would be nice to get this confirmed....
You won't find anything changed there... ;-P
Well, I was told by the kdm maintainer.... And it seems obvious that something must change to allow people, remote access.
I agree. I have a "Start New Session" menu entry in my K-menu. That is to start a local X login session. Another button to start remote X login sessions.
No it is not in the user session/kmenu. It is in the login manager screen.
Could not find it. Could you send me a screenshot in private mail? [...]
BTW, any luck with remote X login sessions like I suggested in my previous mail?
Still the same story. I now checked with ethereal and I know for sure that XDMCP protocal is established and I would say even works. I e.g. see an Xwilling pkg that shows the load of the machine. I've seen this in an Xwilling script. After that an xdmcp manage message is sent (so no firewall problems too).
1. Try it without the firewall. If you use a local network, set IP_FORWARD="yes" in /etc/sysconfig/sysctl and run SuSEconfig. 2. Try it with xdm login instead of kdm login.
So the Xsession seems to be transferred to from the remote machine to the local machine, but no more. Could it be that startkde is not run (also because to the local machine I obtain the grey Xsession background, the bg when X is started).
X :1.0 -once -query 192.168.0.2 -- works -- I get a kdm login dialog X :1.0 -indirect 192.168.0.2 -- does not work, should get a chooser, but X comes 5 times up -- have to kill X with <Ctrl>+<Alt>-<Backspace> X :1.0 -once -broadcast -- works -- I get a watch mouse cursor first, then the kdm login dialog Will check these with xdm login after I've sent this mail. Cheers, Leen
On Monday 03 March 2003 10:40, Leendert Meyer wrote:
On Monday 03 March 2003 10:14, Richard Bos wrote:
Op maandag 3 maart 2003 09:48, schreef Leendert Meyer:
Op maandag 3 maart 2003 00:19, schreef Leendert Meyer:
Is this a bug in kde, or is it something else?? <<== It would be nice to get this confirmed.... [...] BTW, any luck with remote X login sessions like I suggested in my
On Monday 03 March 2003 09:22, Richard Bos wrote: previous mail?
Still the same story. I now checked with ethereal and I know for sure that XDMCP protocal is established and I would say even works. I e.g. see an Xwilling pkg that shows the load of the machine. I've seen this in an Xwilling script. After that an xdmcp manage message is sent (so no firewall problems too).
1. Try it without the firewall. If you use a local network, set IP_FORWARD="yes" in /etc/sysconfig/sysctl and run SuSEconfig.
2. Try it with xdm login instead of kdm login.
I just tried the xdm login, with the firewall off on both machines. This works well! What kind of login dialog appears (xdm/kdm) depends on what is running on the remote machine. [...]
X :1.0 -once -query 192.168.0.2 -- works -- I get a kdm login dialog works with xdm too
X :1.0 -indirect 192.168.0.2 -- does not work, should get a chooser, but X comes 5 times up -- have to kill X with <Ctrl>+<Alt>-<Backspace>
Update: after waiting a bit longer (~ 1 min), a kdm login dialog appears. Still no kdm chooser. With xdm logins on remote machine, I get a xdm chooser! :-) So it seems that the kdm chooser is broken???
X :1.0 -once -broadcast -- works -- I get a watch mouse cursor first, then the kdm login dialog
works with xdm too What still remains is figuring out how to let this work with the firewall ON. Cheers, Leen
Op maandag 3 maart 2003 11:24, schreef Leendert Meyer:
Update: after waiting a bit longer (~ 1 min), a kdm login dialog appears. Still no kdm chooser.
I now waited a bit longer too => X gives an error message that it can't open the display at 192.168.0.2. Which is correct, because there is no machine connected to that IP. I had the number in my /etc/hosts file, but removing it did not solve the problem. I assume it is cached some where, if I can clear the particular cache I'll closer to the solution (I hope).
With xdm logins on remote machine, I get a xdm chooser! :-)
So it seems that the kdm chooser is broken???
-- Richard Bos Without a home the journey is endless
Op maandag 3 maart 2003 12:00, schreef Richard Bos:
Op maandag 3 maart 2003 11:24, schreef Leendert Meyer:
Update: after waiting a bit longer (~ 1 min), a kdm login dialog appears. Still no kdm chooser.
I now waited a bit longer too => X gives an error message that it can't open the display at 192.168.0.2. Which is correct, because there is no machine connected to that IP. I had the number in my /etc/hosts file, but removing it did not solve the problem. I assume it is cached some where, if I can clear the particular cache I'll closer to the solution (I hope).
The problem is the underneath displayed package that is being sent from the source system. Here the source system tell which connections are present. Okay they used to be there but the I've removed the 1st 3 addresses with ifconfig. - ifconfig ippp0/1/2 down route -n shows these routes; Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.4.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.4.1 0.0.0.0 UG 0 0 0 eth0 and ifconfig shows only 1 device (eth0). So I'm wundering where the other 3 connections come, and why they are there. grepping in "/etc" shows only rc.config (suse-7.3) with 192. grepping in /etc/X11/..../..../... for files 192 does not reveal anything. For now I'm lost :( User Datagram Protocol, Src Port: rmiregistry (1099), Dst Port: xdmcp (177) Source port: rmiregistry (1099) Destination port: xdmcp (177) Length: 119 Checksum: 0xa56e (correct) X Display Manager Control Protocol Version: 1 Opcode: Request (0x0007) Message length: 105 Display number: 1 Connections (4) Connection 1: 192.168.0.2 Type: Internet Address: 192.168.0.2 Connection 2: 192.168.1.1 Type: Internet Address: 192.168.1.1 Connection 3: 192.168.2.1 Type: Internet Address: 192.168.2.1 Connection 4: 192.168.4.2 Type: Internet Address: 192.168.4.2 Authentication name: Authentication data (0 bytes) Authorization names (3) Authorization name: MIT-MAGIC-COOKIE-1 Authorization name: XDM-AUTHORIZATION-1 Authorization name: XC-QUERY-SECURITY-1 Manufacturer display ID: -- Richard Bos Without a home the journey is endless
Op maandag 3 maart 2003 10:40, schreef Leendert Meyer:
I agree. I have a "Start New Session" menu entry in my K-menu. That is to start a local X login session. Another button to start remote X login sessions.
No it is not in the user session/kmenu. It is in the login manager screen.
Could not find it. Could you send me a screenshot in private mail?
No, because I don't have it either. I've told that it should be there. It's perhaps time to browse the source code (which I don't have around, so that directs me to webcvs).
[...]
BTW, any luck with remote X login sessions like I suggested in my previous mail?
Still the same story. I now checked with ethereal and I know for sure that XDMCP protocal is established and I would say even works. I e.g. see an Xwilling pkg that shows the load of the machine. I've seen this in an Xwilling script. After that an xdmcp manage message is sent (so no firewall problems too).
1. Try it without the firewall. If you use a local network, set IP_FORWARD="yes" in /etc/sysconfig/sysctl and run SuSEconfig.
It was already set to yes...
2. Try it with xdm login instead of kdm login.
On my todo list. -- Richard Bos Without a home the journey is endless
Op zaterdag 1 maart 2003 22:30, schreef Richard Bos:
Question about the activation of xdmcp in kde and its login manager.
After enabling xdmcp in suse-8.1 in kdmrc in the file: /opt/kde3/share/config/kdm/kdmrc, nothing shows up in kde login manager. Does anyone have succesfully activated this functionality in suse-8.1?
I did a discovery today concerning this problem; Have a look at VT10 (<ctl><alt><f10>) just after starting the X server. I have there log message saying that some kdmrc keys are not recognized. These keys are: [X-:0-Greeter] EnableChooser=true LogSource=/dev/xconsole ShowLog=true loginMode=2 I wunder why they are not recognized. A not much saying snippet of the code (file kdebase/kdm/kfrontend/kdm_config.c): for (i = 0; i < cursec->sect->numents; i++) if ((int)strlen (cursec->sect->ents[i].name) == nlen && !memcmp (cursec->sect->ents[i].name, nstr, nlen)) goto keyok; LogError ("Unrecognized key '%.*s' at %s:%d\n", nlen, nstr, kdmrc, line); goto keyfnd; http://lxr.kde.org/source/kdebase/kdm/kfrontend/kdm_config.c#L760 It would be nice to know what causes this.... -- Richard Bos Without a home the journey is endless
On Saturday 08 March 2003 22:06, Richard Bos wrote:
Op zaterdag 1 maart 2003 22:30, schreef Richard Bos:
Question about the activation of xdmcp in kde and its login manager.
After enabling xdmcp in suse-8.1 in kdmrc in the file: /opt/kde3/share/config/kdm/kdmrc, nothing shows up in kde login manager. Does anyone have succesfully activated this functionality in suse-8.1?
I did a discovery today concerning this problem;
Have a look at VT10 (<ctl><alt><f10>) just after starting the X server. I have there log message saying that some kdmrc keys are not recognized. These keys are:
[X-:0-Greeter] EnableChooser=true LogSource=/dev/xconsole ShowLog=true loginMode=2
I wunder why they are not recognized.
A not much saying snippet of the code (file kdebase/kdm/kfrontend/kdm_config.c): for (i = 0; i < cursec->sect->numents; i++) if ((int)strlen (cursec->sect->ents[i].name) == nlen && !memcmp (cursec->sect->ents[i].name, nstr, nlen)) goto keyok; LogError ("Unrecognized key '%.*s' at %s:%d\n", nlen, nstr, kdmrc, line); goto keyfnd;
http://lxr.kde.org/source/kdebase/kdm/kfrontend/kdm_config.c#L760
It would be nice to know what causes this....
A feature (in development...)? Get ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_8.1/source/kdebase3-3.1-75.src.rpm and have a look at kdebase-3.1/kdm/kfrontend/genkdmconf.c, the generator of kdmrc (yup, same dir as above snippet) kdm only barfs, but doesn't stumble. I think it's nothing to worry about (exciting perhaps). (BTW, kdebase3.spec is very interesting, with all that stuff about suse_version > 811 and kcm_randr... :P about 2 months to go for 8.2 :P...) Cheers, Leen
Op zondag 9 maart 2003 03:02, schreef Leendert Meyer:
It would be nice to know what causes this....
A feature (in development...)?
No, it's ready but to late for kde-3.1 feature freeze => only available in 3.2 :( Or build it yourself it is available now.
Get ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/u pdate_for_8.1/source/kdebase3-3.1-75.src.rpm
and have a look at kdebase-3.1/kdm/kfrontend/genkdmconf.c, the generator of kdmrc (yup, same dir as above snippet)
kdm only barfs, but doesn't stumble. I think it's nothing to worry about (exciting perhaps).
(BTW, kdebase3.spec is very interesting, with all that stuff about suse_version > 811 and kcm_randr... :P about 2 months to go for 8.2 :P...)
Well hopefully SuSE backports this xdmcp stuff from head back to kde-3.1.? -- Richard Bos Without a home the journey is endless
participants (3)
-
Leendert Meyer -
Richard Bos -
Torsten Foertsch