Re: kern/120636: Ndis driver causes system to hang while bringing AirLink101-AWLC3026 card up

[ Available lists | Index of freebsd-bugs | Month of Feb 2008 | Week of 29 Feb 2008 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Volker <volker@vwsoft.com>
Date
29 Feb 2008 00:40:08
Subject
Re: kern/120636: Ndis driver causes system to hang while bringing AirLink101-AWLC3026 card up
Message-ID
200802290040.m1T0e7FJ008259@freefall.freebsd.org


[ Hide this part ]
The following reply was made to PR kern/120636; it has been noted by GNATS.

From: Volker <volker@vwsoft.com>
To: bug-followup@FreeBSD.org, yuri@tsoft.com
Cc:
Subject: Re: kern/120636: Ndis driver causes system to hang while bringing
AirLink101-AWLC3026 card up
Date: Fri, 29 Feb 2008 01:37:32 +0100

Yuri,

may I suggest not to key in every example command from the handbook and
see how it fails? The handbook is really just to explain how things are
working, not a "tell me 1:1 which commands I need to enter" tutorial and
it's up to the user to configure everything to his needs.

If you think documentation should be changed, you're free to join the
docs team. I know they're happy for every helping hand to write the
documentation.

Anyway, to solve your problem, I'm really wondering if you're able to
get your wifi network working when using either no wep key index number
or at least start with number 1 index key?

To start with wifi networks and figuring out how to configure them, it
often helps to first start with unencrypted network configurations. If
you have that running, you may just make the next step and enable WEP.

If it doesn't work in the first step, please enable wlan debugging and
see what you're getting. As you've been afraid to show us your dmesg or
at least output of `uname -a', everything else is guesswork for us.

Please notice, there have been wlan changes lately in the RELENG_7
branch, so it may make sense to you to cvsup to the latest, rebuild
kernel + world and retry setting up everything.

Also keep in mind, wep "protected" networks are known to get broken
easily for years and it's advised to use WPA instead. hostapd and
wpa_supplicant will happily do their jobs and it's not too difficult to
set them up under FreeBSD.


Elapsed time: 0.182 seconds