[driverloader] Configuration for USR805416 and fedora 1
Linuxant support (Jonathan)
support at linuxant.com
Mon Oct 4 12:47:47 EDT 2004
according to the output of the 'iwconfig' command in a root shell, we
can see that you are associated (connected) the the access point as we
can see the MAC address of your access point in the output of that
command. Since you are using the open security mode, even if you are
connected, it's not sure if the WEP key is correct.
Please disable WEP to see if this is the problem. You should also
disable all the secirity festures of the access point to see if they are
not the problem. You could also take a look in the output of the 'dmesg'
command after you have failed to ping the access point to see if you do
not get a suspicious message related to DriverLoader there.
When you have used the 'ifconfig' commands to bring up your wireless
interface, you forgot to set the netmask for the wireless interface. You
can also set it with the 'ifconfig' command. Please take a look at the
manual page of the 'ifconfig' command for more information.
We do not recommend that you manually configure your wireless interface
with low level commands as 'iwconfig' and 'ifconfig' as it is more
simple to do it with the network configuration tool of your Linux
distribution and using the 'ifup' and 'ifdown' commands to control your
wireless interface is expected by the other tools of the distribution.
If you require more assistance, while you have configured the 'eth1'
wireless interface with the network configuration tool of Fedora Core 1,
please send at support at linuxant.com 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 -f -n 30 /var/log/messages
Technical specialist / Linuxant
support at linuxant.com
Nick Betteridge wrote:
> I'm running fedora 1 and a USR 805416 pci adaptor.
> I have installed the linuxant drivers, the inf/sys/xxx files from the
> linuxant site and everything thing installed without error - even in the
> kernel log. During installation, a temporary license was picked up and
> When I do a iwlist scan, I can see the AP. This AP is already working
> fine with a laptop & windows xp using a USR 805410.
> I entered the pci adaptors mac in the access table on the AP
> The details from the windows xp installation are:
> Association BSSID - <hex-number>
> SSID - <name>
> Channel - <number>
> NetworkType - Infrastructure
> Preamble - lonn preamble
> Data Encryption - yes
> Authentication Mode - Open
> Network Key - <13-character-key-in-hex>
> I use this manually configure the adaptor:
> /sbin/iwconfig eth1 key restricted <13-character-key-in-hex> essid
> "<name>" mode Managed nick "" channel <number>
> /sbin/ifconfig eth1 192.168.0.9
> /sbin/ifconfig eth1 up
> When I do a iwconfig -a, I get :
> lo no wireless extensions.
> eth0 no wireless extensions.
> eth1 IEEE 802.11-DS ESSID:"<name>" Nickname:"anyname"
> Mode:Managed Frequency:2.442GHz Access Point:
> Bit Rate=100Mb/s Tx-Power=0 dBm
> RTS thr:off Fragment thr:off
> Encryption key:<13-character-key-in-hex> Security mode:open
> Power Management:off
> Link Quality:98/100 Signal level:-66 dBm Noise level:-154
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:7 Missed beacon:0
> But when I try and ping a machine on the network, nothing happens -
> attempted after rebooting without the ethernet cable plugged in.
> Not too sure how to go from here, and I would be very grateful for any
> ideas on how to take this further.
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader