As I recall, Sunday the 12th, I used YaST2 to update the Kernel. Today I upgraded and existing shorewall to 2.4.0 In my syslog I get: Jun 15 14:27:14 mymachine modprobe: FATAL: Could not load /lib/modules/2.6.8-24.14-default/modules.dep: No such file or directory On the terminal when restarting I get: FATAL: Could not load /lib/modules/2.6.8-24.14-default/modules.dep: No such file or directory ip6tables v1.2.11: can''t initialize ip6tables table `filter'': iptables who? (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. Did I accidentally turn on IPv6 ? Shorewall status says it''s running - do I believe it ? Should I back off to the prior version of shorewall ? Environment SuSE 9.2 running 2.6.8 Kernel - Bill
As I recall, Sunday the 12th, I used YaST2 to update the Kernel. Today I upgraded and existing shorewall to 2.4.0 In my syslog I get: Jun 15 14:27:14 mymachine modprobe: FATAL: Could not load /lib/modules/2.6.8-24.14-default/modules.dep: No such file or directory On the terminal when restarting I get: FATAL: Could not load /lib/modules/2.6.8-24.14-default/modules.dep: No such file or directory ip6tables v1.2.11: can''t initialize ip6tables table `filter'': iptables who? (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. Did I accidentally turn on IPv6 ? Shorewall status says it''s running - do I believe it ? Should I back off to the prior version of shorewall ? Environment SuSE 9.2 running 2.6.8 Kernel ========================================= I''ll answer my own question - IPv6 did get turned on, I believe something in the YaST2 update....anyway... /etc/sysconfig/network/config very last line USE_IPV6 now set to "no" and the error is gone. - Bill
> As I recall, Sunday the 12th, I used YaST2 to update the Kernel. Today I > upgraded and existing shorewall to 2.4.0 > > In my syslog I get: > > Jun 15 14:27:14 mymachine modprobe: FATAL: Could not load > /lib/modules/2.6.8-24.14-default/modules.dep: No such file or directoryDid you boot the new kernel after updating it? Simon> > On the terminal when restarting I get: > > FATAL: Could not load /lib/modules/2.6.8-24.14-default/modules.dep: No > such file or directory > ip6tables v1.2.11: can''t initialize ip6tables table `filter'': iptables > who? (do you need to insmod?) > Perhaps iptables or your kernel needs to be upgraded. > > Did I accidentally turn on IPv6 ? Shorewall status says it''s running - do > I believe it ? Should I back off to the prior version of shorewall ? > > Environment SuSE 9.2 running 2.6.8 Kernel > > =========================================> > I''ll answer my own question - IPv6 did get turned on, I believe something > in the YaST2 update....anyway... /etc/sysconfig/network/config very > last line > > USE_IPV6> > now set to "no" and the error is gone. > > - Bill > > _______________________________________________ > Shorewall-users mailing list > Post: Shorewall-users@lists.shorewall.net > Subscribe/Unsubscribe: > https://lists.shorewall.net/mailman/listinfo/shorewall-users > Support: http://www.shorewall.net/support.htm > FAQ: http://www.shorewall.net/FAQ.htm > >
> As I recall, Sunday the 12th, I used YaST2 to update the Kernel. TodayI> upgraded and existing shorewall to 2.4.0 > > In my syslog I get: > > Jun 15 14:27:14 mymachine modprobe: FATAL: Could not load > /lib/modules/2.6.8-24.14-default/modules.dep: No such file or directoryDid you boot the new kernel after updating it? Simon> > On the terminal when restarting I get: > > FATAL: Could not load /lib/modules/2.6.8-24.14-default/modules.dep: No > such file or directory > ip6tables v1.2.11: can''t initialize ip6tables table `filter'': iptables > who? (do you need to insmod?) > Perhaps iptables or your kernel needs to be upgraded. > > Did I accidentally turn on IPv6 ? Shorewall status says it''s running -do> I believe it ? Should I back off to the prior version of shorewall ? > > Environment SuSE 9.2 running 2.6.8 Kernel > > =========================================> > I''ll answer my own question - IPv6 did get turned on, I believesomething> in the YaST2 update....anyway... /etc/sysconfig/network/config very > last line > > USE_IPV6> > now set to "no" and the error is gone. > > - Bill========================================= The reason NOT to top post.... Simon - To answer your question, Yes, I did re-boot (on that same day) it was a kernel update. If you read above - I had already answered my own question which was included below your question... I surmise, but I''m not going back to re-produce it, that something in the update set that last line to "yes". (If I recall, it was a blank because it was never set). It didn''t really slap me in the face until I then went to update shorewall to the 2.4.0 build. Appreciate you replying, though. Thanks Bill