Hi,
I’m developing a skeleton NDIS 5.0 connection-oriented driver on
Win2k. I call it “the do-nothing” driver since it doesn’t have any
hardware and can’t really do anything. It builds and installs just
fine.
When I install the driver, I immediately see a VC activated on
vci:16 and a packet is sent on that VC. Sure enough, it’s an ILMI
packet (nice of them to put ILMI in the packet eh?). Looks like the
LANE client is trying to discover the non-existant switch.
My problem is that I don’t want to have any signalling/ILMI
traffic. I just want to set up a PVC and use that from the dialup
routines for PPPoA. I’ve set up a PVC with the LANE client, but I
don’t see it when I try and set up a dialout connection.
What am I missing here? Do I need to disable the LANE client?
Do I need to use the IP/ATM client? Should I uninstall both of
them and manually set up the PVC in the registry?
How can I get TAPI to offer a PVC as a candiate for a PPP connection?
After looking at the stack backtrace, I realized that the module that’s
generating the ILMI is the ATMUNI module, not the ATMLANE module (makes
sense that the call manager would be initiating ILMI eh?).
I tried rejecting the VC activations on vci:16 with an
NDIS_STATUS_INVALID_DATA, but NDIS just comes back asking for
OID_ATM_ILMI_VPIVCI, which I don’t support (should I?). After the OID is
rejected as unsupported, I get another activatation request on vci:16 and we
start all over again…
So, the question remains: How do I tell ATMUNI that there’s no switch, so
don’t do ILMI, don’t try any signalling, just do PVCs?
***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.
If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************