Hi,
I need to send some custom OIDs from an application to a NIC driver. Does it
require creating a “passthrough protocol” driver to pass the OIDs from the
application to the NIC driver or there are some other ways to do this?
thx
RG
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Hello,
for some years I have used this code with special OID (look at the
rule in NTDDNDIS.H for custom number plan) to talk from user mode
with my NDIS driver in Windows NT 4. For Windows 9x you must write
a protocol driver.
DWORD
CNdisAccess::queryInformation( (
NDIS_OID oidCode,
PVOID pszBuffer,
DWORD dwBufferLength
)
{
DWORD dwReturnedLength;
if ( ! DeviceIoControl(
hDevice,
IOCTL_NDIS_QUERY_GLOBAL_STATS,
&oidCode,
sizeof(oidCode),
pszBuffer,
dwBufferLength,
&dwReturnedLength,
NULL
) )
{
dwLastError = ::GetLastError();
}
…
}
elli
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Mathias,
In your example oidCode has to be only a custom OID or anyone?
thx
RG
-----Original Message-----
From: Mathias Ellinger [mailto:xxxxx@Ellisoft.de]
Sent: Thursday, June 14, 2001 4:16 PM
To: NT Developers Interest List
Subject: [ntdev] Re: NIC driver’ OIDs
Hello,
for some years I have used this code with special OID (look at the
rule in NTDDNDIS.H for custom number plan) to talk from user mode
with my NDIS driver in Windows NT 4. For Windows 9x you must write
a protocol driver.
DWORD
CNdisAccess::queryInformation( (
NDIS_OID oidCode,
PVOID pszBuffer,
DWORD dwBufferLength
)
{
DWORD dwReturnedLength;
if ( ! DeviceIoControl(
hDevice,
IOCTL_NDIS_QUERY_GLOBAL_STATS,
&oidCode,
sizeof(oidCode),
pszBuffer,
dwBufferLength,
&dwReturnedLength,
NULL
) )
{
dwLastError = ::GetLastError();
}
…
}
elli
You are currently subscribed to ntdev as: xxxxx@envara.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
I am working on an NDIS miniport where I have to support custom OIDs. I
haven’t looked into the details of how to get from the user app, but I was
assuming I would do it using WMI.
Anyone have any thoughts on that?
Marc Reinig
System Solutions
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roman Geller
Subject: [ntdev] NIC driver’ OIDs
I need to send some custom OIDs from an application to a NIC driver. Does it
require creating a “passthrough protocol” driver to pass the OIDs from the
application to the NIC driver or there are some other ways to do this?
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
I still cannot understand why WMI any better the “old way” OIDs
RG
-----Original Message-----
From: Marc Reinig [mailto:xxxxx@pacbell.net]
Sent: Thursday, June 14, 2001 5:04 PM
To: NT Developers Interest List
Subject: [ntdev] RE: NIC driver’ OIDs
I am working on an NDIS miniport where I have to support custom OIDs. I
haven’t looked into the details of how to get from the user app, but I was
assuming I would do it using WMI.
Anyone have any thoughts on that?
Marc Reinig
System Solutions
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roman Geller
Subject: [ntdev] NIC driver’ OIDs
I need to send some custom OIDs from an application to a NIC driver. Does it
require creating a “passthrough protocol” driver to pass the OIDs from the
application to the NIC driver or there are some other ways to do this?
You are currently subscribed to ntdev as: xxxxx@envara.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Hello,
In your example oidCode has to be only a custom OID or anyone?
this was a custom ID.
elli
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
As far as I know so far, you still support the custom OIDs in the
minidriver, but the communication between the minidriver and the app is
handled through WMI. I.e., no extra driver is required. WMI handles the
communication between the application and NDIS, which passes the requests on
to your driver through the custom OIDs.
Additionally, I think the use of WMI is similar in concept to using GUIDs
and Interfaces. You register the data you supply or consume. Applications
don’t have to know the specifics of how to talk to the driver, they talk
instead to the exposed “interface.” It also allows for network access, etc.
Mind you, this is what I believe. When I get to the point of actually
implementing it, I will find out for sure. ;=)
Probably, for a very specific need, it is no better. But, I think for more
general use and extensibility, it seems to offer much.
Watch this space if I am sorely disappointed .
Marc Reinig
System Solutions
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roman Geller
Subject: [ntdev] RE: NIC driver’ OIDs
I still cannot understand why WMI any better the “old way” OIDs
RG
-----Original Message-----
From: Marc Reinig [mailto:xxxxx@pacbell.net]
Subject: [ntdev] RE: NIC driver’ OIDs
I am working on an NDIS miniport where I have to support custom OIDs. I
haven’t looked into the details of how to get from the user app, but I was
assuming I would do it using WMI.
Anyone have any thoughts on that?
Marc Reinig
System Solutions
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roman Geller
Subject: [ntdev] NIC driver’ OIDs
I need to send some custom OIDs from an application to a NIC driver. Does it
require creating a “passthrough protocol” driver to pass the OIDs from the
application to the NIC driver or there are some other ways to do this?
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
WMI is the best way to communicate between App and NDIS driver. Take a
look at the E100bex sample in the XP DDK. We have added some custom OIDs
and also an app (testwmi) that shows how to interact with the driver
using WMI interface.
-Eliyas
-----Original Message-----
From: Marc Reinig [mailto:xxxxx@pacbell.net]
Sent: Thursday, June 14, 2001 8:04 AM
To: NT Developers Interest List
Subject: [ntdev] RE: NIC driver’ OIDs
I am working on an NDIS miniport where I have to support custom OIDs. I
haven’t looked into the details of how to get from the user app, but I
was
assuming I would do it using WMI.
Anyone have any thoughts on that?
Marc Reinig
System Solutions
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roman Geller
Subject: [ntdev] NIC driver’ OIDs
I need to send some custom OIDs from an application to a NIC driver.
Does it
require creating a “passthrough protocol” driver to pass the OIDs from
the
application to the NIC driver or there are some other ways to do this?
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Hello ,
EY> WMI is the best way to communicate between App and NDIS driver. Take a
EY> look at the E100bex sample in the XP DDK. We have added some custom OIDs
EY> and also an app (testwmi) that shows how to interact with the driver
EY> using WMI interface.
Yes I know this is Microsoft way. The total overkill to pass some info
to the/from driver. Some line of code with create/device control/close
against the COM (DCOM) overkill … No thanks, only for very big
projects.
elli
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
If you’re OK with Win2K or XP only, there’s always NdisMRegisterDevice,
which creates a device the App can open, and send standard IOCTLs to.
Quoth Mathias Ellinger:
EY> WMI is the best way to communicate between App and NDIS driver. Take a
EY> look at the E100bex sample in the XP DDK. We have added some custom OIDs
EY> and also an app (testwmi) that shows how to interact with the driver
EY> using WMI interface.
ME>Yes I know this is Microsoft way. The total overkill to pass some info
ME>to the/from driver. Some line of code with create/device control/close
ME>against the COM (DCOM) overkill … No thanks, only for very big
ME>projects.
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Yes and on NT IoCreateDevice() can be used although it isn’t so easy. I
agree with Mathias WMI is an ovekill for simple things and on the other
side, it is insufficient (AFAIK) for more complicated app<->driver
communication.
Best regards,
Michal Vodicka
Veridicom
(RKK - Skytale)
[WWW: http://www.veridicom.com , http://www.skytale.com]
From: Scott Neugroschl[SMTP:xxxxx@troikanetworks.com]
Reply To: NT Developers Interest List
Sent: Friday, June 15, 2001 5:31 PM
To: NT Developers Interest List
Subject: [ntdev] RE: NIC driver’ OIDs
If you’re OK with Win2K or XP only, there’s always NdisMRegisterDevice,
which creates a device the App can open, and send standard IOCTLs to.
Quoth Mathias Ellinger:
EY> WMI is the best way to communicate between App and NDIS driver. Take a
EY> look at the E100bex sample in the XP DDK. We have added some custom
OIDs
EY> and also an app (testwmi) that shows how to interact with the driver
EY> using WMI interface.
ME>Yes I know this is Microsoft way. The total overkill to pass some info
ME>to the/from driver. Some line of code with create/device control/close
ME>against the COM (DCOM) overkill … No thanks, only for very big
ME>projects.
You are currently subscribed to ntdev as: xxxxx@rkk.cz
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com