I use the following channel patch with current compat-wireless drivers & bt4
source:
Gmane Loom
Maxim Levitsky - 01.june 2010
works for me quite well
Type: Posts; User: FooFighter007; Keyword(s):
I use the following channel patch with current compat-wireless drivers & bt4
source:
Gmane Loom
Maxim Levitsky - 01.june 2010
works for me quite well
since the official kernel update I'm quite happy with the compat wireless drivers and my AWUS036NH.
Index of /kernel/compat-wireless-2.6
no need to use kernels from the Outer Rim Territories :)
Hello,
I use several systems with BT3 (installed/USB/VMWare) for a while and just got into trouble with my new X-Mas GUSB600N WLAN Stick
No matter what driver is installed...
okay, my previous descriptition probably was a bit to short if you haven't done this before
go to that line described and search the upper content of your reject file. if you don't find it you are...
I'm no programmer but I would simply backup file tx.c
then open the file in an text editor and go to line 636
make the section look like the lower part of your reject file except the "+"...
I know this from patching other sources like madwifi-ng + injection + karma
what went wrong can be found in the .rej file so at first have a look at this file to see what the patch expected to...
dhcpcd is DHCP client daemon
http://www.phystech.com/download/dhcpcd_man.html
in common home networks your DSL-router serves as a DHCP server so you need him to get your device configured...
I assume that the lilo menu shows up, right? if so you can change the root parameter. let's assume the title in the lilo menu shows the name "backtrack" you can change the parameter to
backtrack...
if you encounter some problems it might help to have a look at the logs at connection time
xterm -e tail -f /var/log/dmesg &
xterm -e tail -f /var/log/daemon.log &
rmmod ipwraw
modprobe...
you don't have to run vsf_findlibs.sh manually as it is used in the Makefile
LIBS = `./vsf_findlibs.sh`
"make && make install" should be fine here
have you checked here?
...
somehow you seem to screwed your configuration file. you can try this ...
open file in VI and save in unix format
vi FILE
:set fileformat=unix
:wq
-- or get a fresh copy
my last script was madifi-ng only without airbase-ng for that reason
I just modified my script to make it fit more/less to your setup but without airbase-ng - works quite fine here :)
connect wireshark to ath1 and watch out for DHCP stuff
#!/bin/bash
...
is ICMP answer disabled on 10.0.0.20?
could also be a routing problem
what list does "route print" (Windows) / "route" (Linux) show?
do you have a iptables cleanup section like
iptables --flush
iptables --table nat --flush
iptables --delete-chain
iptables --table nat --delete-chain
I would try the following as I'm not...
great news! I'm happy that I could point you to the right place :)
I'm happy to hear that you succeeded :)
have tried this guide here?
kunin.wordpress.com/2008/07/05/asus-eee-pc-901/
check the permissions with "ls -l FILE" and change them with the chmod command if required. (x means execute / r meand read / w means write)
good luck!
go to
/pentesting/wireless/karma and...
I toyed around with bt3 & karma on my Eee 701 for the past two days. As long as you use madwifi-ng keep the following in mind
path:
.../karma/modules/servers/AccessPoint
file:
accesspoint.rb...
Karma uses iwconfig to set the mode of you device but this doesn't work anymore with the current madwifi-ng drivers - search for "set mode (8B06)" in the madwifi ticket system
the following works...
Hi level, tank you for the help!
that works quite fine :)
I also changed my ettercap part to ...
xterm -e ettercap -u -Tq -i at0 /192.168.1.129/...
this is a cut&paste of my script from bt3
#!/bin/bash
# - SoftAP for wireless-testing -
# Hardware: Eee PC 701 - NICs eth0 (LAN) / ath0 (WLAN)
# Software: BT3 Final (HD inst.)
# infra: net...
thank you for the help. unfortunately -u for unoffensive doesn't seem to be allowed in MitM so I have to give "man iptables" a re-run to get around this :)
Hello,
as I have some older Wifi devices @home not capable of WPA/WPA2, I once wrote basic script to give them temporary access to my Inet through a softAP. Since there is airbase-ng out I started...