On Fri, 19 Dec 2008 12:37:44 -0800 (PST)
Jeff D <fixedored@gmail.com> wrote:
> On Fri, 19 Dec 2008, Micha Feigin wrote:
>
> > On Sat, 13 Dec 2008 01:07:12 +0200
> > subscriptions <subscriptions@rdegraaf.nl> wrote:
> >
> > > On Fri, 2008-12-12 at 22:10 +0100, Micha Feigin wrote:
> > > >
> > > > For some reason after a few days of uptime , tcp stops working on my
> > > > machine.
> > > > Ping and dns lookups work, tcp doesn't. I tried both wired and
> > > > wireless,
> > > > removing the firewall and unloading all firewall related modules but
> > > > nothing
> > > > seems to change.
> > > >
> > > > Only restarting seems to help
> > > >
> > > > Any ideas what else could it be?
> > > >
> > > > Thanks
> > >
> > > Try 'netstat -atn' to see if you have filled all ports.
> > >
> >
> > Here's the output, doesn't seem to me that I filled the ports, but I may be
> > wrong. Not sure what are all those open ports at the 40000-60000 range
> > I also it seems that the connection is not all dead, it's just really slow
> > (I sometime get a reply to telnet www.google.com 80 after a couple of
> > minutes although it mostly times out. ping works fine. nada
> > in /var/log/syslog and /var/log/messages
> >
> > vivalunalitshi:tmp# netstat -atn
> > Active Internet connections (servers and established)
> > Proto Recv-Q Send-Q Local Address Foreign Address State
> > tcp 0 0 192.168.1.11:55178 132.66.7.110:80
> > ESTABLISHED tcp 0 1 192.168.1.100:51591
> > 132.66.7.110:80 SYN_SENT tcp 0 0
> > 192.168.1.100:51593 132.66.7.110:80 ESTABLISHED tcp
> > 0 1 192.168.1.100:49378 74.125.79.109:995 SYN_SENT
> > tcp 0 1 192.168.1.100:51590 132.66.7.110:80
> > SYN_SENT tcp 0 0 192.168.1.100:57531
> > 130.83.165.8:3250 ESTABLISHED tcp 0 0
> > 192.168.1.100:42224 87.70.122.110:43754 ESTABLISHED tcp
> > 0 1 192.168.1.100:43329 132.66.7.110:80 SYN_SENT
> > tcp 0 0 192.168.1.100:39098 77.127.241.67:10184
> > ESTABLISHED
> >
> > > Best,
> > >
> > > Rob
>
> are you seeing issues with all tcp or just web traffic? One other thing
> you might want to try out is to fire up tcpdump (tcpdump -i eth0 -n ) and
> run:
> traceroute -n google.com
> and
> traceroute -n -T google.com
>
> The -T there, tells traceroute to send out tcp packets. It could give you
> some insight on what may be causing this issue, or at least where the
> issue might be.
>
I have no idea on how to read this. It seems that regular traceroute fails (-n)
tcp traceroute works (-n -T) and telnet www.yahoo.com 80 fails (same with
google and a few others I testes)
Any ideas?
vivalunalitshi:mpi$ sudo traceroute -n www.yahoo.com
traceroute to www.yahoo.com (69.147.76.15), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
vivalunalitshi:mpi$ sudo traceroute -n -T www.yahoo.com
raceroute to www.yahoo.com (69.147.76.15), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 69.147.76.15 225.569 ms 225.608 ms 180.227 ms
vivalunalitshi:mpi$ telnet www.yahoo.com 80
Trying 69.147.76.15...
<and nada>
> Jeff
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
tcpip stops working after some time
