Hello,
> This is probably due to your user definition above, which for a Cisco should
> include a Service-Type = Framed-User reply item. Cisco's are very picky about
> this. There have been several discussions about this on the list and you should
> be able to find the references on the archive site.
Eeks sorry, i had been browsing around the last three months of archive,
but hadn't found anything pointing to that. (and i had the idea that i put
that statement in the default reply items)
It actually doesn't complain about the appropriate type anymore, but now
it whines about this :
--<snip>--
4d21h: Se0:0 AAA/AUTHOR/LCP: Processing AV interface-config=ip address
192.168.121.133 255.255.255.224
--<snip>--
4d21h: Vi1 AAA/AUTHOR/FSM: (0): LCP succeeds trivially
--<snip>--
4d21h: Vi1 AAA/AUTHOR/FSM (2029435040): Method=radius (radius)
4d21h: RADIUS: cisco AVPair "lcp:interface-config=ip address
192.168.121.133 255.255.255.224" not applied for ip
4d21h: Vi1 AAA/AUTHOR (2029435040): Post authorization status = PASS_REPL
4d21h: Vi1 AAA/AUTHOR/FSM: We can start IPCP
4d21h: Vi1 AAA/AUTHOR/IPCP: Start. Her address 192.168.240.22, we want
0.0.0.0
--<snip>--
"not applied for ip".. i'm digging into that rightnow..
Greets,
Nils Swart - [EMAIL PROTECTED]
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
