Re: DHCP request timed out, iwlwifi

[Marco <netuse@lavabit.com>]

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

> At this point, either the wifi driver isn't cooperating, or there
> isn't a DHCP server listening.

Not a single other computer on the network has DHCP problems. If I
plug in an external USB network adapter (which uses a different
driver) the computer connects instantly. However, other computers on
the network also use the iwlwifi driver without problems (but with
different hardware).

> I'd rule out the firewall because typically they let DHCPv4
> through by default.

I think so, too. And if it would be the firewall, it wouldn't
connect with a different network adapter, I guess.

> 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.  If that doesn't
> work and you're sure the address/netmask you set is correct, then
> there's something wrong in the driver.

Now it works again and I cannot test it any more. That's what I
meant with “it's not really reproducible”. I'll have to wait a
couple of days until it occurs again.

> 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 will report back on this issue when the connection fails again and
I can test.

> If the 4-way handshake works, that indicates your WPA passphrase
> is correct.

It's saved in the NetworkManager. I would be surprised if the
passphrase would, out of a sudden, be wrong.

Thanks for taking the time to help tracing down this issue.


Marco