That feature description doesn't sound to me as though it will solve
the problem completely. What about staticly assigned addresses? Not
all of us use OSPF to do this.
In our case, we assign IP addresses from different subnets depending
on the user. ComOS does not provide a way to aggregate those routes,
so with OSPF on we end up with a /32 for every dialup user propagating
to all of our routing tables. Yuck.
So I think this problem should be fixed more generically at the routing
rather than the NAS layer -- we really just need something like Cisco's
"ip route 1.1.1.64 255.255.255.192 null0" to create a backup deadend
route.
Note that this feature should also tell OSPF to aggregate -- it should
advertise 1.1.1.64/26 rather than 1.1.1.65/32, 1.1.1.66/32, etc.
-- Marc Rouleau
VP and Chief Technology Officer Voice: (812) 456.1226 Fax: (812) 461.3363
Community Telephone Corporation http://www.communitytelephone.com
-
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/>