I opened this as an RFE, but I think we're already looking into this as
several European customers have asked for it.
>2. A way to differentiate K56flex frm 33.6k or lower asynchronous calls at
>auth time (even if it requires "watching" for a combination of attributes
>inside the RADIUS server).
There will be a connect speed reported - but I'm not sure if it is sent in
the auth req. I sent it to RFE just to be safe.
>Q: Since I don't see a place to set version 1 or 2, can I assume that ComOS
>3.5 is RIPv2 capable in a "compatibility" sort of setup--it broadcasts and
>accepts both versions? Or is it still RIPv1 only?
RIPv1. We stopped development on v2. We pretty much had it done but with
the release of working OSPF the demand completely evaporated. And since
we feel OSPF is a *far* superior solution in any case, we did not have
an engineering justification to continue with RIP development. Should there
be sufficient demand we could continue, but at this time there isn't.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588