RE: Blank username/password

2004-01-14 Thread Anson Rinesmith 

Our users file contains the following DEFAULT entry :

You have
DEFAUTL Auth-Type := Accept, Called-Station-Id == 1

DEFAULT Called-Station-ID == 9995551234, Auth-Type := Accept

Is Closer to what you need in your users file



- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

RE: Blank username/password

2004-01-14 Thread Adil Bikarbass 
I've tried this too but with the same result when the username is not
empty it's accepted otherwise it's rejeted,

The problem is with empty usernames/passwords, once again i want to grant
access based on the Called-Station-Id no matter what the username is
(empty username).

Any tips?

Thanks

 On Wed, 14 Jan 2004, Anson Rinesmith wrote:


 Our users file contains the following DEFAULT entry :

 You have
 DEFAUTL Auth-Type := Accept, Called-Station-Id == 1

 DEFAULT Called-Station-ID == 9995551234, Auth-Type := Accept

 Is Closer to what you need in your users file



 -
 List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


-- 
|-Adil Bikarbass
|-IT Manager
|-MTDS S.A.
|-tel +212.3.767.4861
|-fax +212.3.767.4863
|-gsm +212.6.139. 4541
|-14, rue 16 novembre
|-Rabat, Kingdom of Morocco

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

RE: Blank username/password

2004-01-14 Thread Anson Rinesmith 
With the supplied line in your users file, could you send me your relevant
output from radiusd -X, might help debug your problem.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Adil
Bikarbass
Sent: Wednesday, January 14, 2004 10:36 AM
To: [EMAIL PROTECTED]
Subject: RE: Blank username/password

I've tried this too but with the same result when the username is not
empty it's accepted otherwise it's rejeted,

The problem is with empty usernames/passwords, once again i want to grant
access based on the Called-Station-Id no matter what the username is
(empty username).

Any tips?

Thanks

 On Wed, 14 Jan 2004, Anson Rinesmith wrote:


 Our users file contains the following DEFAULT entry :

 You have
 DEFAUTL Auth-Type := Accept, Called-Station-Id == 1

 DEFAULT Called-Station-ID == 9995551234, Auth-Type := Accept

 Is Closer to what you need in your users file



 -
 List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html


-- 
|-Adil Bikarbass
|-IT Manager
|-MTDS S.A.
|-tel +212.3.767.4861
|-fax +212.3.767.4863
|-gsm +212.6.139. 4541
|-14, rue 16 novembre
|-Rabat, Kingdom of Morocco

- 
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

RE: Blank username/password

2004-01-14 Thread Adil Bikarbass 
Well i've noticed after reading the debug that the request with the empty
username did not even hit the radius server (nothing on the debug output)

But when using any character on the username i got some input :

- Begining of Input -

rad_recv: Accounting-Request packet from host my_NAS:1026, id=252,
length=101
Acct-Session-Id = B85D
User-Name = t
NAS-IP-Address = my_NAS
NAS-Port = 45
NAS-Port-Type = ISDN
Acct-Status-Type = Start
Acct-Authentic = RADIUS
Called-Station-Id = 1
Calling-Station-Id = 037680045
Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 194.204.200.232
Acct-Delay-Time = 0
modcall: entering group preacct for request 28
rlm_realm: No '/' in User-Name = t, looking up realm NULL
rlm_realm: No such realm NULL
  modcall[preacct]: module ROAM returns noop for request 28
rlm_realm: No '@' in User-Name = t, looking up realm NULL
rlm_realm: No such realm NULL
  modcall[preacct]: module suffix returns noop for request 28
  modcall[preacct]: module files returns noop for request 28
  modcall[preacct]: module preprocess returns noop for request 28
modcall: group preacct returns noop for request 28
modcall: entering group accounting for request 28
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 = my_NAS,NAS-IP-Address =
my_NAS,Acct-Session-Id = B85D,User-Name = t'
rlm_acct_unique: Acct-Unique-Session-ID = 2dd4757bbb6a253d.
  modcall[accounting]: module acct_unique returns ok for request 28
