I posted this on comp.os.linux.networking last week; maybe here is a
better place to ask...

Diald is working great for me, except for one smallish area: I
consistently have problems with http connections either keeping the
link up, or bouncing it up and down.
    
In maybe 50% of Netscape sessions, I get at least one connection left
in what netstat labels 'LAST_ACK' or 'CLOSE_WAIT' or other near-death
condition.  I don't know if this is Netscape's fault or the server's,
but diald dutifully brings the link up every time tcp resends the
packet, which often means many minutes until tcp backs off or gives
up.  On top of that, my IP address is dynamic, so most of the time
these tcp connections have _no_ hope of ever closing successfully on a
re-dial.

Is there any way to configure diald to _not_ bring the link up for
those connections?  I'm guessing not, since it would require
knowing the state of the tcp connection.

Barring that, is there any way to configure tcp to give up on
those connections any faster?

<Joe
-- 
 Joe Smith
 [EMAIL PROTECTED]


-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to