Notices

All,

After speaking to engineers at companies who are far smarter than myself, it is their belief that the firmware in the wl1251 chipset is preventing the collection of data packets while in monitor mode.

I have personally tried damn near all the suggestions here in this thread. Nothing, and I mean nothing, works to collect data packets.

The ONLY data packets I CAN collect are my own when connected to a network which defeats the purpose of Kismet and Aircrack.

So, I am becoming more and more convinced that until someone produces a hacked firmware binary, we will NOT be collecting data packets while in monitor mode.

However, I would really love to see someone more capable than myself prove me wrong!

Good luck, fellas!

Geezer

All,

Here's a follow-up to my previous post. Here is an excerpt from a thread I found while digging around:

"As we discussed on IRC, it is really needed. We must always provide a BSSID when changing channels in preparation for an association. For this reason (and others) the wl1271 with the current firmware does not support promiscuous mode or frame injections.

I'll ask TI next time we meet them, if there is any possibility to remove the need for the BSSID at this point, so things will be greatly simplified. There is a very slight chance that this could be possible for wl1271, but for wl1251 I think there's no hope to change it anymore. So in any case, we will need to support this on the stack if we want to have wl1251 to work correctly. "

Source: http://patchwork.kernel.org/patch/54245/

Geezer

I've talked to the tree maintainer for wl1251 and it's likely not to be an issue with tertiary firmware - I spoke with Kalle less than a week ago.

HTC uses the same chipset in their WM and Android phones, there are many wl1251 initial loader fimware binary blobs floating around. I've used the OpenMoko section and to no avail.

I believe it to be solely and only a mac80211 stack issue that needs to be "customized" for the WL12xx as a workaround.

Thanks, hawaii!

That was my read on the various threads as well. However, do you or anyone you speak with, know the priority of this capability on Kalle's TODO list? I'm sure there are more pressing issues than our needs and wants!

He has quite a bit, was unable to give me a timeframe - but it is fairly low on the priority list. Like, real low.

I also don't expect to see a "community" fix for this issue, just due to the nature of the problem.

I've talked to a few other dev's who did work on the HTC driver and I'm now torn between information of whether it's tertiary firmware issues, or driver/stack issues.

We'll see more when Kalle updates, when I know, you'll know and I hope when somebody else knows, we'll know too. I'll post anything I'm updated on, on Twitter.

hawaii whats the twitter to follow?

@SimonLR is me.

You can simply search the #N900 hashtag for a lot of N900 posts.

I'm sorry te be such a noob, but its not clear to me:
-if the latest version is pretty safe
-if this allows you to get into protected WLAN-spots(if it can hack the passwords)

Hoping for respond, sorry if this is realy stupid.
Regards, Thijs

Haha! That's funny. I already follow you and tweeted with you, Simon! This is Terry, or t_dunlap on Twitter! Small world.

I had lunch yesterday with guy that said some of his teammates had to implement some special firmware on an HTC device for a client. According to his peeps, there isn't a software solution. Only firmware.

I'll keep my fingers crossed that Kalle can do some magic!

I hope you're diggin' your new N900!!

Well hello there.

From the experimenting I've done, I think you whoever you spoke with, is right. I'm not so sure we'll see a fix for this until the tertiary firmware is completed busted open.

Makes me a sad panda.