Re: Setitng OID_802_11_SSID in XP SP2

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

"John K Gummadi" wrote:
> Hi Pavel,
>
> > 1.Microsoft never said that Ndisuio driver in XP is a public interface.
> > You've used it on your own risk, you've lost.
> > There is a sample source code (in the DDK) similar to ndisuio, that you
> can
> > use instead.
> What is the name of the sample? I can see "ndisuio" in
> "C:\WINDDK\2600.1106\src\network\ndis" folder. Is this you're talking about?

This sample is named "ndisprot" in the current (Win2003 SP1) DDK.
Name "ndisuio" belongs to the real XP component and it's sources are not
available.

> > 2. Even if you manage to set the SSID, this won't get you connected to a
> > real life network protected by WPA or WPA2. You'll need a supplicant.

> This means I have to write a driver, right? If so, are there any docs for
> beginners, like how to install the sys file, etc., And if want to debug (to
> see if my code is really being executed), how do I do?

Look... most (if not all) commercial supplicants available today are some
kind of drivers (transport or IM). So it seems that driver is the way to go.
Then you'll need all the tools, kernel debugger and so on.
You can buy the supplicant component (with support of course), this
will save you many many weeks of work and nerve cells.
Security isn't simple and cheap.

> >this won't get you connected to a real life network protected by WPA or
> WPA2.
> I assume this is because WPA or WPA2 doesn't have corresponding OIDs exposed
> by driver like "OID_802_11_ADD_WEP" for WEP, is that correct?

Yes. there are some message exchanges that go as (almost normal) data
packets, not OIDs.

> Though in the future I would love to write a driver, at the moment I'll be
> happy with just WEP if it works without having to write a driver.

Ok, then the OIDs should work.

Arkady: to kick the WZC off the adapter you don't need to stop WZC, correct?
You once posted a fix how to use WZC API for this?
It is a pity that Microsoft won't document how to disable WZC on certain
adapter.
People need this and will do this, if not by a documented way, then by dirty
hacks.
About using "ndisuio": see my 1st reply.

Regards,
--PA

.

Relevant Pages

  • Re: Determine who opens the network adapter driver
    ... Since NDISUIO can't be used by anyone except WZC, then it isn't necessary to know "who opened NDISUIO". ... Now some other third-party NDIS driver other than NDISUIO could be managing the 802.11 adapter. ...
    (microsoft.public.development.device.drivers)
  • Re: windows 2k and msndis_80211_bssilist
    ... | A driver, during initialization, calls ntoskrnl!IoWmiRegistration ... | For NDIS drivers, it does not work that great, given the Miniport ... | Certain classes in MSNDIS relay completely on existing Miniport codes. ... | You need to eitehr write a protocol driver a-la NDISUIO, ...
    (microsoft.public.win32.programmer.wmi)
  • Re: NDISUIO.SYS - Windows XP SP2 - User Mode App Fails
    ... Ndisuio can have additional limitations ... > Add plenty of debug trace into your own clone of ndisprot. ... ring-3 without having to develop a driver. ... Then I used code for for DDK I ...
    (microsoft.public.development.device.drivers)
  • Re: Setitng OID_802_11_SSID in XP SP2
    ... All I need is to be able to talk to the adapter and send ... OIDs successfully. ... I tried disabling WZC ... >>> This means I have to write a driver, ...
    (microsoft.public.development.device.drivers)
  • Re: How can i use Ndisuio in win32
    ... What I do in WinCE is that from my application I opened NDISUIO using ... NDISUIO(or NDISPROT) sample provided in DDK, ... possible that instead of writing a separate driver I could just use the NDIS ...
    (microsoft.public.development.device.drivers)