Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: iptables: User
Kernel crash. Are ipt_recent and ipt_conntrack culprit?
 

Index | Next | Previous | View Flat


vitaly_il at yahoo

Sep 17, 2007, 3:39 AM


Views: 2897
Permalink
Kernel crash. Are ipt_recent and ipt_conntrack culprit?

I run RHEL3 with kernel 2.4.21-32.0.1.ELsmp.
Yesterday morning I started to play with iptables on
this server and yesterday evening I had kernel crash
on this server.

My iptables contains just two rules, see script below

MAXHITS=70
iptables -F
rmmod ipt_recent
modprobe ipt_recent ip_pkt_list_tot=200

iptables -I INPUT -p tcp --dport 80 ! -s
10.10.10.0/24 -m state --state NEW -m recent --set
iptables -I INPUT -p tcp --dport 80 ! -s
10.10.10.0/24 -m state --state NEW -m recent
--update --seconds 60 --hitcount $MAXHITS -j LOG
--log-prefix "http_limit_test " --log-level="DEBUG"

I don't see reports about recent 2.4
kernel/ipt_recent/ip_conntrack crashes.
OTOH, this server worked many months without crashes
before I activate iptables.

Should I go to the latest RHEL3 kernel even I don't
see something relevant into kernel changelog? Other
suggestions?

Thanks
Vitaly




____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7

Subject User Time
Kernel crash. Are ipt_recent and ipt_conntrack culprit? vitaly_il at yahoo Sep 17, 2007, 3:39 AM

  Index | Next | Previous | View Flat
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.