radius_xlat:  '/var/log/radius/radacct/my_NAS/detail'
rlm_detail: /var/log/radius/radacct/%{Client-IP-Address}/detail expands to
/var/log/radius/radacct/my_NAS/detail
  modcall[accounting]: module detail returns ok for request 28
  modcall[accounting]: module unix returns ok for request 28
radius_xlat:  '/var/log/radius/radutmp'
radius_xlat:  't'
  modcall[accounting]: module radutmp returns ok for request 28
modcall: group accounting returns ok for request 28
Sending Accounting-Response of id 252 to my_NAS:1026
Finished request 28
Going to the next request
Waking up in 6 seconds...

-- End Debug 

My users file contains the following

DEFAUTL Auth-Type := Accept, Called-Station-Id == 1

Please advise

Adil


On Wed, 14 Jan 2004, Anson Rinesmith wrote:

 With the supplied line in your users file, could you send me your relevant
 output from radiusd -X, might help debug your problem.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Adil
 Bikarbass
 Sent: Wednesday, January 14, 2004 10:36 AM
 To: [EMAIL PROTECTED]
 Subject: RE: Blank username/password

 I've tried this too but with the same result when the username is not
 empty it's accepted otherwise it's rejeted,

 The problem is with empty usernames/passwords, once again i want to grant
 access based on the Called-Station-Id no matter what the username is
 (empty username).

 Any tips?

 Thanks

  On Wed, 14 Jan 2004, Anson Rinesmith wrote:

 
  Our users file contains the following DEFAULT entry :
 
  You have
  DEFAUTL Auth-Type := Accept, Called-Station-Id == 1
 
  DEFAULT Called-Station-ID == 9995551234, Auth-Type := Accept
 
  Is Closer to what you need in your users file
 
 
 
  -
  List info/subscribe/unsubscribe? See
 http://www.freeradius.org/list/users.html
 



-- 
|-Adil Bikarbass
|-IT Manager
|-MTDS S.A.
|-tel +212.3.767.4861
|-fax +212.3.767.4863
|-gsm +212.6.139. 4541
|-14, rue 16 novembre
|-Rabat, Kingdom of Morocco

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

RE: Blank username/password

2004-01-14 Thread Dustin Doris 

On Wed, 14 Jan 2004, Adil Bikarbass wrote:

 Well i've noticed after reading the debug that the request with the empty
 username did not even hit the radius server (nothing on the debug output)

 But when using any character on the username i got some input :


