I have had similar strange behavior by one of two machines (both are combined fw/file/print/samba/mail/web servers for two home networks). Both run RedHat 7.2/2.4.9-13 (custom-compiled), IPTables 1.2.5, and similar firewall rules. The offender is an AMD-K6-III/450 with 768MB RAM, the other machine is a K7 (Athlon) 900, also with 768M RAM.
About every five days, the K6-III machine starts spewing the log entries of dropped/rejected packets (normally sent to /var/log/messages) to the console of the first virtual terminal. If I ignore this, after about a day the first virtual tty will become unusable. After another day or so, other things (including the 'net connection over eth0) begin going down. After reboot - all's well for another five days. The Athlon box did this once before under a heavier barrage (lots of dropped packets after I put a game server on it; was filtering out a huge block of IP addresses intentionally) but seems to be much better-behaved than the K6-III; it's been up now for about three weeks (I had to shut it down to install a new CD-ROM drive) without any problems. I've tested the RAM thoroughly; can't seem to find the problem. This machine was up for over 200 days previous to the upgrade to RedHat 7.2. I doubt that it's the CPU or the motherboard. When you figure out what's causing your problem, would you be so kind as to let me know what your fix was? Thanks in advance -- Bob On Tue, 26 Feb 2002, Darrell Dieringer wrote: > Hello, > > Every fourteen days, I need to reboot my firewall/ nat box (RH 7.2 > ker 2.4.17 ipt 1.2.4) in order to restore Internet connectivity to my > NAT-ed private LAN. Last night I had been browsing the web from a LAN > machine just fine. I came back twenty mintues later and I had no > connectivity to the Internet, neither from the LAN nor from the fw/nat > box directly. > > I checked "uptime" on the fw/nat box, and it was fourteen days, > fifteen minutes. So at the time it was still working, it was five > minutes before the fourteen day barrier. > > I then rebooted the fw/nat box, and Internet connectivity was > restored. > > I know others have mentioned this behavior on the list a couple of > times. Has anyone found an explanation? I'll provide any additional > information that might prove helpful. Just let me know what you need > to know. > > > Pentium 133 - 96M RAM > Three PCI NIC's > - one for external > - one serving four machines on a private LAN > - one serving a single machine in the DMZ > - all the same brand - DLink 10/100's using tulip driver > iptables modules are _not_ compiled into the kernel > RH 7.2 > ker 2.4.17 > ipt 1.2.4 > > Thank You, > > Darrell Dieringer - Madison, WI > > > -- ________________________________________ Bob Sully - Simi Valley, California, USA http://www.malibyte.net "The weather is here - wish you were beautiful." - J. Buffett
