[driverloader] Configuration problem?
robmonty at hotmail.com
Wed Jul 20 16:13:34 EDT 2005
I, too, am having this problem.
I am able to see the AP (this is with and without WEP) and get all of the
necessary info but can not get a dhcp address (i.e., make that final
connecition). Even with WEP not enabled, when I look at my AP management
system (this is on an enterprise WLAN), I see my client associated but
UNAUTHENTICATED. At first glance one would say all is fine with the
equipment and it must be authentication. But am not able to get on this
network with or WITHOUT Authentication (WEP) enabled.
I am using an HP zd7140 laptop with both the internal WNIC and an external
D-Link WNIC (albeit not at the same time). OS is Ubuntu.
So far I have not found a solution.
----- Original Message -----
From: "Peter Talbot" <pete at stagefights.com>
To: <driverloader at lists.linuxant.com>
Sent: Wednesday, July 20, 2005 2:58 PM
Subject: [driverloader] Configuration problem?
> I've just purchased driverloader after unsuccessfully trying to get
> ndiswrapper working on my laptop. I'm having the following problem:
> I can "see" my access point with iwconfig (it correctly lists the ESSID
> and MAC address of my router), but trying to ping the router results in
> the error "Network is unreachable", and browsing web pages fails.
> My network consists of two routers one at 192.168.1.1, which is my
> gateway to the internet and a wireless router at 192.168.1.2 .
> My laptop is a 64-bit emachines M6811 running Fedora Core 4. The
> wireless card lists (under windows) as board: BCM4306MP Rev 4.4
> chipset:BCM4306/BCM22050000. I have no difficulty with wireless under
> windows (however I strongly suspect windows is using a 32-bit driver for
> the card).
> I'm not sure what's exactly wrong here, and would appreciate any help.
> I'm somewhat experienced with Fedora linux, have used it for about a
> year, but wireless is something I've never been able to get working
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader