> Is radius 2.0 needed for PM3???
No, we run Radius 1.16 just fine right now. But, you do lose some
functionality, like the ability to limit calls to ISDN vice analog,
session limits, number of connects on MLPPP, etc. Plus the new RADIUS
allows menus, dbm format user database, prefix/suffix, multiple defaults,
etc. We are going to it, just waiting a little longer for any problems
to show up and get resolved (also waiting for ComOS 3.5 on the PM-2e's
to be released so that PM code bases are similar) One of the things
that Livingston (IMHO) has miscalculated on is that even on sites that
DO now have some PM-3's in their installed base, some of the features will
not be tested/ironed out until ComOS 3.5 for PM-2e's is released. We
are not about to run OSPF on our PM-3 until it is available for testing
with the corresponding PM-2's and/or IRX's. I would prefer not to run
a mixed bag of OSPF/RIP as my interior routing protocols.
> We presently run ESVA version. How close is version 2.0 to this??
Probably not very. Although, I'm sure some of the ideas of ESVA (and
Merit) cross-pollenated to RADIUS 2.0. RADIUS 2.0 follows the RADIUS RFC.
Unfortunately, since it is essentially stateless, it does not prevent
multiple simultaneous logins. I would like to see the hack to 2.0 to
accomplish this, even if Livingston can't officially support it.