iwlist wlan0 scan returns incomplete Cell 24???

[Archangel-Amael]

Not sure but I believe that Chinese page is old junk.
Try Jean's actual page here
Wireless Tools for Linux

[Archangel-Amael]

Not sure but I believe that Chinese page is old junk.
Try Jean's actual page here
Wireless Tools for Linux

As for the buffer, I believe what you are referring to is the scan buffer, which is limited in size, whereas the buffer that I mentioned is for the actual printed output. Again I read through the code I downloaded from madwifi rather quick like.
But at any rate download the latest code indicated by the numbers, and give it a once over. It's version 30pre9 beta.

[g1ic7h]

Not sure but I believe that Chinese page is old junk.
Try Jean's actual page here
Wireless Tools for Linux

You are absolutely correct, I had multiple tabbed pages open last night, I had both the old page and the new page open but this morning I started reading the old page. Thanks for the correction.

After skimming through the current code, it appears that he checks the buff size and reallocates accordingly. I'm at a loss now...I could try contacting Jean or use airodump as TAPE suggested. Either way iwlist breaks when ap's number above 24-25...which in turn breaks any tool which uses it an is unaware of iwlist limitation.
Unless you code around this but why bother building on a broken foundation.

Many thanks archangel.amael, Tape

EDIT: I have wasted enough time with this...it is a speed(iwlist) verses accuracy(airodump) dilemma.
I guess I will use airodump for my parsing instead of iwlist.

[Archangel-Amael]

You are absolutely correct, I had multiple tabbed pages open last night, I had both the old page and the new page open but this morning I started reading the old page. Thanks for the correction.
Many thanks archangel.amael, Tape

No problem that's what I am here for.

After skimming through the current code, it appears that he checks the buff size and reallocates accordingly. I'm at a loss now...I could try contacting Jean or use airodump as TAPE suggested. Either way iwlist breaks when ap's number above 24-25...which in turn breaks any tool which uses it an is unaware of iwlist limitation.

Well if you don't make contact then the developer may never know. But it also goes without saying to make sure your assumptions ( due to you are the only one that at present seems to have this issue both here and at google) are well documented so that you can present good info.

Unless you code around this but why bother building on a broken foundation.

Well I am not sure if the foundation is broken.

[g1ic7h]

Well if you don't make contact then the developer may never know.

Update, I have spoken with Jean. I have to commend him on his response time.
To quote him,

Yes, there is a buffer limitation. You could try wireless
tools v30 that double the max buffer, it may help.

I tried 30pre9 beta, still no luck.

It was noticed, which is why version 30 is better than
previous versions. However, the underlying data structures are the
limit.

Regards,

Jean

[TAPE]

Commendable response time indeed !

Well at least you know the limitations on iwlist scan results, and now so do we all !

Good luck with trying out other methods for your project.

[Archangel-Amael]

Commendable response time indeed !

Well at least you know the limitations on iwlist scan results, and now so do we all !

Good luck with trying out other methods for your project.

Indeed within the same day, or 24hours is a good time.

[g1ic7h]

He replied in 50 mins, outstanding.

The script I was/am working on can be found here:
http://forums.remote-exploit.org/pro...k-manager.html

Its a fairly solid script.
About 300 lines of code...still a work in progress...I would be honored if anyone
would like to test it.

Again, thank you all for your assistance.