[cisco-nas] RE: Framed-Route syntax change in 12.3?
Oliver Boehmer (oboehmer)
oboehmer at cisco.com
Fri Jul 9 05:20:45 EDT 2004
Hi Rainer,
> Oliver Boehmer (oboehmer) wrote:
>>> did the Framed-Route syntax in 12.3.6a change? We've started to get
>>> the following message for a bunch of backup dialins:
>>>
>>> %AAA-3-PARSEERR: Error(2) parser is unable to parse IP route
>>> 192.168.1.0 255.255.255.0 150 per-user command
>>>
>>> This used to work fine with 12.1, 12.1T, 12.2 on as5300. I couldn't
>>> find any syntax description searching cisco.com.
>>
>> The whole AAA infrastructure has been re-written in 12.2T/12.3, but
>> this should be (more or less) transparent. Can you post "debug
>> radius", "deb aaa author" and "deb aaa per-user" (or send it
>> unicast) to check how the framed-route arrives and how it is being
>> processed.
>
> Jepp, here it comes - let me know if I've x-ed out too much:
[...]
> Framed-Route [22] 22 "192.168.1.0/29 150"
> Framed-Route [22] 23 "192.168.2.0/29 150"
While RFC doesn't really define a format, most implementations
(including ours) adhere to
route mask [gateway [metric]]
If you don't want to specify a gateway, but want to use a metric, please
send 0.0.0.0 ("0" might also work) as gateway
"192.168.1.0/29 0.0.0.0 150"
Why did it work in 12.2 and earlier? The parsing routine was a bit
different in the old code. Should it work in 12.3 as well? I think so,
we're currently working on this routine (via CSCee92890), will alert the
engineer of this inconsistency as well, maybe we can work something out.
Tx,
oli
More information about the cisco-nas
mailing list