> I tried to stop Squid and restart the DNS; still not solve the problem > (;;connection timed out). > How do you tell Squid to take only 80% of the bandwidth? You need to setup delay pools in squid. Read about it at http://squid.visolve.com/squid/squid24s1/delaypool.htm. Basically add lines to your squid.conf delay_pools 1 delay_class 1 2 delay_parameters 1 450000/500000 300000/350000 You will have to tune the x/x pair of parameters to get the byte/sec right for your link (these are my values) Marco. On Mon, 01 Nov 2004 19:08:45 +0700, Kh Linux <fedora.kh@xxxxxxxx> wrote: > Thank you. > > > My 2 cents: > > > > Might want to uncomment the following line in your named.conf > > > > // query-source address * port 53; > > I did that as I found it on a thread from the Net, but did not solve the > problem. > > > > > This will revert to the pre BIND 8.1 behaviour. If you PIX rules are > > setup that way you probably do not get the delay anymore. > > > > Regarding the saturated link: try the eliminate method: stop squid for > > a moment (yes users will complain) and do some DNS testing and see if > > anything changes. If DNS responds normally take a look at the squid > > config. I setup my squid with delay pools to take 80% of our bandwith > > so some is left for other stuff on the link. > > I tried to stop Squid and restart the DNS; still not solve the problem > (;;connection timed out). > How do you tell Squid to take only 80% of the bandwidth? > > My PIX keeps getting Input Packet Errors (the number of errors keeps > increasing). I am not sure what causes this. Maybe that makes it very slow. > And the MRTG graphs shows only 3.5k for my 1 Mbps link. I think, that is the > main cause. Sorry to bother you all around. > > Let me try to resolve my PIX problem first. > Well, it is out of topic but may I ask if anyone has an idea of what's wrong > with my PIX or my local network? What could cause Input Packet errors? > > Thank you all again; I'm very much greatful. > > Regards, > Vidol > >
