08-19-2008
FreeBSD Wireless - Can do WPA but not WEP or even open
Hello,
I am using FreeBSD on my laptop (R60) and currently it is working great, however, I am having trouble connecting to open or WEP secured networks.
I have read the FreeBSD handbook regarding this many times. That is how I found out how to connect to WPA networks. If anyone could post a brief step by step for open or WEP I would be very greatful.
WPA is easy because I can use WPA suppliment and /etc/rc.d/netif start but this doesnt seem to work for open or WEP... nothing happens.
Thanks,
Karsten
7 More Discussions You Might Find Interesting
1. Programming
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
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
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
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
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
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
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
LEARN ABOUT MOJAVE
perlfreebsd5.18
PERLFREEBSD(1) Perl Programmers Reference Guide PERLFREEBSD(1)
NAME
perlfreebsd - Perl version 5 on FreeBSD systems
DESCRIPTION
This document describes various features of FreeBSD that will affect how Perl version 5 (hereafter just Perl) is compiled and/or runs.
FreeBSD core dumps from readdir_r with ithreads
When perl is configured to use ithreads, it will use re-entrant library calls in preference to non-re-entrant versions. There is a bug in
FreeBSD's "readdir_r" function in versions 4.5 and earlier that can cause a SEGV when reading large directories. A patch for FreeBSD libc
is available (see http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/30631 ) which has been integrated into FreeBSD 4.6.
$^X doesn't always contain a full path in FreeBSD
perl sets $^X where possible to a full path by asking the operating system. On FreeBSD the full path of the perl interpreter is found by
using "sysctl" with "KERN_PROC_PATHNAME" if that is supported, else by reading the symlink /proc/curproc/file. FreeBSD 7 and earlier has a
bug where either approach sometimes returns an incorrect value (see http://www.freebsd.org/cgi/query-pr.cgi?pr=35703 ). In these cases
perl will fall back to the old behaviour of using C's argv[0] value for $^X.
AUTHOR
Nicholas Clark <nick@ccl4.org>, collating wisdom supplied by Slaven Rezic and Tim Bunce.
Please report any errors, updates, or suggestions to perlbug@perl.org.
perl v5.18.2 2013-11-04 PERLFREEBSD(1)