On Sat, 20 Feb 1999, Neel Karkhanis wrote:
> Presently, I use a linux box as a gateway/firewall through which my
> three Windows boxes access the internet. This linux machine runs diald
> and dialmon.
That's similar to my setup, although my other computer runs Linux and
Netscape 4.5.
> When I start Netscape, etc. on a Windows box (which causes diald to dial
> out), Netscape always returns a "could not resolve" or "timed out" error
> on the initializing request. However, when I make a Netscape request
> sometime in the middle of diald's dial out, this first request succeeds.
That has happened to me too, which leads me to believe that Netscape uses
its own DNS resolver, which wouldn't surprise me, and that Netscape's
resolver is extremely impatient. There may be a way to change the
timeouts within Netscape, but I don't know what it is offhand.
> I'm guessing that there's a problem with some kind of timeout here. Is
> it in Netscape or on the linux box? I've already modified
> /etc/resolv.conf to include my nameserver 3 times, and I'm echoing a 7
> to the ip_dynaddr sysctl. Also, on the Windows boxes, TCP/IP is
> configured to include the nameserver 3 times.
I can't think of anything else you might try along those lines.
> If the problem is on the linux box, does anyone know of a way to correct
> it? I read an earlier message on this list about how buffered packets
> work with some ISPs and not others, but that doesn't seem to cover this
> semi-functional case.
You might try running a caching named on your Linux box. Then sites which
you have visited before wouldn't time out so quickly.
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]
