Re: mschap and ldap auth-type together no more working

-CHAP I believe that mschap or MS-CHAP makes the difference. Dominique Alan DeKok a écrit : LALOT Dominique wrote: Before, I was able to do LDAP or MSCHAP automatically. I had and entry in users lalot Auth-Type := ldap That will prevent MS-CHAP from working. See: http

Re: mschap and ldap auth-type together no more working

I cleaned the auth-type in users file. Everything is OK now on freeradius side. My second problem is the NAS sending a null port. That's not a freeradius problem. Thanks Dom LALOT Dominique a écrit : Sorry, I didn't see your answer. I just got it via the archives. I explain a little bit

mschap and ldap auth-type together no more working

Hello, I had a problem with ippool, but it is a NAS problem. I wanted to do further checks so I upgrade to newer versions: freeradius 1.0.2-4sarge3 stable (I come from this one) freeradius 1.1.3-3 testing freeradius 1.1.2-1bpo1 sarge-backports Before, I was able to do

Re: groupmembership_filter

I noticed too, there is no scope in the ldap configuration. It's time consuming for nothing. I know what the DN is and found no way to avoid the search uid=xxx There's some little improvements todo I think. Tomasz Wolniewicz a crit : I am using the groupmembership_attribute to add users to

rlm-ippool questions

Hello, I've changed ldap.attrmap to include: checkItem Pool-Name supannaffectation That item is case insensitive as an ldap search 1. I have to check now all the values of suppannaffectation to see if it's case sensitive. Is there a way to tell rlm_ippool to compare

Re: rlm_ippool - not releasing ip addresses

Kostas Kalevras a écrit : I have some scripts here which will process a ip pool file (using rlm_ippool_tool) against radwho or a radacct table, which I used to clean out rm_ippool's data every so often. The problem is that any non-FreeRADIUS modification of the database needs to be done while

Re: help groups and LDAP

Ldap-Group, so it just does an LDAP lookup, not specifically matching on groups. This should pool the supannafecction attribute from ldap and make that the Pool-Name check item, which should then fire ippool. -Dusty Doris On Thu, 18 Nov 2004, LALOT Dominique wrote: Thanks for all, be

Re: help groups and LDAP

It does not work either, may be I should avoid pools for default IP settings?. I put a value toto in supannaffectation which does not exist as a pool name Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module preprocess

Re: help groups and LDAP

will all output. ie: accounting { ... u2labo u3labo ... } post_auth { ... u2labo u3labo ... } On Wed, 17 Nov 2004, LALOT Dominique wrote: Thanks, I have to leave, but the quick and last test I did with your advice, gave me bad results. See tomorrow.. Using radtest, I don't get any IP

Re: help groups and LDAP

that to the list will all output. ie: accounting { ... u2labo u3labo ... } post_auth { ... u2labo u3labo ... } On Wed, 17 Nov 2004, LALOT Dominique wrote: Thanks, I have to leave, but the quick and last test I did with your advice, gave me bad results. See tomorrow.. Using radtest, I don't get any IP

help groups and LDAP

Hello all, I've spent quite a long time trying to understand how freeradius works and trying to get everything I want working. I am using Openldap since 2001 and I've no problems to understand LDAP as I wrote many programs around LDAP. In fact I don't understand how groups are working under

Re: help groups and LDAP

Thanks, I have to leave, but the quick and last test I did with your advice, gave me bad results. See tomorrow.. Using radtest, I don't get any IP, and there is very little doc about ippool and the way it works. I suppose that the NAS is completely relying on radius for IP delivery. I'm