Dave Hatch wrote in a message to Mike Bilow:

DH>> That's a bit difficult across an ethernet cable.  The ISDN
DH>> setups I have operate via Cisco 1003 routers.  The function
DH>> exists - but it's "different". 

MBi> Why are you using the dialer at all, then?

 DH> Because that's the only way to coax the Cisco to connect at
 DH> ISDN. 

 DH> No dial, no connect.

You have me really confused now.  When we talk about "dialer," we
are obviously talking about some process running on the machine actually
connected physically to the ISDN terminal.  If the Cisco router has the
ISDN hardware, then the machine running FNOS is connected only via Ethernet
to the Cisco, right?  In this case, we would not mean the FNOS
"dialer" module, which is what was confusing me.

DH>> "Transport" needs to be handled in a pretty generic way if it's 
DH>> to survive in all of the Modem/Cable modem/ISDN/T1/EtherNet 
DH>> environments.  So does node addressing.  Workin' on it.

MBi> Maybe I'm not following what it is that you are doing?

 DH> At the moment, trying to understand / make use of the
 DH> potential on ISDN interfaced Cisco 1003's.   Watch this
 DH> space, there will be further developments after this primary
 DH> task completes...:-)

Marc:

If FNOS is looking to find out if a particular interface is up, it should
query the interface through the ifconfig facility.  All interface types
(including asy/slip, asy/ppp, and packet/Ethernet) should be pollable for
the "up" condition.  Using DCD directly in any way is a bad idea.
 Is this what is causing Dave grief?
 
-- Mike


---