on my side i've dropped NM since a while, too many headaches, and installed wicd.
It is not difficult to edit several files and have network without NM even being awaken from a deep sleep...
Last edited by zika; May 14th, 2012 at 06:51 PM.
That's not a solution, just a workaround...
I have this problem on my PP fallback install,
started late in dev cycle.
Funny that I have quite a few other installs of LL, NN, OO, PP and QQ,
without this problem, I would like to find a solution for a "stock" install
But, that's just me.
Castles Made of Sand,
Fall in the Sea,
Last edited by cecilpierce; May 15th, 2012 at 12:28 AM. Reason: PS
I know not having a working network connection can be a big pain, but doing a bit of troubleshooting before using a work-around, would have been nice.
We are here to test and report bugs, by installing a different network manager, you sort of bypass that process.
Just for documentation purposes, it would be nice if anyone else runs into the problem, that they post the output of the following commands, if it seems that networking isn't working:
This command allows use to see if an ip address has been obtained.Code:ifconfig
This command will allow us to see if DNS is working properly, if the above command doesn't work then try:Code:ping www.google.com
If this command works, then it points to DNS not working properly. With this information, a bug can be filed with the proper information against network-managerCode:ping 22.214.171.124
Thanks, I try those and see what happens.
My problem is that when my system is first started DNS works the way it should, but after a couple of hours, I get "can't resolve urls" messages too. This is on two systems using the same Nvidia based motherboard. The network adapter on these motherboards are bridge devices, and not an actual networking chip. I believe VinDSL, ran into the same sort of thing. I resolved my problem by setting a static ip address and entering the DNS addresses I use in Network-manager.
Other systems I have using dynamic ip addresses don't have the problem.
This is 12.04, happens in one 12.10 and one other 12.10 works fine ?