Thanks very much... I figured that out just a little while ago.... Appreciate it...;)
Paul -----Original Message----- From: Oliver Boehmer (oboehmer) [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 14, 2007 1:55 PM To: Paul Stewart; [email protected] Subject: RE: [c-nsp] 5350XM Config Paul Stewart <> wrote on Tuesday, August 14, 2007 4:36 PM: > Hey folks.... I'm puzzled why this configuration isn't working and > looking for a 'second set of eyes'...;) > > Incoming T1 is 24X56K and the modems are answering but cannot > authenticate... something is missing but not sure what it is... > > Any help appreciated... relevant parts below... > > aaa authentication login default group tacacs+ enable aaa > authentication ppp Nexicom group Nexicom aaa authorization network > Nexicom group Nexicom [...] > ! > interface Group-Async0 > ip unnumbered Loopback0 > encapsulation ppp > no ip mroute-cache > async mode dedicated > peer default ip address pool pool_dialup ppp authentication pap > callin group-range 1/00 1/107 ! for modem calls, authentication and authorization settings are specified on the group-async interface, the Dialer configuration is not used. So you're missing a ppp authentication pap callin Nexicom ppp authorization Nexicom on your Group-async0 interface in order to perform Radius authen/author. You could also just configure aaa authen ppp default group Nexicom aaa author network default group Nexicom then you don't need to specify the named methods on the interface(s).. If this doesn't work, please enable "debug ppp authentication" and check what's happening. You should at least see ppp starting.. oli _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
