Well, I have it working, at least it appears to be, but I am still not
getting an ip on the laptop -- do I need to pass the dhcp server somewhere?
Sorry if I don't understand this stuff as well as you do, please be patient
with me.




rad_recv: Access-Request packet from host 216.139.200.5:59452, id=49,
length=147
        User-Name = "cdukes"
        Framed-MTU = 1400
        Called-Station-Id = "000f.8f76.2e20"
        Calling-Station-Id = "0006.25a9.8594"
        Message-Authenticator = 0xf7b2bde25d17ea027b4f0b283a60cdae
        EAP-Message = 0x0202000b016364756b6573
        NAS-Port-Type = Wireless-802.11
        NAS-Port = 378
        State = 0x92f333abdd073fa963f08d534129f7a4
        Service-Type = Framed-User
        NAS-IP-Address = 10.100.10.10
        NAS-Identifier = "ap-noc"
  Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 4
  modcall[authorize]: module "preprocess" returns ok for request 4
  modcall[authorize]: module "chap" returns noop for request 4
  modcall[authorize]: module "mschap" returns noop for request 4
    rlm_realm: No '@' in User-Name = "cdukes", looking up realm NULL
    rlm_realm: No such realm "NULL"
  modcall[authorize]: module "suffix" returns noop for request 4
  rlm_eap: EAP packet type response id 2 length 11
  rlm_eap: No EAP Start, assuming it's an on-going EAP conversation
  modcall[authorize]: module "eap" returns updated for request 4
    users: Matched DEFAULT at 152
    users: Matched DEFAULT at 171
    users: Matched cdukes at 215
  modcall[authorize]: module "files" returns ok for request 4
modcall: group authorize returns updated for request 4
  rad_check_password:  Found Auth-Type EAP
auth: type "EAP"
  Processing the authenticate section of radiusd.conf
modcall: entering group authenticate for request 4
  rlm_eap: EAP Identity
  rlm_eap: processing type tls
 rlm_eap_tls: Requiring client certificate
  rlm_eap_tls: Initiate
  rlm_eap_tls: Start returned 1
  modcall[authenticate]: module "eap" returns handled for request 4
modcall: group authenticate returns handled for request 4
Sending Access-Challenge of id 49 to 216.139.200.5:59452
        Framed-IP-Address = 255.255.255.254
        Framed-MTU = 576
        Service-Type = Framed-User
        EAP-Message = 0x010300060d20
        Message-Authenticator = 0x00000000000000000000000000000000
        State = 0x45e0bb69aebe14a82b34c32a696e3a8f
Finished request 4
Going to the next request
Waking up in 6 seconds...


 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alan DeKok
Sent: Friday, April 23, 2004 4:31 PM
To: [EMAIL PROTECTED]
Subject: Re: Cisco 1100 AP and XP Client using tls (PEAP) 

"Clayton Dukes" <[EMAIL PROTECTED]> wrote:
> Sorry, I must have misunderstood. Forgive me...If I turn off LDAP in 
> the authenticate section,

  Did I say to do that?  No.  Go back and read what I said.

  If you're retrieving passwords from the LDAP directory, then setting
Auth-Type := LDAP is not only redundant, it ensures that CHAP, MS-CHAP, and
PEAP authentication won't ever work.  In addition, it increases the load on
your LDAP server, for no point.

  If you're not retrieving passwords from LDAP, then CHAP, MS-CHAP, and PEAP
won't *ever* work.  Only PAP authentication will work.

  Don't set Auth-Type := LDAP.

  Please READ my responses, and don't read into them your interpretation of
what you think I meant to say.

  Alan DeKok.

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


!DSPAM:40897a14247361853017648!




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

Reply via email to