The problem seems to have been that tcp congestion notification
(net.ipv4.tcp_ecn) had been turned on, which doesn't work and play
well with my internet connection. Turning it off got things working
again.
My guess (and it's only a guess) is that /etc/sysctl.conf was tweaked
when I emerged sys-apps/baselayout back on June 10. When I rebooted
the machine yesterday morning, it got a new ECN setting, which hosed
things.
Well, that blew a few hours of my time. Feh. :-)
On Sat, 9 Jul 2005, Paul Heinlein wrote:
I got an odd new problem.
The host in question is on a five-node LAN sitting behind a NAT gateway.
I can
a. ping any host on the LAN or Internet (i.e., ICMP works fine)
b. query any DNS server on LAN or Internet (UDP works fine)
c. receive TCP connections from LAN or Internet
d. initiate TCP connections to hosts on LAN
I cannot
* initiate TCP connections to hosts on the Internet
The problem isn't specific to any TCP protocol; they all fail: smtp, telnet,
ftp, http, ...
I'm working on isolating the interesting parts of strace output; right now
the only thing that leaps out at me is that connect() is timing out, e.g.,
connect(3, {sa_family=AF_INET, sin_port=htons(80),
sin_addr=inet_addr("129.95.36.100")}, 16) = -1 ETIMEDOUT (Connection timed
out)
Clues?
-- Paul Heinlein <[EMAIL PROTECTED]>
--
[email protected] mailing list
-- Paul Heinlein <[EMAIL PROTECTED]>
--
[email protected] mailing list
