|
||||||||
Monowall does not act as a DHCP server in my case. The LAN environment has 5 laptops, 6 Grandstream IP phones and a printer. The IP phones and the printer connects only occasionally to the internet - mostly to synchronize with a timeserver. df gives the following output (uptime 28 days, DNS forwarder restarted 1 week ago): $ df Filesystem 512-blocks Used Avail Capacity Mounted on /dev/md0c 21758 20164 1594 93% / procfs 8 8 0 100% /proc /dev/ad0a 13822 9376 4446 68% /cf Best regards /Søren -----Original Message----- From: Lee Sharp [mailto:leesharp at hal dash pc dot org] Sent: 9. januar 2007 16:03 To: m0n0wall at lists dot m0n0 dot ch Subject: Re: [m0n0wall] DNS Forwarder Crashes >From: Jim Golden [mailto:jgolden at wingnet dot net] >For some reason the DNS forwarder dies from time to time in one of my >installations. I'm running v. 1.22. If i disable DNS forwarding and >later re-enable it everything works again. I have tried this on two >different Soekris boxes. The machines that have static ip addresses >assigned can still access the Internet, however the ones that have >their addresses assigned by dhcp cannot access the web. Are both of you having trouble with DHCP users only? Because they both should use the same DNS... Or are your DHCP users not getting IP addresses? The php.core issue can cause DHCP to hang. Look at the status.php page in the "df" section, or do a df from the exec.php and see if the ramdrive is full. Normally it runs about %85. --------------------------------------------------------------------- To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch |