Novell/SuSE development has an updated package in testing that fixed my problem. I would assume it will be available shortly. While I do not have a continuing support package with them yet, they took care of this problem promptly. Consider me one satisfied user. --Kris -----Original Message----- From: freeradius-users-admin@lists.freeradius.org [mailto:freeradius-users-admin@lists.freeradius.org] On Behalf Of Seferovic Edvin Sent: Tuesday, May 24, 2005 11:46 AM To: freeradius-users@lists.freeradius.org Subject: RE: shared secret problem Hi, you welcome ;) If you contact Novell/SuSE and get an answer about this topic ( or maybe a solution ) I would be thankful if you could mail it to this mailing list. I intend to move on SLES shortly, and now when I know the fact that freeRadius is not working ( on x86_64 ) whis move could be delayed. Regards, Edvin Seferovic -----Original Message----- From: freeradius-users-admin@lists.freeradius.org [mailto:freeradius-users-admin@lists.freeradius.org] On Behalf Of Kris Sent: Dienstag, 24. Mai 2005 18:24 To: freeradius-users@lists.freeradius.org Subject: RE: shared secret problem Thanks so much for the information and quick response. I'll attempt to contact Novell/SuSE. I tried the procedure below without much success over the last week or two. -----Original Message----- From: freeradius-users-admin@lists.freeradius.org [mailto:freeradius-users-admin@lists.freeradius.org] On Behalf Of Seferovic Edvin Sent: Tuesday, May 24, 2005 11:17 AM To: freeradius-users@lists.freeradius.org Subject: RE: shared secret problem BINGO... there u go ;) I was using SuSE PRO 9.1 on x86_64 WHICH WAS BROKEN !! SuSE changed this in the next version 9.2. Aparently SLES 9 has the same problem. You could try contacting Novell/SuSe about this ;) Here is a part of a friendly person from this list which encountered the same problem, and solved it : --- cut --- Since, I also got the SuSE 9.2 RPM working on SuSE 9.1 I will include the more detailed instructions below: Well I just got mine working on SuSE 9.1 64 bit. It was one heck of a hack, and probably not done in the correct way, but this is what I did: 1. I grabbed the 9.2 source rpm: freeradius-1.0.0-5.4.src.rpm 2. I ran rpm build --rebuild freeradius-1.0.0-5.4.src.rpm to learn dependencies. I installed the dependencies I could off of the 9.1 distribution. From the 9.2 distribution I installed: libnscd-1.0-2.x86_64.rpm and libzio-0.1-4-0.1-4.x86_64.rpm. 3. I thought I had other issues so I also installed libtool-1.5.8-3.x86_64.rpm and libtool-32bit-9.2-200410061204.x86_64.rpm but they are probably not required from 9.2. 4. I installed the source rpm. 5. I went into /usr/src/packages/SOURCES and bunzipped freeradius-1.0.0.0.tar.bz2 6. I cd'ed into the freeradius-1.0.0.0 directory and in Make.inc I modified the variable LIBLTDL to: LIBLTDL = /usr/lib64/libltdl.so 7. I re-bzipped the directory so the change was stored in the bzipped file. 8. I cd'ed into the /usr/src/packages/SPEC/ directory and ran: rpmbuild -bb freeradius.spec 9. I cd'ed into /usr/src/packages/RPMS/x86_64 and installed the 2 created packages: freeradius-1.0.0-5.4.x86_64.rpm freeradius-devel-1.0.0-5.4.x86_64.rpm 10. eap was still broken so I cd'ed into /usr/src/packages/BUILD/ freeradius-1.0.0/src/modules/rlm_eap/.libs/ 11. I copied rlm_eap-1.0.0.soU to /usr/lib/freeradius 12. I cd'ed into /usr/lib/freeradius and did a ln -s rlm_eap-1.0.0.soU rlm_eap.so --- cut --- Maybe you could just take the RPM package from another SuSE distro and try it. I hope this could help. BTW - I spent over 2 weeks looking for this crapy error. Regards, Edvin Seferovic -----Original Message----- From: freeradius-users-admin@lists.freeradius.org [mailto:freeradius-users-admin@lists.freeradius.org] On Behalf Of Kris Sent: Dienstag, 24. Mai 2005 17:59 To: freeradius-users@lists.freeradius.org Subject: RE: shared secret problem So sorry, I'm using SLES 9 for x86_64 --Kris -----Original Message----- From: freeradius-users-admin@lists.freeradius.org [mailto:freeradius-users-admin@lists.freeradius.org] On Behalf Of Seferovic Edvin Sent: Tuesday, May 24, 2005 10:50 AM To: freeradius-users@lists.freeradius.org Subject: RE: shared secret problem Hi, can you tell us what operating system are you using? I had recently problems with SuSE 9.1 where some packages were broken and therefore the shared secret auth wasn't functioning. Regards, Edvin Seferovic -----Original Message----- From: freeradius-users-admin@lists.freeradius.org [mailto:freeradius-users-admin@lists.freeradius.org] On Behalf Of Kris Sent: Dienstag, 24. Mai 2005 17:38 To: freeradius-users@lists.freeradius.org Subject: shared secret problem If I'm getting a incorrect checksum error on the UDP packet sent from the client to the server, would that be the cause of my "Shared secret is incorrect" error? I've removed/readded the secret on both sides many times... If that is the case, I'm assuming the problem is with the md5 hash on the server and not anything with Freeradius. Is that correct? Thanks, Kris - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html