This is a pretty easy fix as follows
# chmod u-w /usr/bin/kismet*
# chmod u+s,o-r /usr/bin/kismet_capture
Now you should be able to run kismet now under standard user accounts.
Debian
All posts tagged Debian
Below is a way to connect your clients like smartphone, laptop, etc to the Internets while you are out and about connecting to random WiFi networks etc like Mac Donalds, and to help protect yourself while on them unknown networks with unknown users
Install mppe kernel support
# modprobe ppp-compress-18
Install PPTPD
# apt-get install pptpd
Configure IP Address Range
Edit the file /etc/pptpd.conf for the IP address range
localip 172.16.100.1
remoteip 172.16.100.200-250
restart pptpd to activate changes
# invoke-rc.d pptpd restart
Adding users accounts
Edit the file /etc/ppp/chap-secrets
test_user * lamepassword *
The above will give you a working PPTPD where your able to connect to securely but you’ll most probably can’t connect to the outside network.
To allow you PPTP clients access to the big bad internet
Enable IPv4 forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward
Finally configure your iptables
iptables -A INPUT -i ppp+ -j ACCEPT
iptables -A OUTPUT -o ppp+ -j ACCEPT
iptables -A POSTROUTING -t nat -o eth0 -j MASQUERADE
iptables -A POSTROUTING -t nat -o ppp+ -j MASQUERADE
If you want all traffic to go through the PPTP connection
Edit the file /etc/ppp/pptpd-options and change
# Debian: do not replace the default route
nodefaultroute
to
# Debian: do not replace the default route
#nodefaultroute
and don’t forget to restart pptpd 
Reference
Debian pptpd HOWTO
IP Chicken
# nano /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0B05", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="413C", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18D1", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="109B", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0BB4", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="12D1", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="24E3", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="22B8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="1D4D", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04DA", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="05C6", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="1F53", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04E8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04DD", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0FCE", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2340", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666", GROUP="plugdev"
# chmod +x /etc/udev/rules.d/51-android.rules
Reference:
Using Hardware Devices
Yesterday my Softrock RX Ensemble II HF Receiver arrived from Five Dash Inc. in the US within ten days and was very well packed. Any way like most grown men with a new toy I descided to take the day out and build it, the took me about 15 hours in total. The guide by WB5RVZ is comprehensive and easy enough to follow in a half dozen so steps. I also have a nice box for the Ensemble II RX coming from the KM5H store and it will make it to be a nice looking package.
Here are some pics from the build
Continue Reading
My SeaSDR_40 kit arrived from Italy. Last night I finished off building the kit together, the is rather easy to put together and the only real thing to watch out for is the toriod with the primary and secondary windings on it, to soldering it in correctly.
I also got the SeaSDR_40 working with Quisk by only having to make a couple minor alterations to the ~/.quisk_conf.py file.
near the top of the file I changed the hardware import
import quisk_hardware_model as quisk_hardware
to
import quisk_hardware_fixed as quisk_hardware
This will allow you to have frequency shown in Quisk based on the VFO of the SeaSDR_40.
To alter the VFO to that of the SeaSDR_40 change
fixed_vfo_freq = 7056000
to
fixed_vfo_freq = 7080500
All that is left for me to do is buy a metal box to mount the board into with some socket and connectors.
This is how I got the ENE UB6250 card reader working under Debian testing one my Acer Aspire One D255E
lsusb:
…
Bus 001 Device 005: ID 0cf2:6250 ENE Technology, Inc. SD card reader (UB6250)
…
This card reader uses the ums-eneub6250 module and needs firmware to operate correctly which is currently not included in the Debian firmware-linux or firmware-linux-nonfree packages.
The way I have gotten around the problem at the moment is to downloaded the Ubuntu linux-firmware package and extracted the deb package to copy the directory ene-ub6250 from the extracted directory /lib/firmware/ to /lib/firmware/ on my working system as I not wanted to install 40 odd megabyte of other firmware I not needed.
After moving the files over run the following and all should be ready to use
# depmod -ae
# update-initramfs -u
Reference:
http://forum.dug.net.pl/viewtopic.php?id=20461&p=1
Today I setup Prey 0.5.3 on my netbook running Debian testing.
# apt-get install prey
Here is what I modified in my ‘/etc/prey/config‘
.... # autoconnect feature, disabled by default until we are 200% sure it # works flawlessly in all platforms. feel free to try it out though. auto_connect='y' .... # you can get both of these from Prey's web service api_key='' device_key='' .... # if you're having trouble getting requests across your firewall or proxy, # you can try adding '-0' to make curl perform HTTP 1.0 requests curl_options='-0 --compress' # this option prepends a random number as a subdomain to the check URL on http mode # makes it harder for other programs to block Prey so its a good idea to be on randomize_check_host='y' ....
Also I added to my root crontab for updates
# crontab -e
Was
*/10 * * * * /usr/share/prey/prey.sh > /var/log/prey.log
now is
*/10 * * * * /usr/lib/prey/prey.sh > /var/log/prey.log
The Debian Edu Team is pleased to announce the release of Debian Edu “Squeeze” 6.0.4+r0! Debian Edu (aka “Skolelinux”) is a Debian Pure Blend specifically targeted at schools and educational institutions, and provides a completely configured school network environment out of the box. It covers PXE installation, PXE booting for diskless machines, and setup for a school server, for stationary workstations, and for workstations that can be taken away from the school network. Several educational applications like Celestia, Dr. Geo, GCompris, GeoGebra, Kalzium, KGeography and Solfege are included in the default desktop setup.
Well switching from nVidia propietry drivers to the open source Nouveau drivers for nVidia GPU’s I found I had no 3D acceleration, and when running glxinfo etc I was getting
Error: couldn't find RGB GLX visual or fbconfig
And in Xorg.log.0 output file I was seeing
Failed to load module "glx" (loader failed, 7)
Turns out after stuffing around trying to find a solution, I did a search to find the package that held libglx.so and that was in the xserver-xorg-core. Well I reinstalled xserver-xorg-core and it fixed the problem and I now have 3D goodness 
# apt-get install --reinstall xserver-xorg-core
Well I thought I’d have another play with Nouveau the open source driver for nVidia GPU’s, as it been a while since played around with them. Since the last time I played with Nouveau it was very buggy and unstable and 3D support was even worse, but I very surprised that there is some 3D support via Gallium3D.
Anyways this how I setup my xorg.conf for dual head setup with nouveau under Debian testing (wheezy):
Section "Monitor"
Identifier "monitor0"
Option "PreferredMode" "1920x1080_60.00"
EndSection
Section "Monitor"
Identifier "monitor1"
Option "PreferredMode" "1440x900_60.00"
Option "RightOf" "monitor0"
EndSection
Section "Device"
Identifier "device0"
VendorName "nVidia Corporation"
BoardName "GeForce GT 220"
Driver "nouveau"
Option "Monitor-DVI-I-1" "monitor0"
Option "Monitor-VGA-1" "monitor1"
EndSection
Section "Screen"
Identifier "screen0"
DefaultDepth 24
SubSection "Display"
Depth 24
Virtual 3360 1080
EndSubSection
Device "device0"
EndSection
Section "ServerLayout"
Identifier "layout0"
Screen "screen0"
EndSection
At the moment I am very happy with Nouveau and going to keep using it till it borks it again
Also if you not want to go through the hassle of xorg.conf you could run or put this in your session startup file, example this what I used for testing with ~/.fluxbox/startup
$ xrandr --output DVI-I-1 --mode 1920x1080 --pos 0x0 && xrandr --output VGA-1 --mode 1440x900 --pos 1920x0 &
The above does the same as the above xorg.conf configuration.
![[FSF Associate Member]](http://dale.id.au/fsfmem80x15.png){kind=small}
