On 6/22/07, Larry Finger <[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
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

If the encryption key shown above is the correct one, everything seems OK
except for having a valid
IPV4 address. Are you planning on using static or dynamic addresses? If
dynamic, you need to issue a
dhclient command. When I on't use NetworkManager, mine is automatic based
on the information in
/etc/sysconfig/network/ifcfg-eth1, but I think 'dhclient -d eth1' should
be sufficient.

Once this is working, you should change your encryption key. It isn't
quite all that is needed to
hack your computer, but it is enough to listen to your wireless
transmissions. I strongly recommend
switching to WPA-PSK. If your PSK secret is longer than 20 characters and
not found in a dictionary,
it is essentially uncrackable. Your 64-bit WEP encryption can be cracked
in as little as 1 minute.

Larry


I'm planning on dhcp.  But 'dhclient -d eth1' gives:

Listening on LPF/eth1/00:14:a5:d0:1c:7a
Sending on   LPF/eth1/00:14:a5:d0:1c:7a
Sending on   Socket/fallback/fallback-net
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
receive_packet failed on eth1: Network is down
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database.

Sleeping.



and then hangs.  I noticed at one point that ifconfig was telling me "frank"
but the network dialog didn't update, it still showed another ap I tried.  I
don't understand how the two interact, but I do know that just using the
dialog doesn't seem to do it.

Damn those Broadcom people.  And damn me for not checking before I bought.

-Chuckk
--
http://www.badmuthahubbard.com
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to