|
Yes,
I'd like to reinforce one of Gildas' points:
'Service-Type = Framed-User',
'Framed-Protocol = PPP'
While
our USR/3Com NASes will work fine if these "standard" Reply items are omitted,
our Cisco NAS does not, so we had to state them explicitly.
Dave
:)
Hi
Arslan,
I
succeeded to make Cisco 5300 working with Radiator. You need the following
lines on Cisco to make IP address reservation :
aaa
new-model
aaa authentication ppp wap group radius
aaa authorization
network default group radius
aaa accounting update newinfo
aaa
accounting network wap start-stop group radius
interface Group-Async0
ip unnumbered Ethernet0
no ip
directed-broadcast
encapsulation ppp
async dynamic
address
async mode interactive
ppp authentication chap pap
wap
ppp accounting wap
group-range 1 60
hold-queue
10 in
radius-server host <IP> auth-port 1645 acct-port 1646 key
<KEY>
user
profile should returned 'Service-Type = Framed-User', 'Framed-Protocol =
PPP' and 'Framed-IP-Address' attributes.
Good
luck.
Gildas.
Hi,
We are facing problem in radiator
implementation with Cisco AS5300 NAS. It seems that Cisco NAS is really
picky in understanding attributes replied by radiator; like IP address
reservation , session-timeout etc. I have checked the configuration of both
NAS and radiator and all look good. Radiator is correctly replying
attrbutes but NAS somehow does not implement them. We were
using Tacacs+ earlier and it worked fine with Cisco. If anyone of you
have implemented radiator with Cisco , please suggest some
solution.
kind regards,
arslan.
|