I would say that is a problem on your NAS.


 - Begining of Input -

 rad_recv: Accounting-Request packet from host my_NAS:1026, id=252,
 length=101
 Acct-Session-Id = B85D
 User-Name = t
 NAS-IP-Address = my_NAS
 NAS-Port = 45
 NAS-Port-Type = ISDN
 Acct-Status-Type = Start
 Acct-Authentic = RADIUS
 Called-Station-Id = 1
 Calling-Station-Id = 037680045
 Service-Type = Framed-User
 Framed-Protocol = PPP
 Framed-IP-Address = 194.204.200.232
 Acct-Delay-Time = 0
 modcall: entering group preacct for request 28
 rlm_realm: No '/' in User-Name = t, looking up realm NULL
 rlm_realm: No such realm NULL
   modcall[preacct]: module ROAM returns noop for request 28
 rlm_realm: No '@' in User-Name = t, looking up realm NULL
 rlm_realm: No such realm NULL
   modcall[preacct]: module suffix returns noop for request 28
   modcall[preacct]: module files returns noop for request 28
   modcall[preacct]: module preprocess returns noop for request 28
 modcall: group preacct returns noop for request 28
 modcall: entering group accounting for request 28
 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 = my_NAS,NAS-IP-Address =
 my_NAS,Acct-Session-Id = B85D,User-Name = t'
 rlm_acct_unique: Acct-Unique-Session-ID = 2dd4757bbb6a253d.
   modcall[accounting]: module acct_unique returns ok for request 28
 radius_xlat:  '/var/log/radius/radacct/my_NAS/detail'
 rlm_detail: /var/log/radius/radacct/%{Client-IP-Address}/detail expands to
 /var/log/radius/radacct/my_NAS/detail
   modcall[accounting]: module detail returns ok for request 28
   modcall[accounting]: module unix returns ok for request 28
 radius_xlat:  '/var/log/radius/radutmp'
 radius_xlat:  't'
   modcall[accounting]: module radutmp returns ok for request 28
 modcall: group accounting returns ok for request 28
 Sending Accounting-Response of id 252 to my_NAS:1026
 Finished request 28
 Going to the next request
 Waking up in 6 seconds...

 -- End Debug 

 My users file contains the following

 DEFAUTL Auth-Type := Accept, Called-Station-Id == 1

 Please advise

 Adil


 On Wed, 14 Jan 2004, Anson Rinesmith wrote:

  With the supplied line in your users file, could you send me your relevant
  output from radiusd -X, might help debug your problem.
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of Adil
  Bikarbass
  Sent: Wednesday, January 14, 2004 10:36 AM
  To: [EMAIL PROTECTED]
  Subject: RE: Blank username/password
 
  I've tried this too but with the same result when the username is not
  empty it's accepted otherwise it's rejeted,
 
  The problem is with empty usernames/passwords, once again i want to grant
  access based on the Called-Station-Id no matter what the username is
  (empty username).
 
  Any tips?
 
  Thanks
 
   On Wed, 14 Jan 2004, Anson Rinesmith wrote:
 
  
   Our users file contains the following DEFAULT entry :
  
   You have
   DEFAUTL Auth-Type := Accept, Called-Station-Id == 1
  
   DEFAULT Called-Station-ID == 9995551234, Auth-Type := Accept
  
   Is Closer to what you need in your users file
  
  
  
   -
   List info/subscribe/unsubscribe? See
  http://www.freeradius.org/list/users.html
  
 
 

 --
 |-Adil Bikarbass
 |-IT Manager
 |-MTDS S.A.
 |-tel +212.3.767.4861
 |-fax +212.3.767.4863
 |-gsm +212.6.139. 4541
 |-14, rue 16 novembre
 |-Rabat, Kingdom of Morocco

 -
 List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

RE: Blank username/password

2004-01-14 Thread Adil Bikarbass 
I'm running Lucent Postmaster 3 ComOS version 3.9 which is running just
fine

I'll double check the config

Thanks
On Wed, 14 Jan 2004, Dustin Doris wrote:


 On Wed, 14 Jan 2004, Adil Bikarbass wrote:

  Well i've noticed after reading the debug that the request with the empty
  username did not even hit the radius server (nothing on the debug output)
 
  But when using any character on the username i got some input :
 

 I would say that is a problem on your NAS.


  - Begining of Input -
 
  rad_recv: Accounting-Request packet from host my_NAS:1026, id=252,
  length=101
  Acct-Session-Id = B85D
  User-Name = t
  NAS-IP-Address = my_NAS
  NAS-Port = 45
  NAS-Port-Type = ISDN
  Acct-Status-Type = Start
  Acct-Authentic = RADIUS
  Called-Station-Id = 1
  Calling-Station-Id = 037680045
  Service-Type = Framed-User
  Framed-Protocol = PPP
  Framed-IP-Address = 194.204.200.232
  Acct-Delay-Time = 0
  modcall: entering group preacct for request 28
  rlm_realm: No '/' in User-Name = t, looking up realm NULL
  rlm_realm: No such realm NULL
modcall[preacct]: module ROAM returns noop for request 28
  rlm_realm: No '@' in User-Name = t, looking up realm NULL
  rlm_realm: No such realm NULL
