RFUtils more trouble

[Mikkel Andreasen]

Hi Paul

More feedback on your great work. As mentioned earlier, we are experiencing
some problems using RFUtils with the sandisk SD WIFI card.

We have now tried RFUtils on a HP iPAQ 2210 with an ASUS Spacelink WL-110
WIFI compact flash card. But unfortunatly we are experiencing the same
errors as with the SD card.

I don't know if you are still working on it, but thought you would like to
know.

Can you also please let me know, which devices you know it works on?

So far we have gotten it to work on an iPAQ 4150.

Regards

Mikkel Andreasen

 

[Paul G. Tobey [eMVP]]

The only cards that I have are CISCO 350-series cards. We should probably
keep reports of problems in a single thread, rather than starting a new one
for each card that doesn't work (or does), too...

Please refresh my memory on what the symptoms of the failure are. On a card
with which you are having problems, step through the process that is failing
and note anything that might be useful (error codes, not being able to open
NDISUIO, getting not-enough-memory errors from the SSID queries, etc.)
There are a number of places where I didn't bother trying to reallocate
buffers, if the DeviceIoControl failed and maybe one of those is at fault.

Paul T.

 

[Mikkel Andreasen]

Hi again

You are rigth about the single thread..

I tried to locate the one, but could not find it...

The error occurs when retrieving the SSIDs from the
adapter, we get the following exception:

A manged ArgumentOutOfRangeException occurred at Application::Run+0xf
Application::Run+0xf
Form1::Main+0xf

When debuggin we found that this error occurs when public String SSID class
is used in RFUtils:

public String SSID
{
get
{
// Get the string length from the first four bytes.
int c = BitConverter.ToInt32( data, offset + SsidOffset );

// Convert the rest of the SSID stuff to a string.
return System.Text.Encoding.ASCII.GetString( data, offset + SsidOffset + 4,
c ); <-- EXCEPTION HERE

}
}

It seems that the lenght of the integer c gets very large (larger that the
data.length), so that
when doing the ASCII encoding we get an exception.

Hope this migth help.

Mikkel Andreasen

 

[Paul G. Tobey [eMVP]]

OK, I'll see if I can bullet-proof that a bit more.

Paul T.

 

[Paul G. Tobey [eMVP]]

One more thing: what *is* the SSID supposed to be, in the case where it
fails?

Paul T.

 

[Mikkel Andreasen]

Actually I am not quite sure... I'll check when I get back tomorrow.

I think it should not be there at all? In our testing enviroment, we have
from 2-8 SSID with the name AAU and one or two with SSID E3-113. The number
of AAU SSID's is very variating.

We'll make some tests tomorrow.

Mikkel

One more thing: what *is* the SSID supposed to be, in the case where it
fails?

Paul T.

Hi again

You are rigth about the single thread..

I tried to locate the one, but could not find it...

The error occurs when retrieving the SSIDs from the
adapter, we get the following exception:

A manged ArgumentOutOfRangeException occurred at Application::Run+0xf
Application::Run+0xf
Form1::Main+0xf

When debuggin we found that this error occurs when public String SSID class
is used in RFUtils:

public String SSID
{
get
{
// Get the string length from the first four bytes.
int c = BitConverter.ToInt32( data, offset + SsidOffset );

// Convert the rest of the SSID stuff to a string.
return System.Text.Encoding.ASCII.GetString( data, offset + SsidOffset + 4,
c ); <-- EXCEPTION HERE

}
}

It seems that the lenght of the integer c gets very large (larger that the
data.length), so that
when doing the ASCII encoding we get an exception.

Hope this migth help.

Mikkel Andreasen



"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> skrev i en
meddelelse news:[email protected]...

The only cards that I have are CISCO 350-series cards. We should probably
keep reports of problems in a single thread, rather than starting a

new
one

for each card that doesn't work (or does), too...

Please refresh my memory on what the symptoms of the failure are. On

a
card

with which you are having problems, step through the process that is failing
and note anything that might be useful (error codes, not being able to open
NDISUIO, getting not-enough-memory errors from the SSID queries, etc.)
There are a number of places where I didn't bother trying to reallocate
buffers, if the DeviceIoControl failed and maybe one of those is at fault.

Paul T.

Hi Paul

