Scott, thank you for the advice.
I read that DachStein was the LRP of choice now. Not to hot on switching but will if I must. I spent many hours getting the router to pass my VPN so I can plug in for work at home. Got it to work and when I ran one of those external firewall testers it still showed me as secure. I did it so long ago I forgot what I did. I am not looking forward to the work getting Dachstein working also. Thank you again. ----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, January 14, 2002 12:29 PM Subject: Re: [Leaf-user] Message log Overflow crashes EigerStein > Greg: > Heya. You got three options to fix this; used to kill me > too. First, you could upgrade your EigerStein box to a Dachstein > one. The Dachstein series puts log files on a separate ram-disk > partition, so even if that disk fills up, the router still works. > > That will keep you running, but it won't keep your disk > from filling. To do *that* you could experiment with the SILENT_DENY > field in the network.conf file. Since you're on a cable modem > environment, you're going to see lotsa noise from other people's > networks, such as the DHCP requests you typed in below. > > Lastly, you may want to give echowall.lrp a try. I built > it on my Eigerstein box on a cable-modem environment, so I was > very sensitive to minimizing what gets logged and what is, by > default, silently denied. You can see in the echowall.rules file > a much more aggressive "don't log this noise" list than what comes > stock on the Dachstein distribution. > > Hope this helps! > > -Scott > > > I am a novice with linux and the EigerStein router has run flawlessly for > > many months on my old 486. > > > > The last week My router crashes every 1-2 days and I have to restart it. > > > > The message log seems to overflow with the following: and 10.38.64.1 is > > not an IP address assigned by either me or my provider. > > > > Any ideas on how to make the EigerStein handle this better? > > > > I tried the suggestion on Domain Spaming by Victor form 6/9/2001 (dns floods > > port 53) but is seems to have no effect. > > I have tried changing the port in his solution to both 67 and 68 still no > > effect! > > > > Any help would be appreciated. I do not want to have to run out and buy a > > router. but don't know what to do. > > > > GregO > > > > Jan 13 20:05:40 myrouter kernel: Packet log: input DENY eth0 PROTO=17 > > 10.38.64.1:67 255.255.255.255:68 L=340 S=0x00 I=24287 F=0x0000 T=255 (#9) > > > > > > _______________________________________________ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
