yum update caused weird network problems

derzok · 11-18-2007, 08:41 PM

So I installed Fedora Core 6 a while ago on my server. I have a decently static IP so I have a domain name for it. I recently did a

Code:

yum update

It took about an hour to download all the packages (a few hundred of them, actually). They all installed fine with no error messages. The only things to note were

Code:

Updating: pam [17/493]warning: /etc/pam.d/system-auth created as /etc/pam.d/system-auth.rpmnew
Updating: postfix [ 56/493]warning: /etc/postfix/main.cf created as /etc/postfix/main.cf.rpmnew
Updating: postfix [ 56/493]warning: /usr/lib/sasl2/smtpd.conf created as /usr/lib/sasl2/smtpd.conf.rpmnew
Updating: sendmail [116/493]warning: /etc/mail/sendmail.cf created as /etc/mail/sendmail.cf.rpmnew

None of those looked too crucial.

So now when I access my website via the url http://zoklet.net it won't load.

I assumed SELinux decided to **** with me again so I did a

Code:

setenforce 0

just to make sure. No luck. nmap says that all the ports are filtered. However when I run nmap on the box's lan IP it says all the necessary ports are open.

The server's local IP has not changed, my outside IP has not changed, and all the ports are still forwarded properly. I am thinking that it's got something to do with the upgrade, but I can't figure out what.

Glennzo · 11-19-2007, 05:05 AM

Might be easier to go over to www.dyndns.org and get yourself a free account. I can successfully ping www.zoklet.net,

[glenn@toshiba ~]$ ping www.zoklet.net
PING www.zoklet.net (69.135.212.19) 56(84) bytes of data.
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=1 ttl=47 time=61.5 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=2 ttl=47 time=60.7 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=3 ttl=47 time=53.9 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=4 ttl=47 time=47.7 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=5 ttl=47 time=48.5 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=6 ttl=47 time=50.3 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=7 ttl=47 time=52.1 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=8 ttl=47 time=49.3 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=9 ttl=47 time=51.6 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=10 ttl=47 time=53.9 ms
64 bytes from cpe-69-135-212-19.woh.res.rr.com (69.135.212.19): icmp_seq=11 ttl=47 time=54.7 ms

but not http://zoklet.net

Setup an account and then install inadyn, configure /etc/inadyn.conf and everything should work well. That's what I've been doing with a dynamic Comcast IP and it's worked out very well. Clicking the link for your website loads nothing.

derzok · 11-19-2007, 06:33 AM

Currently I'm using afraid.org as my name server. It's never given me any problems before. How would dyndns help?

Glennzo · 11-19-2007, 07:36 AM

In my case I have Comcast for my ISP. The public IP address is dynamic, meaning, as I'm sure you know, that it changes from time to time. If I setup a web site using the current public IP it would work until the public IP changed. Using a free account at dyndns.org combined with the local inadyn service my public IP address is kept current. Inadyn constantly polls the public IP and relays the info to the dyndns account. That way when the public IP changes dyndns knows about it and makes the appropriate change, keeping my web site available at all times. Check out my site in my signature just to see that you will be able to access it any time.

derzok · 11-19-2007, 02:34 PM

Quote:

Originally Posted by Glennzo

In my case I have Comcast for my ISP. The public IP address is dynamic, meaning, as I'm sure you know, that it changes from time to time. If I setup a web site using the current public IP it would work until the public IP changed. Using a free account at dyndns.org combined with the local inadyn service my public IP address is kept current. Inadyn constantly polls the public IP and relays the info to the dyndns account. That way when the public IP changes dyndns knows about it and makes the appropriate change, keeping my web site available at all times. Check out my site in my signature just to see that you will be able to access it any time.

That makes perfect sense to me. I actually have the exact same setup using afraid.org. Every hour my server wget's a page on afraid.org's server and update's my DNS records accordingly. That's not the problem. The problem is that I can not access my server from inside OR outside the network using my IP address OR the domain name. My server address is http://69.135.212.19/ and nobody can see it. The ports are forwarded properly on all of my routers. Something is blocking my server. When I access the server with it's local IP: http://192.168.0.12/ it works fine.

Glennzo · 11-19-2007, 03:45 PM

Misconfigured httpd.conf ???

Jack_Fedora · 11-19-2007, 04:11 PM

I was able to load the Fedora 8 and it resolved the problem. I found that updating the kernel in Fedora 6 and 7 caused this error. The sever would ping out, but not in. Could not find it in the local network nor on the net. Clean install of 8 solved the problem. Have updated the kernel a few times and have not had a problem.

ifconfig would show that the card was working fine.

derzok · 11-19-2007, 10:20 PM

Just checked my httpd.conf and conf.d/* - everything looks normal. Tomorrow I will set up another computer on the network to act as a server and set that as dmz. If that server works, then we can rule out the possibility of it being the router. I'm pretty sure it's got something to do with the server, though. It worked just fine until I updated with yum.

derzok · 11-20-2007, 08:05 AM

Update: I just installed apache on a windows machine and set it as my router's DMZ. The apache test page showed when I went to both my IP and to my domain name. It's definitely a problem with the server, not the router or modem.

Edit: Oddly enough, when I switched DMZ back to my linux machine, it worked fine. I can now access my server from both the IP and domain name - though I'm not sure why... Thanks for your help Jack and Glennzo!