More feedback on your great work. As mentioned earlier, we are
experiencing
some problems using RFUtils with the sandisk SD WIFI card.

We have now tried RFUtils on a HP iPAQ 2210 with an ASUS Spacelink WL-110
WIFI compact flash card. But unfortunatly we are experiencing the same
errors as with the SD card.

I don't know if you are still working on it, but thought you would

like

to
know.

Can you also please let me know, which devices you know it works on?

So far we have gotten it to work on an iPAQ 4150.

Regards

Mikkel Andreasen

 

[Paul G. Tobey [eMVP]]

What I'm trying to figure out is, is the length number just totally corrupt
or might it have some twisted sense to it (maybe they are using some bits of
the length to indicate status flags or something, for example).

Paul T.

Actually I am not quite sure... I'll check when I get back tomorrow.

I think it should not be there at all? In our testing enviroment, we have
from 2-8 SSID with the name AAU and one or two with SSID E3-113. The number
of AAU SSID's is very variating.

We'll make some tests tomorrow.

Mikkel

One more thing: what *is* the SSID supposed to be, in the case where it
fails?

Paul T.

Hi again

You are rigth about the single thread..

I tried to locate the one, but could not find it...

The error occurs when retrieving the SSIDs from the
adapter, we get the following exception:

A manged ArgumentOutOfRangeException occurred at Application::Run+0xf
Application::Run+0xf
Form1::Main+0xf

When debuggin we found that this error occurs when public String SSID class
is used in RFUtils:

public String SSID
{
get
{
// Get the string length from the first four bytes.
int c = BitConverter.ToInt32( data, offset + SsidOffset );

// Convert the rest of the SSID stuff to a string.
return System.Text.Encoding.ASCII.GetString( data, offset + SsidOffset

+
4,

c ); <-- EXCEPTION HERE

}
}

It seems that the lenght of the integer c gets very large (larger that the
data.length), so that
when doing the ASCII encoding we get an exception.

Hope this migth help.

Mikkel Andreasen



"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> skrev i en
meddelelse The only cards that I have are CISCO 350-series cards. We should probably
keep reports of problems in a single thread, rather than starting a new
one
for each card that doesn't work (or does), too...

Please refresh my memory on what the symptoms of the failure are.

On

a

 

[Paul G. Tobey [eMVP]]

If anyone is interested, I've tried this with an Agere "Ruby" card, as well,
and it works fine. These might be branded as Lucent, too.

Paul T.

What I'm trying to figure out is, is the length number just totally corrupt
or might it have some twisted sense to it (maybe they are using some bits of
the length to indicate status flags or something, for example).

Paul T.

Actually I am not quite sure... I'll check when I get back tomorrow.

I think it should not be there at all? In our testing enviroment, we have
from 2-8 SSID with the name AAU and one or two with SSID E3-113. The number
of AAU SSID's is very variating.

We'll make some tests tomorrow.

Mikkel

"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> skrev i en
meddelelse news:[email protected]...

One more thing: what *is* the SSID supposed to be, in the case where it
fails?

Paul T.

Hi again

You are rigth about the single thread..

I tried to locate the one, but could not find it...

The error occurs when retrieving the SSIDs from the
adapter, we get the following exception:

A manged ArgumentOutOfRangeException occurred at Application::Run+0xf
Application::Run+0xf
Form1::Main+0xf

When debuggin we found that this error occurs when public String SSID
class
is used in RFUtils:

public String SSID
{
get
{
// Get the string length from the first four bytes.
int c = BitConverter.ToInt32( data, offset + SsidOffset );

// Convert the rest of the SSID stuff to a string.
return System.Text.Encoding.ASCII.GetString( data, offset +

SsidOffset

+

4,
c ); <-- EXCEPTION HERE

}
}

It seems that the lenght of the integer c gets very large (larger

that
the

data.length), so that
when doing the ASCII encoding we get an exception.

Hope this migth help.

Mikkel Andreasen



"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> skrev

i
en

meddelelse The only cards that I have are CISCO 350-series cards. We should
probably
keep reports of problems in a single thread, rather than starting

a
new

one
for each card that doesn't work (or does), too...

Please refresh my memory on what the symptoms of the failure are.

On

