Active Topics

 


Reply
Thread Tools
Posts: 64 | Thanked: 42 times | Joined on Jun 2009
#21
Originally Posted by nieldk View Post
not sure if you can in closef mode, but after deve-su->rootme try to issue
develsh
and then the iwconfig command
Might as well go all the way (as someone suggested further up in this thread) and do ssh root@Localhost, followed by devel-sh. I Could have sworn that I got it to work that way, from closed mode.
 
Guest | Posts: n/a | Thanked: 0 times | Joined on
#22
Source for the N900 injection drivers (courtesy of David Gned, thanks!)
is available here http://david.gnedt.eu/blog/wl1251/

(download link, from that page: http://david.gnedt.eu/wl1251/wl1251-maemo-0.1.tar.gz)

Perhaps it will be helpull for creating new drivers for N9
 

The Following 3 Users Say Thank You to For This Useful Post:
Posts: 64 | Thanked: 42 times | Joined on Jun 2009
#23
Originally Posted by hoggerz View Post
Thats better

Works now using develsh then the commands
Someone just needs to sort out the patched drivers/kernel now....

hoggerz
Are you able to do it without turning networking off from the GUI (i.e. By using IP link set ...)! ?

Btw I noticed that if I try to run the IP link set ... And iwconfig commands separately, I also get an error (in open mode). So I combined them via '&&'. could be that the second command merely has to be issues within a limited period after the first.
 
hoggerz's Avatar
Posts: 56 | Thanked: 35 times | Joined on Oct 2009
#24
Yeah, If I do:

devel-su
(rootme)
develsh
ip link set wlan0 down && /sbin/iwconfig wlan0 mode monitor

it works
If I then type: /sbin/iwconfig wlan0
It says wlan0 is in monitor mode

hoggerz
 
hoggerz's Avatar
Posts: 56 | Thanked: 35 times | Joined on Oct 2009
#25
Only thing is although airodump-ng will now run, It can't see any wireless networks/clients at all. And it seems to think 596523 hours and 14 mins has elapsed since I opened it.

hoggerz
 
Guest | Posts: n/a | Thanked: 0 times | Joined on
#26
Originally Posted by hoggerz View Post
Only thing is although airodump-ng will now run, It can't see any wireless networks/clients at all. And it seems to think 596523 hours and 14 mins has elapsed since I opened it.

hoggerz
Can you tell a bit about where you got airodump-ng ?
I installed iw and aircrak from post 1, but only got aircrack-ng, airdecap-ng, aircloack-ng airolib-ng from that
 
hoggerz's Avatar
Posts: 56 | Thanked: 35 times | Joined on Oct 2009
#27
I originally installed the deb from rzr in this post:

http://talk.maemo.org/showpost.php?p...19&postcount=8

but I overwrote the package with the one in this post

try /opt/maemo/usr/sbin/airodump-ng
It seems to install files in odd places.
I found it with: find / -name airodump-ng

hoggerz
 

The Following User Says Thank You to hoggerz For This Useful Post:
Guest | Posts: n/a | Thanked: 0 times | Joined on
#28
So far, I added all the missing paths to PATH
(export PATH=$PATH:/opt/maemo/usr/sbin:/sbin:/usr/sbin)
EDIT: add the above to $HOME/.profile to make the path permanent

Now, I can successfully issue
airmon-ng start wlan0 (starts monitor device on mon0)

I can also start airodump-ng, but with the same time issue as hoggerz)

trying to start aireplay-ng or airodump-ng on mon0 after airmon-ng outputs

ioctl($IOCSIFFLAGS)failed: Cannot assign requested address

Also, confirms injection is not available when issuing airodump-ng wlan0 with mon0 devoice up

EDIT: we have wl1271, not wl1251 as the N900, so the drivers from David will probably not work directly compiled.
EDIT: Yes, indeed, should do it if we can recompile on the (openmode) kernel, fromDavids Blog "many ports of missing features from wl12xx/wl1271 to current wl1251 (e.g. bluetooth coexistence, hardware filtering, multicast filtering, ...)"

EDIT: For porting the driver, this is very useful: http://wireless.kernel.org/en/users/Drivers/wl12xx
(our kernel is 2.6.32)

Last edited by nieldk; 2012-02-18 at 19:23.
 
Posts: 64 | Thanked: 42 times | Joined on Jun 2009
#29
make sure wlan0 is also brought back up after changing to monitoring mode (ip link set wlan up).

That will at least remove the error I think (still won't work, though). I am currently rebuilding kismet to see how far I get with that.
 
Guest | Posts: n/a | Thanked: 0 times | Joined on
#30
Originally Posted by zszabo View Post
make sure wlan0 is also brought back up after changing to monitoring mode (ip link set wlan up).

That will at least remove the error I think (still won't work, though). I am currently rebuilding kismet to see how far I get with that.
wlan0 was up doing all this.
 
Reply


 
Forum Jump


All times are GMT. The time now is 13:39.