Re: NDIS Drivers, Symbolic Names, Ethernet send/receive etc.
From: Arkady Frenkel (arkadyf_at_hotmailxdotxcom)
Date: 01/18/05
- Next message: Arkady Frenkel: "Re: NAT traversal"
- Previous message: Randolph Neall: "Cable modem/router causes error 10054, "Connection was forcibly reset by remote host""
- In reply to: Skybuck Flying: "NDIS Drivers, Symbolic Names, Ethernet send/receive etc."
- Next in thread: Arkady Frenkel: "Re: NDIS Drivers, Symbolic Names, Ethernet send/receive etc."
- Reply: Arkady Frenkel: "Re: NDIS Drivers, Symbolic Names, Ethernet send/receive etc."
- Reply: Skybuck Flying: "Re: NDIS Drivers, Symbolic Names, Ethernet send/receive etc."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 Jan 2005 08:19:42 +0200
Hi!
"Skybuck Flying" <nospam@hotmail.com> wrote in message
news:csgk1d$8sg$1@news4.zwoll1.ov.home.nl...
> Hi,
>
> Suppose a user has a computer with a network card and windows xp
> pre-installed.
>
> Now I want to write a program to send and receive ethernet packets for
this
> kind of computer.
>
> To do this I would need to call CreateFile and then use some sort of
> symbolic name.
Usually you can't do this because not driver but NDIS created security
setting for device
due to Security Descriptor Definition Language (SDDL) in the driver calling
IoCreateDeviceSecure() inside.
>
> Maybe something like:
>
> \\.\\NDIS
>
> What is this specific symbolic name ?
>
> Or maybe
>
> \\.\\IP
>
> ?
>
No , you have to use GUID as a name for device device
> Does windows xp automatically install NDIS drivers for detected network
> cards ?
>
Yes , but if default driver don't match the device , Device manager will ask
you about
driver for NIC
> If so how can I use these drivers ? How do I find out their symbolic names
?
>
You'll see them in registry
> If not then the user should install NDIS drivers ?
>
I answered on that : one before last
> Again how do I find out their symbolic names ? Or how do I find these
> drivers ? ( so my application can talk to them ).
>
As an example look at http://www.pcausa.com/Utilities/macaddr2.htm
> Is there anything else I need to do with these NDIS drivers... maybe bind
> them ? or is that driver specific ?
>
Device Manager automatically bind miniport(s) ( driver(s) of NIC ) to layer
above : IM or protocol.
Miniport in NDIS have no knowledge about protocol above it , only NDIS
manage that.
HTH
Arkady
> Bye,
> Skybuck.
>
>
>
- Next message: Arkady Frenkel: "Re: NAT traversal"
- Previous message: Randolph Neall: "Cable modem/router causes error 10054, "Connection was forcibly reset by remote host""
- In reply to: Skybuck Flying: "NDIS Drivers, Symbolic Names, Ethernet send/receive etc."
- Next in thread: Arkady Frenkel: "Re: NDIS Drivers, Symbolic Names, Ethernet send/receive etc."
- Reply: Arkady Frenkel: "Re: NDIS Drivers, Symbolic Names, Ethernet send/receive etc."
- Reply: Skybuck Flying: "Re: NDIS Drivers, Symbolic Names, Ethernet send/receive etc."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|