[ieatlint]

OK, I've got a weird issue going on here that I'm hoping someone can shed light on. Couldn't find any reference to this problem on the forum already, but if I missed it, I apologize.

The problem is that TCP is not routing. It only happens when I try to go through my cheap netgear router. I can talk to other computers on the network, they have unimpeded access to the internet and to me.
I can also successfully make DNS queries, but TCP just times out.
ICMP also works perfectly...

ethereal doesn't contain any errors, nothing unusual going on.

My machine is a Inspiron 8100, running with both a netgear FA311 and a orinoco minipci wifi. There is no firewall in place, default route is configured correctly (as you can see it routes UDP). iptables has no rules set, all policies on the filter table are ACCEPT (I've even unloaded the modules to be positive).

I've ruled out any issues with my hardware, in that it worked perfectly with FC1 (just reinstalled), and UDP is working. My gateway could be the cause, but since nothing changed on it in the ~3 hours since I was running FC1 without issue, I'm inclined to think it's FC2-test1. The only things I can find from the messages log is references to SELinux, something new in 2.6.x.

Don't suppose that the default config for ipsec or ipv6 could interfere...

Any help is greatly appreciated. Thanks.

[genci]

I had this with FC2 test 1 too with my ADSL modem/router, I couldn't get out onto the internet yet DNS was fine.

This is what fixed mine:
Edit /etc/sysctl.conf and add the lines:#Disable ECN
net.ipv4.tcp_ecn=0Then run sysctl -p. I see that ghenry at FedoraNEWS (http://fedoranews.org/ghenry/apt-fc2/) had the same problem and has also posted the workaround.

See if this helps.

[ieatlint]

Well, that was perhaps the most confusing thing I've ever come accross in Linux...
So yeah, that fixed it. Thank you very much :)

[Jman]

Marked as resolved.