Share via

The NDIS Blog: We’re back!

  • Article

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

  • Anonymous
    June 29, 2011
    The comment has been removed
  • Anonymous
    June 29, 2011
    @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.