a
card
with which you are having problems, step through the process that is
failing
and note anything that might be useful (error codes, not being

able

to the
same

 

[Mikkel Andreasen]

Hey Paul

It's great that you can and will help. As far as I can recall it runs
through the SSID a couple of times, but suddenly it gets this weird length
number.

The "funny" thing is, that sometimes it can take 2 or 3 updates before the
crash.

As said earlier, I will run some more test detailing what exactly is going
on, tomorrow.

BTW: which device are you using?

Mikkel

What I'm trying to figure out is, is the length number just totally corrupt
or might it have some twisted sense to it (maybe they are using some bits of
the length to indicate status flags or something, for example).

Paul T.

Actually I am not quite sure... I'll check when I get back tomorrow.

I think it should not be there at all? In our testing enviroment, we have
from 2-8 SSID with the name AAU and one or two with SSID E3-113. The number
of AAU SSID's is very variating.

We'll make some tests tomorrow.

Mikkel

"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> skrev i en
meddelelse news:[email protected]...

One more thing: what *is* the SSID supposed to be, in the case where it
fails?

Paul T.

Hi again

You are rigth about the single thread..

I tried to locate the one, but could not find it...

The error occurs when retrieving the SSIDs from the
adapter, we get the following exception:

A manged ArgumentOutOfRangeException occurred at Application::Run+0xf
Application::Run+0xf
Form1::Main+0xf

When debuggin we found that this error occurs when public String SSID
class
is used in RFUtils:

public String SSID
{
get
{
// Get the string length from the first four bytes.
int c = BitConverter.ToInt32( data, offset + SsidOffset );

// Convert the rest of the SSID stuff to a string.
return System.Text.Encoding.ASCII.GetString( data, offset +

SsidOffset

+

4,
c ); <-- EXCEPTION HERE

}
}

It seems that the lenght of the integer c gets very large (larger

that
the

data.length), so that
when doing the ASCII encoding we get an exception.

Hope this migth help.

Mikkel Andreasen



"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> skrev

i
en

meddelelse The only cards that I have are CISCO 350-series cards. We should
probably
keep reports of problems in a single thread, rather than starting

a
new

one
for each card that doesn't work (or does), too...

Please refresh my memory on what the symptoms of the failure are.

On

a
card
with which you are having problems, step through the process that is
failing
and note anything that might be useful (error codes, not being

able

to the
same

 

[Paul G. Tobey [eMVP]]

Our device.

Paul T.

Hey Paul

It's great that you can and will help. As far as I can recall it runs
through the SSID a couple of times, but suddenly it gets this weird length
number.

The "funny" thing is, that sometimes it can take 2 or 3 updates before the
crash.

As said earlier, I will run some more test detailing what exactly is going
on, tomorrow.

BTW: which device are you using?

Mikkel

What I'm trying to figure out is, is the length number just totally corrupt
or might it have some twisted sense to it (maybe they are using some

bits

of
the length to indicate status flags or something, for example).

Paul T.

Actually I am not quite sure... I'll check when I get back tomorrow.

I think it should not be there at all? In our testing enviroment, we have
from 2-8 SSID with the name AAU and one or two with SSID E3-113. The number
of AAU SSID's is very variating.

We'll make some tests tomorrow.

Mikkel

"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> skrev i en
meddelelse One more thing: what *is* the SSID supposed to be, in the case where it
fails?

Paul T.

Hi again

You are rigth about the single thread..

I tried to locate the one, but could not find it...

The error occurs when retrieving the SSIDs from the
adapter, we get the following exception:

A manged ArgumentOutOfRangeException occurred at Application::Run+0xf
Application::Run+0xf
Form1::Main+0xf

When debuggin we found that this error occurs when public String SSID
class
is used in RFUtils:

public String SSID
{
get
{
// Get the string length from the first four bytes.
int c = BitConverter.ToInt32( data, offset + SsidOffset );

// Convert the rest of the SSID stuff to a string.
return System.Text.Encoding.ASCII.GetString( data, offset +

SsidOffset

+
4,
c ); <-- EXCEPTION HERE

}
}

It seems that the lenght of the integer c gets very large (larger that
the
data.length), so that
when doing the ASCII encoding we get an exception.

Hope this migth help.

Mikkel Andreasen



"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com>

skrev

i

starting

a are.
On

that

is able works
on?