> Hi all,
>
> I'd be most grateful if someone could provide help
> with setting this up. I've tried everything and am
> about to give up...
>
> I have it all configured and what seems to fail is the
> DHCP request:
> Dec 20 14:39:46 localhost kernel: Setting key 0
> Dec 20 14:39:46 localhost kernel: airo: WEP_PERM set
> 12106
> Dec 20 14:39:46 localhost kernel: ip_tables: (C)
> 2000-2002 Netfilter core team
> Dec 20 14:39:46 localhost dhclient: wifi0: unknown
> hardware address type 801
> Dec 20 14:39:47 localhost dhclient: wifi0: unknown
> hardware address type 801
> Dec 20 14:39:49 localhost dhclient: DHCPDISCOVER on
> eth1 to 255.255.255.255 port 67 interval 6
> Dec 20 14:39:55 localhost dhclient: DHCPDISCOVER on
> eth1 to 255.255.255.255 port 67 interval 16
> Dec 20 14:40:11 localhost dhclient: DHCPDISCOVER on
> eth1 to 255.255.255.255 port 67 interval 17
> Dec 20 14:40:28 localhost dhclient: DHCPDISCOVER on
> eth1 to 255.255.255.255 port 67 interval 10
> Dec 20 14:40:38 localhost dhclient: DHCPDISCOVER on
> eth1 to 255.255.255.255 port 67 interval 10
> Dec 20 14:40:48 localhost dhclient: DHCPDISCOVER on
> eth1 to 255.255.255.255 port 67 interval 2
> Dec 20 14:40:50 localhost dhclient: No DHCPOFFERS
> received.
>
> It works on eth0 (network card) and I do know the WiFi
> card works fine under W2K. I have installed the Cisco
> utilities, have used the network configuration
> utilities, even manually editing the files and all's
> fine! Just that it doesn't work.
>
> The funny thing is the card seems to be up, and even
> the interface seems to be up:
> [root@localhost root]# /sbin/ifconfig eth1
> eth1 Link encap:Ethernet HWaddr
> 00:40:96:41:C4:D0
> UP BROADCAST RUNNING MULTICAST MTU:1500
> Metric:1
> RX packets:0 errors:1023 dropped:0
> overruns:0 frame:1023
> TX packets:12 errors:12 dropped:0 overruns:0
> carrier:12
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:3960 (3.8 Kb)
> Interrupt:3 Base address:0x100
>
> But it's not.
>
> Any help?
>
Looks to my like, maybe your WAP key or driver or something isn't working
quite right! You have no packets sent without failure and you havn't
recieved a single byte of data on the interface, only a fair amount of
errors again!
> RX packets:0 errors:1023 dropped:0 overruns:0 frame:1023
^ ^^^^
> TX packets:12 errors:12 dropped:0 overruns:0 carrier:12
^^
There's a couple of things to do AFTER compiling and installing the driver!
1. Make sure your firmware version i 5.00.01 or 5.00.03 those versions are
the only one that will work with the linux driver... I'm using the .01 and
never tried .03.
2. Using the ACU utility, set your adapter up for using WAP, then set the
wap key(will have to be entered as hex values)
3. If you want this to work on boot you'll have to add a couple of lines
into your /etc/modules.conf:
Something like this should work:
alias eth1 mpi350
post-install mpi350 /opt/cisco/bin/bcard
4. Make sure your eth1 card is set for DHCP... (see
/etc/sysconfig/network-scripts/ifcfg-eth1)
5. Now ifup eth1 and it really should work!!! It does for me, and has at
least in RH9 and FC1 (didn't have and mpi350 before RH9)
On FC1, though - I've installed the airo-mpi driver from
http://bellet.info/~bellet/laptop/
Check the readme here http://bellet.info/~bellet/laptop/airo_mpi.HOWTO.txt
In my oppinion, the airo-mpi is at least as good and stable as the cisco
driver, and the handeling is linux-standard stuff... configuration goes in
ifcfg-eth1, nothing else... no need to call bcard and stuff like that!
very nice! But both should work!
Hope it helps!
Thomas
