[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: tcpip stops working after some time



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.

Jeff
-- 
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.


Reply to: