The NDIS Blog: We’re back!


Now with witty subtitles

Lately things have been quiet on the NDIS blog.  But that’s about to change, because we’ve got some new blog posts lined up for you.  We’ll start things off this week with a discussion on OID requests.

If you would like to suggest a topic, please leave a note in the comments.


Comments (2)

  1. MikeH says:

    Well, I'd like to suggest to further elaborate on NDIS and Powershell.

    It would be also great if you could show the relation of NDIS to Mobile Broadband support.

    By the way is it possible to create RAW-NDIS packets with Powershell out of the box? Or do I always need a driver, written by my own to communicate?

    Thanks!

  2. ndisteam says:

    @MikeH  – Sure, there's lots to say about NDIS and PowerShell :).  Since you asked, I just posted another article:  blogs.msdn.com/…/wmi-events.aspx

    I'll try to cover Mobile Broadband soon.

    NDIS itself always requires you to write a driver to send packets.  However, there are a couple shortcuts you might be able to take:

    - The easiest is using Raw sockets.  If your needs fit within the capabilities of Raw sockets, you can ask PowerShell to create a socket of type System.Net.Sockets.SocketType.Raw.  However, for security reasons, TCPIP.SYS blocks certain operations — read this first: msdn.microsoft.com/…/ms740548%28v=VS.85%29.aspx .

    - Otherwise, you can grab the NDISPROT sample protocol driver from the WDK.  It's already set up to send packets (with no restrictions) from an IOCTL, so the only change you need to make to the driver is give it a distinct name and GUID.  It's even possible to write a thin C# wrapper that P/Invokes DeviceIoControl, so you can issue packets from PowerShell.