1 |
I had a similar problem on 2.4, I was unable to initiate any TCP |
2 |
connections from the local host to the local host... never figured out |
3 |
what it was (upgraded to 2.6). |
4 |
|
5 |
Andrew |
6 |
|
7 |
On Sat, 2005-07-09 at 22:49 -0700, Paul Heinlein wrote: |
8 |
> I got an odd new problem. |
9 |
> |
10 |
> The host in question is on a five-node LAN sitting behind a NAT |
11 |
> gateway. |
12 |
> |
13 |
> I can |
14 |
> |
15 |
> a. ping any host on the LAN or Internet (i.e., ICMP works fine) |
16 |
> b. query any DNS server on LAN or Internet (UDP works fine) |
17 |
> c. receive TCP connections from LAN or Internet |
18 |
> d. initiate TCP connections to hosts on LAN |
19 |
> |
20 |
> I cannot |
21 |
> |
22 |
> * initiate TCP connections to hosts on the Internet |
23 |
> |
24 |
> The problem isn't specific to any TCP protocol; they all fail: smtp, |
25 |
> telnet, ftp, http, ... |
26 |
> |
27 |
> I'm working on isolating the interesting parts of strace output; right |
28 |
> now the only thing that leaps out at me is that connect() is timing |
29 |
> out, e.g., |
30 |
> |
31 |
> connect(3, {sa_family=AF_INET, sin_port=htons(80), |
32 |
> sin_addr=inet_addr("129.95.36.100")}, 16) = -1 ETIMEDOUT (Connection |
33 |
> timed out) |
34 |
> |
35 |
> Clues? |
36 |
> |
37 |
> -- Paul Heinlein <heinlein@××××××.com> |
38 |
|
39 |
-- |
40 |
gentoo-sparc@g.o mailing list |