Network killed?

NoEffex · #1 8th July 2009, 06:34 PM

Well, I don't know what else to say other than it's killed. I did a massive system update after I got back from vacation(Which I had my luggage lost by some nummynuts, fortunately they found it at some airport across the country), and the net just died. I can still access 192.168.1.1 and 192.168.1.2(I am using a router with dd-wrt as a client for now) on fedora, but nowhere else, while I can access the entire net using the exact same setup on any livecd or windows.

All I noticed was it had said pam failed to load, if that could be a problem.

If not, what do you suggest I do? I know first off I'm going to download a fedora 64-bit livecd then chroot->update, but until then, any ideas?

I couldn't find any error messages.

NoEffex · #2 8th July 2009, 07:58 PM

A change in status, I figured out that it's not the network that is killed, it's that it cannot resolve hostnames, while it can still get to IP's.

typerlc · #3 9th July 2009, 12:58 AM

Do the contents of /etc/resolv.conf look sensible?

NoEffex · #4 9th July 2009, 01:42 AM

Yes, actually, I figured out the problem and could have sworn I posted here..

Anyhow, what it was was the i586 nss-mdns package required from wine I guess. What was needed to do was to install the x86_64 version of it.

If anyone else stumbles across the problem and can't get up(Just like the commercial), hit

rpm -Uvh http://149.20.20.135/fedora/developm...c11.x86_64.rpm

Or better yet, go into firefox and download the latest nss-mdns from http://149.20.20.135/fedora/developm...4/os/Packages/, as you can still use IP's, just no DNS stuffs.