Originally Posted by penguin chick
I noticed this error when restarting networking service. wireless works without a problem, so I was just curious:
1. what is causing the error
2. how can it be fixed
3. since the wireless is working, should I even worry about trying to fix it
In my case I was not getting an IP either. It seems to be related to how the driver sets the Mode (Ad-Hoc, Managed, etc.) I changed mine from Auto to Managed (because that's the kind of network topology I have here) and shazaam no more error and I got my IP.
This didn't used to be a problem. So my guess is that perhaps a bug was introduced during one of the updates. But that's just a guess.