Nokia N900 Packet Injection Problems
by zitstif on Jun.11, 2012, under Posts
I am writing this right after I was just about to pull my hair out due to the fact that I rely on my N900 as my primary phone (which is not necessarily the greatest idea if you tinker with it quite a bit).
I have noticed that after updating to this kernel:
Linux N900 2.6.28.10-power50
produces an issue with the bleeding-edge wireless driver that allows the N900 to be able to do packet injection. If you try to enable the driver and use it, the wlan0 interface will disappear. You will then have to reboot your phone to be able to get the wlan0 interface back.
So out of curiosity I decided to try rolling back to the previous kernel I was using that was provided with the bleeding-edge drivers. Case and point, this was a BAD IDEA. The installation failed and upon rebooting my N900, the N900 went into a reboot loop and to power the phone off I had to pull the battery.
Gladly, I was able to reflash the phone and get it functioning.
Conclusion:
If you want to be able to do packet injection (and use awesome tools like reaver and aircrack) on your N900, you MUST (for now) use the kernel (kernel-power_2.6.28-maemo46-wl1) from bleeding-edge.
Feel free to contact me if you need any help regarding this and I will do my best to help you.
July 22nd, 2012 on 4:19 am
Hi,
Just run into the same issue. So, if understanding correctly, downgrading from 2.6.28.10-power50 will fail and the only way to run kernel-power_2.6.28-maemo46-wl1 is to re-flash?
July 22nd, 2012 on 8:31 pm
Have a look at:
http://goo.gl/3zDY1
I apologize for not going into great detail but I’m tired at the moment.
September 8th, 2012 on 11:52 pm
Ive upgraded my kernel from 2.6.28.10-power49 to 2.6.28.10-power50 & I can load & unload the bleeding edge driver without an issue. everything just working fine.
September 17th, 2012 on 9:09 am
Hi!
i’ve problem with ettercap.. i let my victim disconnect after arp poisoning.
i’ve uncomment etter.conf , echo 1 ip forw , execute ettercap as root (uid & gid 0) and iptables -t nat -L gives me correct output.
WTF?
September 22nd, 2012 on 12:02 pm
Pillo, so clients are disconnecting or being kicked offline after you do arp poisoning?