On Tue, 3 Aug 1999, Steve Christall wrote:
> At 17:29 2/08/99 -0700, Derek Simkowiak wrote:
> Example. Went to www.anandtech.com. Wait for page to load and
> link to go down. Clicked on a news item (K6 goes copper) ...
> diald redials ... looks like the DNS is cached locally. Sends
> out request .... no response .. times out ... disconnects.
Work around this by keeping your link up longer if you're browsing
... I have mine stay up for 10 minutes if diald sees an http
packet (and ftp for that matter). Near the top of your
standard.filter you will see
accept tcp 120 tcp.dest=tcp.www
accept tcp 120 tcp.source=tcp.www
Change 120 to 600 or more.
> It never fails for a first dial, just subsequent reconnects to
> the same site, or maybe other sites, and only intermittently
> .... it works prob 70% of the time.
I have a similar problem, and I haven't gotten around to figuring
out what caused it yet. My situation may differ from yours in
that I use IP Masq (do you?) and dynamic IP number assignment, but
the symptoms are the same (only with a web browser). I first
noticed the problem after an OS upgrade.
I believe it has something to do with the browser trying to keep
the connection alive, but having it broken when diald goes down.
It should work with static IP number assignment, but I guess it
doesn't. Maybe something to do with changes in the routing.
Ed
--
Ed Doolittle <mailto:[EMAIL PROTECTED]>
"Everything we do, we do for a reason." -- Peter O'Chiese
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
