No summarization.
>They are not directly connected interfaces (The route is advertised whether
>or not the user has dialled in).
No, I said I had a similar problem, not the same problem. The thing is that
we have users with static IP addresses - a lot, and I'd like to put all
PM3's in one NSSA, and summarize the range of static IP addresses on the
area border router. Right now everytime a user with a static IP logs in or
out it causes routing updates through the entire network.
If you read carefully, I wrote:
>> There is a bug or misfeature in ComOS wrt OSPF route advertizements-
>> static IP numbers (assigned by RADIUS) outside of the "pool"
>> are announced
>> by ComOS as "External type 2". This happens even if the area
>> defined on the
>> portmaster includes the range in which this IP number falls.
>>
>> This IMO is a bug - an interface route should always be advertized as
>> "intra-area". Also it would be nice if this would happen for
>> static routes
>> assigned by radius as well (if they fall into the defined range
>> of the area).
Note that the answer from Lucent was:
>> According to my information about OSPF, when you assign
>> pools/routes to PM products and defind the ospf area's
>> you also need to implement the static ip's in these area's
>> else the PM will always advertise those routes as external
>> type 2.
So if I do:
set ospf area 0.0.0.1 range 195.64.64.0/19
it should advertize the routes for users with a static IP within that
range as intra-area just like it advertizes the pool, yet it doesn't!
Mike.
-- Indifference will certainly be the downfall of mankind, but who cares?-- The From: and Reply-To: addresses are internal news2mail gateway addresses. Reply to the list or to miquels@cistron.nl (Miquel van Smoorenburg) - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>