Hey,
I've done a fresh installation of Fedora 19 (64 bit) on a computer which has been, until lately, functioning adequately with Fedora 16. The computer is my internet gateway, running named, firewalld, postfix, and dovecot. All seems well, for the most part, except that certain internet addresses seem to hang when used from the internal/local network. That is, web browsers on the local net will hang with "Waiting for ..." messages, and applications which worked under F16, like my Amazon Prime account on my television, just sit and spin. Applications running on the gateway system do not have problems. A localnet Windows or OS X box can be hung on an address, and I can jump on the gateway box and browse the same address without problems.
Domain name resolution does not seem to be the problem, because I can put the literal addresses in and the same behavior occurs. Ping and nslookup have no problems. Also, the problem seems to occur only on specific addresses. If I load an Amazon page, the browser will hang on the same image-loading links. The browser will always hang on one news-site link, and never on the other.
As I said, the name-server does not seem to be the problem, since it resolves names from the gateway machine, and the problem occurs with literal addresses as well.
The firewall is set up so that the internal network is "trusted" and the ppp0 network is "external" with only smtp and dns access and masquerading.
NetworkManager is being used, with each interface taking its appropriate firewall "zone" and the ppp0 interface taking its configuration from the ISP automatically with addresses only, so I should be using only my internal nameserver.
Anyway, if someone could point me in a direction in which to look, I would be grateful.
John
I've done a fresh installation of Fedora 19 (64 bit) on a computer which has been, until lately, functioning adequately with Fedora 16. The computer is my internet gateway, running named, firewalld, postfix, and dovecot. All seems well, for the most part, except that certain internet addresses seem to hang when used from the internal/local network. That is, web browsers on the local net will hang with "Waiting for ..." messages, and applications which worked under F16, like my Amazon Prime account on my television, just sit and spin. Applications running on the gateway system do not have problems. A localnet Windows or OS X box can be hung on an address, and I can jump on the gateway box and browse the same address without problems.
Domain name resolution does not seem to be the problem, because I can put the literal addresses in and the same behavior occurs. Ping and nslookup have no problems. Also, the problem seems to occur only on specific addresses. If I load an Amazon page, the browser will hang on the same image-loading links. The browser will always hang on one news-site link, and never on the other.
As I said, the name-server does not seem to be the problem, since it resolves names from the gateway machine, and the problem occurs with literal addresses as well.
The firewall is set up so that the internal network is "trusted" and the ppp0 network is "external" with only smtp and dns access and masquerading.
NetworkManager is being used, with each interface taking its appropriate firewall "zone" and the ppp0 interface taking its configuration from the ISP automatically with addresses only, so I should be using only my internal nameserver.
Anyway, if someone could point me in a direction in which to look, I would be grateful.
John