[driverloader] Configuration problem?
Linuxant support (Jonathan)
support at linuxant.com
Wed Jul 20 18:20:19 EDT 2005
Even if you are connected to an access point, you must still set the IP
information (routing, addresses, DNS, etc...) or obtain them with DHCP.
We recommend that you use the network configuration tool of Fedora Core
4 (neat) to setup the wireless interface.
If you require more assistance, please send us the output of the
following commands entered in a root shell while you are close to the
access point you are trying to connect to.
iwlist eth1 scanning
ping www.linuxant.com -I eth1 -c 5
ping 220.127.116.11 -I eth1 -c 5
tail -n 30 /var/log/messages
These commands expect that your wireless interface is named 'eth1',
which is common under Fedora Core 4.
It is possible that the enterprise network is also using an additional
way than just WEP for authentification, for example using IEEE 802.1x
protocols to do so. This is supported with DriverLoader with the
xuspplicant package available at:
You should contact your network administrator for more information.
Just to make sure that DriverLoader is working fine, you could try to
connect to a public access point to see if it works.
Technical specialist / Linuxant
support at linuxant.com
Rob Montgomery wrote:
> 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
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader