> Using iwlist eth1 scan, I can see a dozen access points,
including
> mine. But
> I can't make a connection. The system log tells the story:
>
> Apr 10 23:03:24 host-148 dhclient: DHCPDISCOVER on eth1 to
> 255.255.255.255 port 67 interval 6
> Apr 10 23:03:30 host-148 dhclient: DHCPDISCOVER on eth1 to
> 255.255.255.255 port 67 interval 10
> Apr 10 23:03:40 host-148 dhclient: DHCPDISCOVER on eth1 to
> 255.255.255.255 port 67 interval 13
> Apr 10 23:03:53 host-148 dhclient: DHCPDISCOVER on eth1 to
> 255.255.255.255 port 67 interval 16
> Apr 10 23:04:09 host-148 dhclient: DHCPDISCOVER on eth1 to
> 255.255.255.255 port 67 interval 9
> Apr 10 23:04:18 host-148 dhclient: DHCPDISCOVER on eth1 to
> 255.255.255.255 port 67 interval 7
> Apr 10 23:04:25 host-148 dhclient: No DHCPOFFERS received.
>
>
Dumb question - are you using WEP/WPA? If so, did you enter your
key? I have seen problems like this when using a private key and the
wireless router is set in the restricted mode. (You can only connect
with the shared key.)
Dumb question? Don't think so! But, I'm using open WEP, so that
wasn't the issue.
Seems the broadcom driver apparently wants to negotiate parameters I had
specified using madwifi when I used the PCMCIA card. This ifcfg-eth1
works:
TYPE=Wireless
DEVICE=eth1
HWADDR=00:24:2b:93:2b:6b
BOOTPROTO=dhcp
ONBOOT=no
MODE=Managed
USERCTL=yes
PEERDNS=no
IPV6INIT=no
NM_CONTROLLED=no
RATE=auto
ESSID=gadzooks
SEARCH=opendns.com
DNS1=208.67.222.222
DNS2=208.67.220.220
CHANNEL=
I changed Mode from "Auto" to "Managed," Rate to "auto,"
and left
the channel unspecified, even though I new the correct answer. As far
as I can tell, those are the only differences from what I had used
with madwifi, although one is never sure using system-config-network.
Thank you for your attention. dpn