Sponsored Content
Operating Systems BSD FreeBSD Wireless - Can do WPA but not WEP or even open Post 302227004 by kpedersen on Wednesday 20th of August 2008 11:20:00 AM
Old 08-20-2008
Quote:
Originally Posted by jb_bsd
no WPA nor WEP here. If so, I might have the process written down.
WPA isn't the problem, do you have a solution to OPEN?

kk, I guess I'll search more... and probs give the handbook another go

thanks,
 

7 More Discussions You Might Find Interesting

1. Programming

open an port on freebsd

i have made some thing with leds on it. i put it directly on the printer port. in dos and windows i can send data to it with outp(0x378,123); and then have some leds on and some leds off. i found out that it is possible linux with same assembly (after searching much.). but i want to have those led... (0 Replies)
Discussion started by: jurrien
0 Replies

2. Cybersecurity

WEP Crack Appz

Looking for a good app to go with my iBook/Airport Extreme card for testing WEP security on my own network... I have had a lot of luck with MacStumbler, but none with KisMAC... any suggestions? Jeffrey d9rw1n:/ root#grep ghost There's nothing like bludgeoning your self with a new box...... (0 Replies)
Discussion started by: f1r3g0dz
0 Replies

3. Windows & DOS: Issues & Discussions

WPA crash vista???

Okay. I need help since I barely use M$ any more, the last time I used it for something other than school, work, or AIM was back in the days of WIN98. I was just reading the article on this site, Is Microsoft about to release a Windows “kill switch”? | Ed Bott's Microsoft Report | ZDNet.com, and... (0 Replies)
Discussion started by: Texasone
0 Replies

4. Programming

Application crashes in FreeBSD 7.1 while working ok in FreeBSD 6.3

Hello there, My mulithreaded application (which is too large to represent the source code here) is crashing after installing FreeBSD 7.1-RELEASE/amd64. It worked properly on others machines (Dual Cores with 4GB of RAM - FreeBSD 6.2-RELEASE/i386). The current machine has 2x Core 2 Duo... (1 Reply)
Discussion started by: Seenquev
1 Replies

5. Red Hat

cannot set user id: Resource temporarily unavailable (not open file/open process related)

First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting. First, this is what's running: This is the error when jobs are run or the... (0 Replies)
Discussion started by: Katahdin
0 Replies

6. Shell Programming and Scripting

FreeBSD rc.subr wireless script

Hi, This is my first thread on Unix forums, so be gentle.:o I'm trying to write a simple start/stop script for my wireless networking adapter, under FreeBSD, using the rc.subr framework. #!/bin/sh # PROVIDE Wireless # KEYWORDS shutdown . /etc/rc.subr name="wireless"... (1 Reply)
Discussion started by: regexp
1 Replies

7. Linux

Is possible to bridge wlan0 and eth0 using network manager?How to for wpa?

I have created a bridge with nmcli between eth0 and wlan0 I use this procedure sudo nmcli con add ifname br0 type bridge con-name br0 sudo nmcli con add type bridge-slave ifname eth0 master br0 sudo nmcli con add type bridge-slave ifname wlan0 master br0 sudo nmcli con modify br0... (1 Reply)
Discussion started by: Linusolaradm1
1 Replies
Reaver(1)						      General Commands Manual							 Reaver(1)

NAME
Reaver - WPS Cracker SYNOPSIS
reaver -i <interface> -b <target bssid> -vv DESCRIPTION
Reaver implements a brute force attack against WiFi Protected Setup which can crack the WPS pin of an access point in a matter of hours and subsequently recover the WPA/WPA2 passphrase. Specifically, Reaver targets the registrar functionality of WPS, which is flawed in that it only takes 11,000 attempts to guess the correct WPS pin in order to become a WPS registrar. Once registred as a registrar with the access point, the access point will give you the WPA passphrase. OPTIONS
-m, --mac=<mac> MAC of the host system (should be resolved automatically) -e, --essid=<ssid> ESSID of the target AP. Unless cloaked, this will be resolved automatically. -c, --channel=<channel> Set the 802.11 channel for the interface (implies -f) -o, --out-file=<file> Send output to a log file [default: stdout] -f, --fixed Disable channel hopping -5, --5ghz Use 5GHz 802.11 channels -v, --verbose Display non-critical warnings (-vv for more) -q, --quiet Only display critical messages -i, --interface=<wlan> Name of the monitor-mode interface to use -b, --bssid=<mac> BSSID of the target AP -p, --pin=<wps pin> Use the specified WPS pin -h, --help Show help AUTHOR
This manual page was written by Craig Heffner <cheffner@tacnetsol.com>, Tactical Network Solutions. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or any later version published by the Free Software Foundation, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. 1.3 29 December, 2011 Reaver(1)
All times are GMT -4. The time now is 02:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy