[Bug 63176] Re: Can't connect to my Kubuntu laptop to my WPA enablednetwork.
stgparris at hotmail.com
Tue Oct 3 17:46:40 UTC 2006
Thanks for the reply but the native Broadcom driver is not an option for me.
I live in an apartment complex with as many as 5 or 6 separate networks in
the area at once. WEP encryption is just pure trash compared to the
security of WPA. I could probably walk around the apartment complex right
now if I had Dapper on here again with Airsnort and get into even the ones
around that are so called secured. However, thanks for the info. I can get
ndiswrapper working fine under Dapper and am moving the laptop back to it in
about 20 minutes. I had to do something to prove to Ubuntu staff I wasn't
lying about ndiswrapper being toasted in Edgy Eft. I've now got screenshots
to prove it. LOL.
>From: Lothar <lothar at tradescape.biz>
>Reply-To: Bug 63176 <63176 at bugs.launchpad.net>
>To: stgparris at hotmail.com
>Subject: [Bug 63176] Re: Can't connect to my Kubuntu laptop to my WPA
>Date: Mon, 02 Oct 2006 22:35:24 -0000
>I run Dapper and I experience the same behaviour. Sometimes it works
>though. It may be a flaw in ndiswrapper. Unfortunately the native BCM
>drivers don't work with more that 1G of ram, so I must use ndiswrapper.
>If you have less ram, try the native bcm driver. It might work for you.
>What annoys me more is that I have to always enter my WPA passkey and
>ssid, as I work with a hidden SSIS. Iwish Knetworkmanager would remember
>my network and allow me just to selekt it from the menu. But after every
>restart I have to enter it manually :-(
>Can't connect to my Kubuntu laptop to my WPA enabled network.
Express yourself - download free Windows Live Messenger themes!
Can't connect to my Kubuntu laptop to my WPA enabled network.
More information about the kubuntu-bugs