The kernel has just been upgraded on my server to 2.4.24 by the datacenter, but I noticed in the messages log the following messages when restarting shorewall: Jan 7 11:24:00 hera modprobe: modprobe: Can''t locate module iptable_nat Jan 7 11:24:00 hera modprobe: modprobe: Can''t locate module iptable_nat Jan 7 11:24:02 hera projnet1: Shorewall Restarted Should I be worried? The server is used for webhosting, and only connected to one network. Thanks! -- Andrew Allen e:: mail@projectandrew.com // t:: +44 (0) 7958 540 596 w:: www.projectandrew.com \\ f:: +44 (0) 8704 601 527 yahoo! messenger: aa_projectandrew skype: aa_projectandrew
--- Andrew Allen <mail@projectandrew.com> wrote:> The kernel has just been upgraded on my server to 2.4.24 by the > datacenter, but > I noticed in the messages log the following messages when restarting > shorewall: > > Jan 7 11:24:00 hera modprobe: modprobe: Can''t locate module > iptable_nat > Jan 7 11:24:00 hera modprobe: modprobe: Can''t locate module > iptable_nat > Jan 7 11:24:02 hera projnet1: Shorewall Restarted > > Should I be worried? The server is used for webhosting, and only > connected to > one network.Andrew did you upgrade the Kernel or did someone else? I think what might of happened is that they didn''t use your previous netfilter kernel selections in "menu config" I would check you Kernel Netfilter selections just to make sure. If this isn''t the case then maybe its the kernel headers from the new kernel that shorewall isn''t recognizing. In that case just make a back-up of your shorewall config files and uninstall and reinstall shorewall and then copy your old shorewall config files back to the newly install /shorewall directory. I suspect you should look at your kernel menu selections first though to make sure that you have all the nesseccary modules loaded or built into the kernel. You can use Tom''s menu selections as an example at: http://www.shorewall.net/kernel.htm But I''m sure Tom or someone else will have a more complete understanding of what you need to do. You can check the Kernel in the mean time though just to get that out of the way. HTH''s, Joshua Banks __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
On Wednesday 07 January 2004 04:02 am, Joshua Banks wrote:> --- Andrew Allen <mail@projectandrew.com> wrote: > > The kernel has just been upgraded on my server to 2.4.24 by the > > datacenter, but > > I noticed in the messages log the following messages when restarting > > shorewall: > > > > Jan 7 11:24:00 hera modprobe: modprobe: Can''t locate module > > iptable_nat > > Jan 7 11:24:00 hera modprobe: modprobe: Can''t locate module > > iptable_nat > > Jan 7 11:24:02 hera projnet1: Shorewall Restarted > > > > Should I be worried? The server is used for webhosting, and only > > connected to > > one network. > > Andrew did you upgrade the Kernel or did someone else? > > I think what might of happened is that they didn''t use your previous > netfilter kernel selections in "menu config" > > I would check you Kernel Netfilter selections just to make sure. If > this isn''t the case then maybe its the kernel headers from the new > kernel that shorewall isn''t recognizing.Shorewall isn''t generating those messages (at least not directly). Shorewall uses ''insmod'' rather than ''modprobe''. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net
On Wednesday 07 January 2004 07:24 am, Tom Eastep wrote:> > Shorewall isn''t generating those messages (at least not directly). > Shorewall uses ''insmod'' rather than ''modprobe''. >FWIW, I just brought up 2.4.24 on my own gateway and I''m not seeing these messages. You can check /lib/modules/2.4.24/kernel/net/ipv4/netfilter to see what modules you *do* have. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net