Hi, me again...
I've enabled Debugging Mode, but I'm still running in circles...
HERE IS THE DEBUGGING LOG:
Waking up in 6 seconds...
rad_recv: Accounting-Request packet from host 196.1.2.3:1646, id=225,
length=139
NAS-IP-Address = 196.1.2.3
NAS-Port = 20203
NAS-Port-Type = ISDN
User-Name = "schalk"
Called-Station-Id = "1200"
Calling-Station-Id = "01509"
Acct-Status-Type = Stop
Acct-Authentic = RADIUS
Service-Type = Framed-User
Acct-Session-Id = "0000A870"
Framed-Protocol = PPP
Acct-Terminate-Cause = User-Request
Acct-Input-Octets = 126
Acct-Output-Octets = 96
Acct-Input-Packets = 6
Acct-Output-Packets = 6
Acct-Session-Time = 0
Acct-Delay-Time = 0
modcall: entering group preacct for request 4
modcall[preacct]: module "preprocess" returns noop for request 4
rlm_realm: No '@' in User-Name = "schalk", looking up realm NULL
rlm_realm: No such realm "NULL"
modcall[preacct]: module "suffix" returns noop for request 4
modcall[preacct]: module "files" returns noop for request 4
modcall: group preacct returns noop for request 4
modcall: entering group accounting for request 4
rlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request,
unique
ID MAY be inconsistent
rlm_acct_unique: Hashing ',Client-IP-Address = 196.1.2.3,NAS-IP-Address =
196.1.2.3,Acct-Session-Id = "0000A870",User-Name = "schalk"'
rlm_acct_unique: Acct-Unique-Session-ID = "cdb77c9d4".
modcall[accounting]: module "acct_unique" returns ok for request 4
radius_xlat: '/var/log/radacct/196.1.2.3/detail-20040314'
rlm_detail: /var/log/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to
/var/
log/radacct/196.1.2.3/detail-20040314
modcall[accounting]: module "detail" returns ok for request 4
modcall[accounting]: module "unix" returns ok for request 4
radius_xlat: '/var/log/radutmp'
radius_xlat: 'schalk'
modcall[accounting]: module "radutmp" returns ok for request 4
modcall: group accounting returns ok for request 4
Sending Accounting-Response of id 225 to 196.1.2.3:1646
Finished request 4
The REALM does not make any difference, even when I try to add the REALM in
the Username.
CHAP authentication still fails, and PAP authentication times out.
Any ideas?
Regards
Schalk
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Alan
DeKok
Sent: 13 March 2004 09:36 PM
To: [EMAIL PROTECTED]
Subject: Re: ISDN Authentication problems - URGENT
"Schalk Erasmus - IGN" <[EMAIL PROTECTED]> wrote:
> Here are the first part of my "USERS" config file:
>
> DEFAULT Fall-Through = no
I have no clue what you think this does.
Delete that line. It's wrong.
> # Analog users
>
> DEFAULT Fall-Through = Yes
Again, this line is completely wrong. Delete it.
> HERE ARE THE RADIUS LOGS:
...
These are not the debug logs. Run the server in debugging mode, as
suggested in the FAQ, README, and pretty much all of the documentation
files.
> Sat Mar 13 20:22:47 2004 : Auth: Login incorrect (rlm_chap: Clear text
> password not available): [isdn/<CHAP-Password>] (from client NAS2 port
20324
What part of that message is not clear?
Alan DeKok.
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
