[cisco-nas] Asynchronous callback problems
    Andris Zarins 
    andris.zarins at microlink.lv
       
    Thu Jul 14 11:10:03 EDT 2005
    
    
  
Hi all,
 
I'm trying to configure callback from 3640 (E1) to WindowsXP PC (async line). There are several types of users callin to that NAS - Cisco routers using ISDN, async modem users who shouldnt be called back, and now there should be async modem users who should be called back. This is why I need per user AAA what is done using RADIUS. Below is RADIUS profile configuration. 
 
 
NAS (3640) has numerous mica-midems installed. Dial-in without callback is working fine, as AAA is done using RADIUS server, so configuration for vaccess interfaces comes also from vtemplate + RADIUS part.  
 
Here is configuration from NAS:
 
interface Group-Async1
 description Dial-in modem pool
 ip unnumbered Loopback2
 encapsulation ppp
 no ip route-cache cef
 no ip route-cache
 ip tcp header-compression
 no ip mroute-cache
 dialer in-band
 dialer idle-timeout 9000
 dialer-group 1
 async mode dedicated
 peer default ip address pool dial-up
 no fair-queue
 ppp authentication chap modem
 no clns route-cache
 group-range 33 56
 
And here is profile from RADIUS for involved user:
 
Profile="callback"
            Framed-Protocol = PPP
            Service-Type = Framed-User
            cisco-avpair = "lcp:interface-config=ppp callback accept"
            cisco-avpair = "lcp:interface-config=ip unnumbered lo2"
            cisco-avpair = "lcp:interface-config=peer default ip address pool dial-up"
            cisco-avpair = "lcp:interface-config=encaps ppp"
            cisco-avpair = "lcp:interface-config=ppp multilink"
 
 
What I'm worried about is command "ppp callback accept". As far as I know - it should be configured on group-async interface, but if I do it - nobody is able to call-in in any manner (with callback or without). "debug aaa authentication" says that user isn't authorized for callback and AAA procedure exits at that moment (or maybe I'm not doin enough debugging, so Im missin something). 
 
Any ideas how to proceed and what to troubleshoot? Maybe anyone has got working configuration for callback? Any ideas what to debug? I understand that there might be not enough information, if you need something else to give some comments - I'll do it :-)
 
Andris
 
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-nas/attachments/20050714/fcae3d8a/attachment.html
    
    
More information about the cisco-nas
mailing list