Notices

Originally Posted by maxximuscool

would be nice if this wasn't running with powerkernel. I would prefered stock kernel instead.

Originally Posted by Mentalist Traceur

Why? Power Kernel is stock kernel + happiness + sunshine + rainbows + cure for AIDS/cancer/Parkinsons + solving world hunger.

jd4200: I don't have any suggestions right off the top of my head, other than using "lsmod | grep [name of module]" to check if a certain module is loaded, instead of saving the state inside a file (less writes to flash chip, and avoids your sudden-reboot/shutdown/battery-flies-out problem).

Originally Posted by Mentalist Traceur

Nothing 'out there' ever reports itself as having an 192.168.something.something address to the outside world.
The easy way to know what your 'outside' IP is is by going to www.whatismyip.com or something like that.

Originally Posted by jd4200

Clicking widgets changes the states, screeny of it:

Originally Posted by jd4200

My bash scripting skills are still in the early stages, but I created two scripts which are executed by QueenBeecon widgets to put the card in and out of monitor mode, and loads and unloads the drivers (just in case anyone else finds them useful):

Clicking widgets changes the states, screeny of it:

Code:

#!/bin/sh
# You'll either need execute this script as root, or allow user to
# use ifconfig/iwconfig in the sudoers file (which is my method)

mode=$(/sbin/iwconfig wlan0 |grep Mode |awk -F : '{print $2'} |awk '{print $1}')
if [[ "$mode" == "Managed" ]]; then

sudo /sbin/ifconfig wlan0 down
sudo /sbin/iwconfig wlan0 mode Monitor
sudo /sbin/ifconfig wlan0 up

echo "Monitor"
exit 1

elif [[ "$mode" == "Monitor" ]]; then

sudo /sbin/ifconfig wlan0 down
sudo /sbin/iwconfig wlan0 mode Managed
sudo /sbin/ifconfig wlan0 up

echo "Managed"
exit 2

else
echo "state error"
exit 127
fi

The driver loader/unloader is here

Anyone have any tips on how to improve it?

As the drivers are unloaded on reboot, I had to use a "state_file" to keep track of whether they are loaded or not during up-time, and before a reboot or shutdown occurs the state_file is set back to "unloaded".
(Not sure what would happen if the phone loses battery power and turns off though)

Originally Posted by IsaacDFP

Fi

That is indeed an interrested desktop, is that all QueenBeecon? If not, would you mind sharing the name of the widget? Particulary interrested in wireless mode and inject modules.

Originally Posted by J4ZZ

Really nice work. Do I just have to put the code into the command field of a new QBWidget or do I need to create a script and let QBW simply start it.

thx in advance,

..::J4ZZ::..

Originally Posted by Mentalist Traceur

If you put the state_file to into /tmp/whatever it won't get saved to disk (well, unless it's swapped, then it's saved to the swap partition), and then you're avoiding a decent amount of flash wear. You can then also always put a script in /etc/init.d/ or /etc/event.d/ that would create the state_file, with the value of 'unloaded' upon ever boot, so that you don't have conflicts between surviving state_files left over from unexpected system crashes/power-offs. (actually, you can do the latter without the former, to set the value of state_file to unloaded at boot.)