modcall[preacct]: module suffix returns noop for request 28
modcall[preacct]: module files returns noop for request 28
modcall[preacct]: module preprocess returns noop for request 28
  modcall: group preacct returns noop for request 28
  modcall: entering group accounting for request 28
  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 = my_NAS,NAS-IP-Address =
  my_NAS,Acct-Session-Id = B85D,User-Name = t'
  rlm_acct_unique: Acct-Unique-Session-ID = 2dd4757bbb6a253d.
modcall[accounting]: module acct_unique returns ok for request 28
  radius_xlat:  '/var/log/radius/radacct/my_NAS/detail'
  rlm_detail: /var/log/radius/radacct/%{Client-IP-Address}/detail expands to
  /var/log/radius/radacct/my_NAS/detail
modcall[accounting]: module detail returns ok for request 28
modcall[accounting]: module unix returns ok for request 28
  radius_xlat:  '/var/log/radius/radutmp'
  radius_xlat:  't'
modcall[accounting]: module radutmp returns ok for request 28
  modcall: group accounting returns ok for request 28
  Sending Accounting-Response of id 252 to my_NAS:1026
  Finished request 28
  Going to the next request
  Waking up in 6 seconds...
 
  -- End Debug 
 
  My users file contains the following
 
  DEFAUTL Auth-Type := Accept, Called-Station-Id == 1
 
  Please advise
 
  Adil
 
 
  On Wed, 14 Jan 2004, Anson Rinesmith wrote:
 
   With the supplied line in your users file, could you send me your relevant
   output from radiusd -X, might help debug your problem.
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On Behalf Of Adil
   Bikarbass
   Sent: Wednesday, January 14, 2004 10:36 AM
   To: [EMAIL PROTECTED]
   Subject: RE: Blank username/password
  
   I've tried this too but with the same result when the username is not
   empty it's accepted otherwise it's rejeted,
  
   The problem is with empty usernames/passwords, once again i want to grant
   access based on the Called-Station-Id no matter what the username is
   (empty username).
  
   Any tips?
  
   Thanks
  
On Wed, 14 Jan 2004, Anson Rinesmith wrote:
  
   
Our users file contains the following DEFAULT entry :
   
You have
DEFAUTL Auth-Type := Accept, Called-Station-Id == 1
   
DEFAULT Called-Station-ID == 9995551234, Auth-Type := Accept
   
Is Closer to what you need in your users file
   
   
   
-
List info/subscribe/unsubscribe? See
   http://www.freeradius.org/list/users.html
   
  
  
 
  --
  |-Adil Bikarbass
  |-IT Manager
  |-MTDS S.A.
  |-tel +212.3.767.4861
  |-fax +212.3.767.4863
  |-gsm +212.6.139. 4541
  |-14, rue 16 novembre
  |-Rabat, Kingdom of Morocco
 
  -
  List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
 

 -
 List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


-- 
|-Adil Bikarbass
|-IT Manager
|-MTDS S.A.
|-tel +212.3.767.4861
|-fax +212.3.767.4863
|-gsm +212.6.139. 4541
|-14, rue 16 novembre
|-Rabat, Kingdom of Morocco

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

RE: Blank username/password

2004-01-14 Thread Adil Bikarbass 
My NAS config seems to be OK

Nothing special in it, i specified the radius server and the shared secret

So i'm wondering what's wrong and why i'm not getting anything in the logs
if there is an empty username

any other ideas?

Adil

