Comment 11 for bug 320268

Revision history for this message
MattParkins (j-launchpad-the-parkins-co-uk) wrote :

I did the "supersede nameserver 192.168.2.1" thing but to no avail (that is the correct gateway for me too).

The only workaround for me right now is booting into the previous kernel (-9). This is especially frustrating for me as wireless crashes the entire machine every few hours. Useless. Fedora time?