Same problem here. I've pretty much tracked down to a Netscape thing.
4.08 and 4.5 both have the same issue. Eventually the link does time out
and die, most of the time. In fact, even if you kill the link, Netscape
may still send out a request and the link will reestablish itself. This
behaiour tends to rear its ugly head at certain sites more than others.
I wonder if it's a Netscape server thing?
Cary O'Brien wrote:
>
> >
> > Sometimes when I am finished with a net surfing session, my link stays up.
> > Seems like there is some sort off www traffic going on even after I exit
> > Netscape. Output from tcpdump:
>
> Excellent. Tcpdump is the way to go.
>
> > 21:39:13.800157 mp-38-119.daxnet.no.8679 > leo.smart.net.www: F 0:0(0) ack
> > 1 win 2048
> > 21:39:50.320157 mp-38-119.daxnet.no.8682 > leo.smart.net.www: F 0:0(0) ack
> > 1 win 2048
> > 21:40:13.360157 mp-38-119.daxnet.no.8672 > leo.smart.net.www: F 0:0(0) ack
> > 1 win 2048
> > 21:41:13.800157 mp-38-119.daxnet.no.8679 > leo.smart.net.www: F 0:0(0) ack
> > 1 win 2048
> > 21:41:50.320157 mp-38-119.daxnet.no.8682 > leo.smart.net.www: F 0:0(0) ack
> > 1 win 2048
> >
> > The host mp-38-119.daxnet.no is with my ISP, leo.smart.net is a host I
> > visited a while ago. I am not sure what the port numbers 8672,
> > 8679 and 8982 means, those are not in my /etc/services file.
> >
> > I haven't changed my filter rules much from the diald example which
> > accompanied diald-0.16.5a, the rules which keep the link up is:
> > accept tcp 120 tcp.dest=tcp.www
> > accept tcp 120 tcp.source=tcp.www
> >
> > Anyone?
> >
>
> My understanding is not 100% but...
>
> mp-38-119.daxnet.no is _probably_ the dynamic ip address you were
> assigned when you connected.
>
> The F means the packet has the FIN (finish) flag set. The 867x port numbers
> are the port numbers on your end that (probably) netscape was assigned
> when it opened tcp/ip connections to talk to leo.smart.net. Netscape
> likes to do lots of transfers in parallel.
>
> All this means that your end thinks the TCP/IP connections have not
> been terminated correctly. If you do a netstat I'll bet a buck
> you get a bunch of connections in FIN_WAIT_2 or something.
>
> Solution? I'm not sure. Stay connected longer? Anyone?
>
--
John J. LeMay Jr.
NJMC, LLC.
http://www.njmc.com
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