On Wed, 14 Jan 2004, Dustin Doris wrote:


 On Wed, 14 Jan 2004, Adil Bikarbass wrote:

  Well i've noticed after reading the debug that the request with the empty
  username did not even hit the radius server (nothing on the debug output)
 
  But when using any character on the username i got some input :
 

 I would say that is a problem on your NAS.


  - Begining of Input -
 
  rad_recv: Accounting-Request packet from host my_NAS:1026, id=252,
  length=101
  Acct-Session-Id = B85D
  User-Name = t
  NAS-IP-Address = my_NAS
  NAS-Port = 45
  NAS-Port-Type = ISDN
  Acct-Status-Type = Start
  Acct-Authentic = RADIUS
  Called-Station-Id = 1
  Calling-Station-Id = 037680045
  Service-Type = Framed-User
  Framed-Protocol = PPP
  Framed-IP-Address = 194.204.200.232
  Acct-Delay-Time = 0
  modcall: entering group preacct for request 28
  rlm_realm: No '/' in User-Name = t, looking up realm NULL
  rlm_realm: No such realm NULL
modcall[preacct]: module ROAM returns noop for request 28
  rlm_realm: No '@' in User-Name = t, looking up realm NULL
  rlm_realm: No such realm NULL
modcall[preacct]: module suffix returns noop for request 28
modcall[preacct]: module files returns noop for request 28
modcall[preacct]: module preprocess returns noop for request 28
  modcall: group preacct returns noop for request 28
  modcall: entering group accounting for request 28
  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 = my_NAS,NAS-IP-Address =
  my_NAS,Acct-Session-Id = B85D,User-Name = t'
  rlm_acct_unique: Acct-Unique-Session-ID = 2dd4757bbb6a253d.
modcall[accounting]: module acct_unique returns ok for request 28
  radius_xlat:  '/var/log/radius/radacct/my_NAS/detail'
  rlm_detail: /var/log/radius/radacct/%{Client-IP-Address}/detail expands to
  /var/log/radius/radacct/my_NAS/detail
modcall[accounting]: module detail returns ok for request 28
modcall[accounting]: module unix returns ok for request 28
  radius_xlat:  '/var/log/radius/radutmp'
  radius_xlat:  't'
modcall[accounting]: module radutmp returns ok for request 28
  modcall: group accounting returns ok for request 28
  Sending Accounting-Response of id 252 to my_NAS:1026
  Finished request 28
  Going to the next request
  Waking up in 6 seconds...
 
  -- End Debug 
 
  My users file contains the following
 
  DEFAUTL Auth-Type := Accept, Called-Station-Id == 1
 
  Please advise
 
  Adil
 
 
  On Wed, 14 Jan 2004, Anson Rinesmith wrote:
 
   With the supplied line in your users file, could you send me your relevant
   output from radiusd -X, might help debug your problem.
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On Behalf Of Adil
   Bikarbass
   Sent: Wednesday, January 14, 2004 10:36 AM
   To: [EMAIL PROTECTED]
   Subject: RE: Blank username/password
  
   I've tried this too but with the same result when the username is not
   empty it's accepted otherwise it's rejeted,
  
   The problem is with empty usernames/passwords, once again i want to grant
   access based on the Called-Station-Id no matter what the username is
   (empty username).
  
   Any tips?
  
   Thanks
  
On Wed, 14 Jan 2004, Anson Rinesmith wrote:
  
   
Our users file contains the following DEFAULT entry :
   
You have
DEFAUTL Auth-Type := Accept, Called-Station-Id == 1
   
DEFAULT Called-Station-ID == 9995551234, Auth-Type := Accept
   
Is Closer to what you need in your users file
   
   
   
-
List info/subscribe/unsubscribe? See
   http://www.freeradius.org/list/users.html
   
  
  
 
  --
  |-Adil Bikarbass
  |-IT Manager
  |-MTDS S.A.
  |-tel +212.3.767.4861
  |-fax +212.3.767.4863
  |-gsm +212.6.139. 4541
  |-14, rue 16 novembre
  |-Rabat, Kingdom of Morocco
 
  -
  List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
 

 -
 List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


-- 
|-Adil Bikarbass
|-IT Manager
|-MTDS S.A.
|-tel +212.3.767.4861
|-fax +212.3.767.4863
|-gsm +212.6.139. 4541
|-14, rue 16 novembre
|-Rabat, Kingdom of Morocco

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: Blank username/password

