FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 12-12-2008, 08:10 PM
Micha Feigin
 
Default tcpip stops working after some time

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


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-12-2008, 10:00 PM
Ron Johnson
 
Default tcpip stops working after some time

On 12/12/08 15:10, 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?


Anything is /var/log/syslog?

--
Ron Johnson, Jr.
Jefferson LA USA

How does being physically handicapped make me Differently-Abled?
What different abilities do I have?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-12-2008, 10:07 PM
subscriptions
 
Default tcpip stops working after some time

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.

Best,

Rob


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-18-2008, 10:42 PM
Micha Feigin
 
Default tcpip stops working after some time

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 0.0.0.0:28147 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:38422 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
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
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 ::1:631 :::* LISTEN
vivalunalitshi:tuxonice-head# netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:28147 0.0.0.0:* LISTEN 1000 11961 5101/skype
tcp 0 0 127.0.0.1:38422 0.0.0.0:* LISTEN 1000 643814 4753/gdl_indexer
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 6112 4041/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 6153 4066/cupsd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 621869 23059/exim4
tcp6 0 0 :::22 :::* LISTEN 0 6110 4041/sshd
tcp6 0 0 ::1:631 :::* LISTEN 0 6154 4066/cupsd
udp 0 0 127.0.0.1:35370 0.0.0.0:* 1000 9211 5101/skype
udp 0 0 0.0.0.0:68 0.0.0.0:* 0 1224846 16412/dhclient
udp 0 0 0.0.0.0:68 0.0.0.0:* 0 360014 29605/dhclient
udp 0 0 0.0.0.0:28147 0.0.0.0:* 1000 11962 5101/skype
udp 0 0 0.0.0.0:631 0.0.0.0:* 0 6156 4066/cupsd

> Best,
>
> Rob
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-19-2008, 07:37 PM
Jeff D
 
Default 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.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-21-2008, 08:51 PM
Micha Feigin
 
Default tcpip stops working after some time

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
 
Old 12-21-2008, 09:10 PM
Bob Cox
 
Default tcpip stops working after some time

On Sun, Dec 21, 2008 at 23:51:02 +0200, Micha Feigin (michf@post.tau.ac.il) wrote:

[...]

> 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 * * *

[...]

Just a thought... what does traceroute -I www.yahoo.com (as root) give
you?


--
Bob Cox. Stoke Gifford, near Bristol, UK.
Please reply to the list only. Do NOT send copies directly to me.
Debian on the NSLU2: http://bobcox.com/slug/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-24-2008, 03:28 PM
Micha Feigin
 
Default tcpip stops working after some time

On Sun, 21 Dec 2008 22:10:46 +0000
Bob Cox <debian-user@lists.bobcox.com> wrote:

> On Sun, Dec 21, 2008 at 23:51:02 +0200, Micha Feigin (michf@post.tau.ac.il)
> wrote:
>
> [...]
>
> > 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 * * *
>
> [...]
>
> Just a thought... what does traceroute -I www.yahoo.com (as root) give
> you?
>
>

It seems that this works, ping works telnet www.yahoo.com 80 mostly doesn't
work (sometimes get quick answer, sometimes takes a couple of minutes, mostly
it times out). aptitude upgrade times out. It seems like there is a little
movement but very slow for some reason.


vivalunalitshi:tuxonice-head# traceroute -I www.yahoo.com
traceroute to www.yahoo.com (87.248.113.14), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 f1.us.www.vip.ird.yahoo.com (87.248.113.14) 171.262 ms 171.277 ms 171.273 ms


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-24-2008, 03:45 PM
Ron Johnson
 
Default tcpip stops working after some time

On 12/24/08 10:28, Micha Feigin wrote:
[snip]


vivalunalitshi:tuxonice-head# traceroute -I www.yahoo.com
traceroute to www.yahoo.com (87.248.113.14), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 f1.us.www.vip.ird.yahoo.com (87.248.113.14) 171.262 ms 171.277 ms 171.273 ms


I've always had good success with mtr (package mtr-tiny), which is a
combo of ping and traceroute.


--
Ron Johnson, Jr.
Jefferson LA USA

I like my women like I like my coffee - purchased at above-market
rates from eco-friendly organic farming cooperatives in Latin America.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 12-24-2008, 06:38 PM
Ken Irving
 
Default tcpip stops working after some time

On Wed, Dec 24, 2008 at 06:28:01PM +0200, Micha Feigin wrote:
> On Sun, 21 Dec 2008 22:10:46 +0000
> Bob Cox <debian-user@lists.bobcox.com> wrote:
> > Just a thought... what does traceroute -I www.yahoo.com (as root) give
> > you?
>
> It seems that this works, ping works telnet www.yahoo.com 80 mostly doesn't
> work (sometimes get quick answer, sometimes takes a couple of minutes, mostly
> it times out). aptitude upgrade times out. It seems like there is a little
> movement but very slow for some reason.

A too-big MTU setting can give odd results in some cases.

Ken

--
Ken Irving


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 01:25 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org