Timeout errors on port 80 when trying to access internet in Fedora Core 2 Test 2

Jeffmrg · 04-09-2004, 08:58 AM

I am getting timeout errors when attempting to access the internet with Fedora Core 2 Test 2. It's a generic timeout error with Mozilla and a timeout port 80 error in Konqueror. All hardware and connectivity were working previously under Fedora Core 1.

Jeffmrg · 04-09-2004, 11:31 AM

My NIC is recognized by my network and communicates with my router so I have a sense that the problem might be related to a security setting. However, disabling or enabling the firewall has no effect, changing any of the device settings through the standard GUI has no effect and changes to my router settings does not seem to effect any type of positive change.

Changes to SElinux settings have no effect.

HELP!

smosends · 04-17-2004, 06:44 PM

Hi,
I have the same problem after upgrading to FC2. I don't have access to internet, no one program can connect. But I can connect to my router through HTTP to configure it. I can ping any page, it does resolve the names to IPs. I started Ethereal and saw that there is no reply on SYNC from any site. Please help.
Thanks,
Sergei

bav · 04-17-2004, 11:18 PM

Search LQ for ECN. I had a similar problem on FC2 Test 1 - I could ping anything, DNS resolved, etc. but could not get a web page to load. I came across the ECN setting for sysctl.conf and once I changed it everything loaded fine.

Never had the problem with FC1 just earlier versions of FC2. Sorry I couldn't post a link - haven't posted enough messages for that. Hope it helps.

smosends · 04-18-2004, 09:16 AM

It does work! Thank you so much BAV !
Just one simple command:
sysctl -w net.ipv4.tcp_ecn=0
and this post's written from Fedora !
Now I'm going to read what does it mean.
Thanks again.
Sergei.

Jeffmrg · 04-19-2004, 06:09 AM

I tried to resolve the problem by issuing the following command:

echo 0 > /proc/sys/net/ipv4/tcp_ecn

as suggested by another thread. This did not work. However, the command:

echo 1 > /proc/sys/net/ipv4/tcp_ecn

provided me with an immediate solution. I have not tried the solution given in this thread, but it is definitely ECN related.

Thanks all.

lehumphr · 04-19-2004, 11:43 AM

I am also having network issues....however during startup my eth0 fails. Does this fix remedy that. I did have the firewall started. Wondering if I should try this or if there is something else wrong with my settings.

bav · 04-19-2004, 02:36 PM

Glad the ECN thing worked! Not sure about why ETH0 won't activate on boot. I went through and configured it using the utilities off the Gnome menu. Not close to my linux machine so can't tell you exactly what I tried. Do you get anything when you do either "ifdown eth0" or "ifup eth0" as root?