Re: DHCP request timed out, iwlwifi

[Marco <netuse@lavabit.com>]

On 2012-08-06 Dan Williams <dcbw@redhat.com>
wrote:

Hi,

I am sorry do wake up this old thread again (should I start a new
one instead?).

> Ok, that does all look fine.  At this point, either the wifi driver
> isn't cooperating, or there isn't a DHCP server listening.

I managed to find another USB network adapter with a different
chipset which works perfectly. My guess is that the DHCP works (I
don't have access to the DHCP server), since it works fine for all
other hosts on the network.

> I'd rule out the firewall because typically they let DHCPv4
> through by default.  One other thing you could do is set the
> connection to "manual" (ie, static) IPv4 addressing, enter an
> address that you know is on the router's subnet, and try to ping
> the default router.  If that works, then clearly something is
> wrong with DHCP.

The ping did not succeed.

> If that doesn't work and you're sure the address/netmask you set
> is correct, then there's something wrong in the driver.

I am not 100% sure that the values I input were correct. I used the
same settings that a different host used and picked a random IP
address on the same subnet.

That way I am connected to the network, but don't have internet
access (e.g. cannot ping google by IP address).

> Yet another alternative is to do the static IP thing and then
> run a wireshark packet capture and see if the wifi card sees any traffic
> at all.

I did that and wireshark receives packages. But I don't really know
what to look for, to be honest. I can provide a wireshark capture
file, if necessary. But I guess it makes more sense to send it via
email, instead of dropping a big binary blob in this list.

> Anyone else have any thoughts?  If the 4-way handshake works, that
> indicates your WPA passphrase is correct.

It is definitely correct. As I said, if I use a different adapter on
the same computer with the same settings assigned via DHCP it works.


Marco