| 1 |
The problem seems to have been that tcp congestion notification |
| 2 |
(net.ipv4.tcp_ecn) had been turned on, which doesn't work and play |
| 3 |
well with my internet connection. Turning it off got things working |
| 4 |
again. |
| 5 |
|
| 6 |
My guess (and it's only a guess) is that /etc/sysctl.conf was tweaked |
| 7 |
when I emerged sys-apps/baselayout back on June 10. When I rebooted |
| 8 |
the machine yesterday morning, it got a new ECN setting, which hosed |
| 9 |
things. |
| 10 |
|
| 11 |
Well, that blew a few hours of my time. Feh. :-) |
| 12 |
|
| 13 |
On Sat, 9 Jul 2005, Paul Heinlein wrote: |
| 14 |
|
| 15 |
> I got an odd new problem. |
| 16 |
> |
| 17 |
> The host in question is on a five-node LAN sitting behind a NAT gateway. |
| 18 |
> |
| 19 |
> I can |
| 20 |
> |
| 21 |
> a. ping any host on the LAN or Internet (i.e., ICMP works fine) |
| 22 |
> b. query any DNS server on LAN or Internet (UDP works fine) |
| 23 |
> c. receive TCP connections from LAN or Internet |
| 24 |
> d. initiate TCP connections to hosts on LAN |
| 25 |
> |
| 26 |
> I cannot |
| 27 |
> |
| 28 |
> * initiate TCP connections to hosts on the Internet |
| 29 |
> |
| 30 |
> The problem isn't specific to any TCP protocol; they all fail: smtp, telnet, |
| 31 |
> ftp, http, ... |
| 32 |
> |
| 33 |
> I'm working on isolating the interesting parts of strace output; right now |
| 34 |
> the only thing that leaps out at me is that connect() is timing out, e.g., |
| 35 |
> |
| 36 |
> connect(3, {sa_family=AF_INET, sin_port=htons(80), |
| 37 |
> sin_addr=inet_addr("129.95.36.100")}, 16) = -1 ETIMEDOUT (Connection timed |
| 38 |
> out) |
| 39 |
> |
| 40 |
> Clues? |
| 41 |
> |
| 42 |
> -- Paul Heinlein <heinlein@××××××.com> |
| 43 |
> -- |
| 44 |
> gentoo-sparc@g.o mailing list |
| 45 |
> |
| 46 |
> |
| 47 |
|
| 48 |
-- Paul Heinlein <heinlein@××××××.com> |
| 49 |
-- |
| 50 |
gentoo-sparc@g.o mailing list |
Archives