Looking For...
Rawether for Windows - The
"Win32 NDIS Framework"
Rawether for Windows is widely-accepted and widely distributed framework that
provides
a uniform user-mode interface to Windows network drivers
across all Windows platforms.
NDIS Protocol Driver Samples for Developers
Specialized
kernel-mode samples and toolkits for
development network applications on
Windows 95, Windows 98, Windows Millennium, Windows NT,
Windows 2000 and higher platforms.
NDIS Intermediate Driver Samples for
Developers
Healthy,
stable, functional and well documented
NDIS Intermediate (IM) driver samples
for Windows 2000 and higher.
Then, we hope that you'll
find what you need at PCAUSA!!!
Rawether for Windows,
"The Win32 NDIS Framework (WinDis 32)", is a set of fourth-generation samples for
development of Windows applications which "directly" access NDIS media-access controller
(MAC) drivers.
Rawether for Windows provides a uniform user-mode API that
can be used to interface with Windows NDIS miniport drivers to query and set
NDIS "object identifiers" (OIDs). The Rawether OID interface is widely used by
Wireless adapter vendors (802.11 and power line) as a component used to manage
wireless network connections.
The Rawether packet collection interface is also widely
used as a point of departure for the development of Windows-based network
monitors.
Key features of Rawether for Windows include the capability to develop common
Win32 applications which work on the Windows 2000, Windows XP (and higher)
and Windows Vista platforms using
a uniform and simple API. In addition, Rawether provides the capability to dynamically
bind with installed MAC drivers at run time, instead of being installed using the Network
Control Panel.
Visit
The Rawether.net Site For More
Information...
Microsoft provides an excellent
NDIS IM driver sample in
the newer Windows Driver
Development Kit (DDK). However, the Microsoft
PassThru sample is a "passive pass through" filter. It does not illustrate how
to examine packet data and does not illustrate how to modify packet data. The
PCAUSA samples are intended to illustrate these additional steps.
The steps followed by PCAUSA in the development of the PCASIM NDIS
IM driver samples are the same that every NDIS IM driver developer must make:
Step 1.) Take the existing NDIS IM DDK documentation and
available samples, and make a baseline that works reliably.
We initially thought this would be a trivial task; however, this was
not the case. Although the Microsoft samples are extremely useful, there is a significant
amount of work needed to achieve this goal.
While there is no denying that a developer may learn quite a bit in
Step 1, the results are still disappointing. The developer finally has a healthy (and
perhaps well documented) do-nothing driver. This is, of course, the driver he or she would
have liked to have started with in the first place.
Step 2.) Take a working baseline NDIS IM driver and add
functionality.
Now the real work can begin…
Customers are attracted to PCAUSA networking samples because they
"actually do something" that can be observed and may relate to the work that the
developer needs to accomplish. PCASIM includes two working NDIS IM driver samples.
What PCASIM offers is...
a healthy, stable and well documented (internally)
baseline NDIS IM driver suite
intended to be a good starting point for development.
If you are a developer that wants to get "up to speed"
quickly for the development of an NDIS IM driver on Windows NT 4.0,
Windows 2000 or higher, consider starting with
the PCASIM NDIS IM driver samples from PCAUSA.
More
Information...
-
Illustrating TDI Client and TDI Filtering techniques...
These samples demonstrate how to use the Windows transport data interface (TDI) API to
access the Microsoft TCP/IP protocol from Windows NT & Windows
2000 kernel mode drivers.
The Advanced TDI Samples also include a PassThru TDI Filter sample that can
be extended to filter the TCP and UDP interface below Winsock.
Microsoft provides documentation of TDI, and this documentation is
essentially correct. However, the documentation is written for the advanced
programmer and is easily misinterpreted. There is a great need for companion
sample code as an adjunct to the documentation.
Driver-level access to network protocols is important in the implementation of a
variety of system components such as file system redirectors. Having sources to a simple,
working TDI client is also of use during the development of TDI drivers for the Windows
environment.
What the Advanced TDI Samples offer is...
an extensive collection of TDI Client drivers
for
Windows NT, Windows 2000 and higher
designed to provide a developer with in-depth detailed insight into
how to use and filter TCP/IP from a kernel mode driver.
If you are a developer that wants to use TDI for
TCP/IP networking from your kernel mode driver or need to perform filtering at
the TDI level (below Winsock), consider starting with the
Advanced TDI Samples from PCAUSA.
More
Information...
-
PCAUSA Newsletter & PCAUSA Discussion List
PCAUSA offers two different facilities for customer communication. Both are
"opt-in" mailing lists that include e-mail or web-based access.
