Chuckk Hubbard wrote: > On 6/22/07, *Larry Finger* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Chuckk Hubbard wrote: > > 64studio:/home/chuckk# ifconfig eth1 > > eth1 Link encap:Ethernet HWaddr 00:14:A5:D0:1C:7A > > inet6 addr: fe80::214:a5ff:fed0:1c7a/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:33 errors:0 dropped:3762 overruns:0 frame:0 > > TX packets:114 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:3916 ( 3.8 KiB) TX bytes:7512 ( 7.3 KiB) > > Interrupt:11 > > > > 64studio:/home/chuckk# iwconfig eth1 > > eth1 IEEE 802.11b/g ESSID:"frank" Nickname:"Broadcom 4311" > > Mode:Managed Frequency= 2.462 GHz Access Point: > > 00:0E:A6:71:DE:05 > > Bit Rate=24 Mb/s Tx-Power=18 dBm > > RTS thr:off Fragment thr:off > > Encryption key:74B5-71F1-C9 Security mode:open > > Link Quality=85/100 Signal level=-49 dBm Noise > level=-69 dBm > > Rx invalid nwid:0 Rx invalid crypt:3764 Rx invalid frag:0
I do not think you have the correct WEP key. Otherwise you wouldn't get all these invalid crypt packets. I missed that before. > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > I'm planning on dhcp. But 'dhclient -d eth1' gives: It doesn't work if encryption is wrong. Can you turn encryption off as a temporary measure to get communications working, then turn it on after we know that we can communicate? Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
