Hello,
Thanks for your reply.
I dont kill netscape, I close it so it should not be the cause and i have
also noticed the same problem by using lynx at the console.
After a bit more testing I have noticed the following situations.
1. Netscape is running but idle and I can see the CLOSE_WAIT status in
netstat and I can also see that netscape responsible for the connection in
lsof. Now I close netscape properly and check netstat and I still see those
CLOSE_WAIT connections but now I can no longer see them in lsof. The
packets still continue to go out and come in and they keep my link up.
2. When netscape or any other internet s/w is not running and nothing is
shown by netstat or lsof. I get packets from a web site that I didnt visit
and my machine sends a response back. This time the communication was
started from outside not from my end. This started to happen even before i
did anything after dialing in. My guess to this is that since i am using
dynamic IP, the IP I got in this connection must have been owned by someone
else and that person has visited this web site, but now I have his IP so
the web site is communicating with me instead and keeping my link up.
3. Say my IP was 202.85.99.111 and I was browsing a web site. I then
stopped but diald wasnt disconnecting because of the CLOSE_WAIT problem and
so I disconnected manually. Then reconnected and got an IP of
202.85.99.222. Now my computer still send packets using the IP
202.85.99.111 as the source but doesnt get a reply back because that is no
longer my IP and it just keeps sending it out thus keeping my link up.
I have monitored these packets for upto 30 minutes and sometimes they all
clear and diald will disconnect but sometimes they continue for
longer. The addition of ignore tcp tcp.fin in standard.filters also did
not help.
Now I have reach a point where I dont know what else to do. I am quite fed
up of it. I have managed to iron out all the other bugs with diald but this
one I cannot understand.
If this is a bug then where is the bug and in which package?
I have tried using diald 0.99.1 and 0.16.5 and I have tried pppd version
2.3.7, 2.3.7 and 2.3.10. The problem is persistent in all these versions.
I am using Mandrake Linux 6.0 which is claimed to be 100% Red Hat 6.0
compatible. Kernel version 2.2.9-27mdk.
I would really appreciate all the help i can get.
Thanks in advance.
Vikash.
> > However as one would expect that after closing netscape these packets
> would
> > stop going through and let diald disconnect, BUT unfortunately this does
> > not happen. The packets keep going through persistently. Now that netscape
> > is closed, lsof or netstat does not show anything anymore and so I cant
> > trace it.
> >
> > I have tried this many times but failed to trace the source of it.
> >
> > Please suggest how I can stop this.
>
>If netscape is closed properly, the connections should disappear, but
>if it crashes, it may leave stray connections open.
>
>This appears to happen when netscape sends a close-connection request,
>but the site you are connected ignores it - in this case it should die
>out in a few minutes because the site keeps sending, but doesn't get a
>TCP_ACK packet.
>
>It should be possible to setup a diald filter to prevent the link from
>staying open for CLOSE_WAIT connections, but I am not an expert on this.
>Something like 'ignore tcp.fin'.
>
>On the other hand, if it doesn't show up in netstat or lsof, it could
>be a bug - it should stop responding to those tcp connections
>altogether. How long do they stay open? Infinitely?
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
