OR-M (functionality & opinions)

Timothy Deem (tdeem2@alpha.comsource.net)
Fri, 1 Nov 1996 11:16:38 -0600 (CST)

I'm looking at the OR-M as a potential solution for a customer and
have a few questions:

The unit has a single async port and a PCMCIA slot -- I'm presuming
they are both usable simultaneously giving you the potential for a dual
dial-up connection -- is that correct? Or do they act like the ethernet
options (BNC/AUI/TP) on the PM's where they are mutually exclusive?

Regardless of the first question, my second question has to do
with how the OR-M dial-up connection is established with a PM2ER. Does
the OR-M have the intelligence built into it to hold the phone numbers,
logon-ids, passwords, and init strings and it controls the connection? Or
is there an external source that has to be involved...?

Understanding the availability of assigned static IP addresses and
even entire class C's to a dial-up async port on the PM2ER based upon
Radius' authentication (and presuming the answer to the first question is
"yes, you can do that"), will the OR-M handle the routing between:

1 Ethernet Port (a unique subnet or class address)
1 Async port (an address assigned by Radius)
1 PCMCIA port (an address assigned and possibly of another
subnet or class address than the async port)

Last question: Of those that are using the OR-M can you please
respond with your opinions as to how the response is from a network
situation over a dial-up connection and as to whether you have done what
I'm asking about or not....?

Thanks for reading all the way through this...

Timothy