Pocket PC Networking >> Accessing 802.11 Data

by AndrL'hoest » Tue, 28 Jun 2005 21:53:51 GMT

Hi there,

although I asked the same question in the german newsgroup I think it
might make sense to ask here as well:

I want to create a (.net) class library in C++ which provides me with
several methods which return the asked data (like rssi, etc.). So I
included the "ntddndis.h" in my C++ File.

In the next step I want to write an application in C# which accesses
methods from C++- .dll. Tried this with a simple test application and it
worked fine. As all code is translated into the CIL (MSIL) I think it
should be possible to use my application on several Pocket PC 2003.

At the end of the day I want to be a able to copy a .exe - File and a
.dll to a Pocket PC which shows me the rssi and the mac - adresses of
the different access points. Of course I want to process the gained data
later on...

My problem by now is: I included "ntddndis.h" but it just won't compile
and Visual Studio .Net 2003 shows me 102 Error Messages.

Is there anything to adjust in my development environment or are there
any other header- Files I have to include? Anybody any ideas?

As formerly mentioned I use Microsoft Visual Studio .Net 2003 with
Microsoft XP SP 2.

I already was told to use opennetcf but as the final application is
supposed to run on quite a number of PDAs I want to keep everything as
small as possible.


Regards,

Andr

Similar Threads

1. Bluetooth Preventing 802.11 Access

2. 802.11 networking was kyocera access bridge and unipod

3. Location Aware 802.11 Access Points - Pocket PC Networking

4. Windows PC As IEEE 802.11 Access Point

Hi All,

The only limitation would be what 802.11 functions the vendor decided
not to support in a device mean to be used as STA-only. [Frankly, if I
were designing an 802.11 module, I would simply integrate all
functions, and disable as necessary, if even that, but that is another
matter.]

I looked around USENET a bit and saw that this question was already
asked at least once, and several people responded by asking, "Why
would you want to do that?"  Well, I still want to do it, and I am
certain that it is what I would ultimately want to do, all things
considered. I am not a noob - I do research in computer networking, so
helpful responses will be helpful. :)

[Must be Windows for now, not Linux].

Thanks!

-Le Chaud Lapin-

5. 802.11 g

6. 802.11 to 802.15.4 bridge

Has anyone created a bridge protocol between 802.11 and 802.15.4? 


7. Embedded TCP/IP on small micros with SMTP & 802.11

8. 802.11 IP Address Issues

I am establishing an ad-hoc network between two devices (one PC and one
PocketPC), and I can get them to associate with one another, but they
still can't talk until they know both have IP addresses.  When I have
the devices configured to get IP addresses automatically, they don't
always get IP addresses and often I look at the IPs and they are both
0.0.0.0.  How can I force the devices to get addresses?  Thanks!