2004-01-14 Thread Adil Bikarbass 
Here is what i got on my PM3 when trying to connect using an empty
username

 Begin of output --

S3: LCP Open
Received UNKNOWN on port S3 of 14 bytes containing:wire bytes 18
0c 03 00 12 67 6e 33 3c 4d 53 52 41 53 56 35 2e
31 30
Received UNKNOWN on port S3 of 24 bytes containing:wire bytes 28
0c 04 00 1c 67 6e 33 3c 4d 53 52 41 53 2d 31 2d
50 43 41 42 44 45 4c 4d 41 4a 49 44
Received PAP_AUTH_REQ on port S3 of 6 bytes containing:
01 01 00 06 00 00
Sending PAP_AUTH_NAK on port S3 of 14 bytes containing:wire bytes 18
03 01 00 12 0d 49 6e 76 61 6c 69 64 20 4c 6f 67
69 6e
Received LCP_TERMINATE_REQUEST on port S3 of 12 bytes containing:wire
bytes 16
05 05 00 10 67 6e 33 3c 00 3c cd 74 00 00 02 b3

Sending LCP_TERMINATE_ACK on port S3 of 0 bytes containing:wire bytes 4
06 02 00 04

-- end of output 


And here is what i got when i use a username like hi :

 begin of output ---

Received LCP_CONFIGURE_REQUEST on port S2 of 16 bytes containing:wire
bytes 20
01 02 00 14 02 06 00 00 00 00 05 06 14 14 1b 12
07 02 08 02
Sending LCP_CONFIGURE_ACK on port S2 of 16 bytes containing:wire bytes 20
02 02 00 14 02 06 00 00 00 00 05 06 14 14 1b 12
07 02 08 02
S2: LCP Open
Received UNKNOWN on port S2 of 14 bytes containing:wire bytes 18
0c 03 00 12 14 14 1b 12 4d 53 52 41 53 56 35 2e
31 30
Received UNKNOWN on port S2 of 18 bytes containing:wire bytes 22
0c 04 00 16 14 14 1b 12 4d 53 52 41 53 2d 31 2d
55 53 45 52 2d 31
Received PAP_AUTH_REQ on port S2 of 16 bytes containing:
01 00 00 10 04 6a 6f 63 6b 06 66 73 74 6f 6e 65

Sending PAP_AUTH_ACK on port S2 of 16 bytes containing:wire bytes 20
02 00 00 14 0f 4c 6f 67 69 6e 20 53 75 63 63 65
65 64 65 64

--- end of output --

Seems like my PM3 is sending a Not acking for some reason when it gets
empty usernames

Still investigating


Adil


On Wed, 14 Jan 2004, Alan DeKok wrote:

 Adil Bikarbass [EMAIL PROTECTED] wrote:
  So i'm wondering what's wrong and why i'm not getting anything in the logs
  if there is an empty username

   You're getting nothing in the logs because the NAS isn't sending any
 packets to FreeRADIUS.

   Alan DeKok.

 -
 List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html


-- 
|-Adil Bikarbass
|-IT Manager
|-MTDS S.A.
|-tel +212.3.767.4861
|-fax +212.3.767.4863
|-gsm +212.6.139. 4541
|-14, rue 16 novembre
|-Rabat, Kingdom of Morocco

- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: Blank username/password

2004-01-14 Thread Alan DeKok 
Adil Bikarbass [EMAIL PROTECTED] wrote:
 Received PAP_AUTH_REQ on port S3 of 6 bytes containing:
 01 01 00 06 00 00
 Sending PAP_AUTH_NAK on port S3 of 14 bytes containing:wire bytes 18

  So the request is being reject by the PPP software, and it's not
even sending a RADIUS request.

  There is nothing you can do to the RADIUS server to fix this
problem.  Ask your NAS vendor what to do.

  Alan DeKok.


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html