[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] 6.2.4.2. Checking for iptables



As we hit the low and slow softballs out of the park, to build 
reputation ... <smile>


On Sun, 2 Jun 2002, Jim Wildman wrote:

> You need to disable the ipchains stuff first
> as root
> 
> service ipchains stop
> rmmod ipchains
> service iptables start
> 
> Of course, Eric's cautions still apply. 
> 
> ------------------------------------------------------------------------
> Jim Wildman, CISSP                                      jim rossberry com
> http://www.rossberry.com
> 
> On Sat, 1 Jun 2002, Eric Harrison wrote:
> 
> > 
> > Red Hat 7.3, which K12LTSP 2.1.0 is based on, uses ipchains by default.
> > You can't use iptables and ipchains at the same time. 
> > 
> > You probably will want to stick with the default ipchains rules unless you
> > know exactly what you're doing.
> > 
> > -Eric
> > 
> > On Sat, 1 Jun 2002, Greg Long wrote:
> > 
> > >Well, I have narrowed down the problem:
> > >
> > >
> > >[root server root]# iptables -L -v
> > >/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_tables.o:
> > >init_module: Device or resource busy
> > >Hint: insmod errors can be caused by incorrect module parameters,
> > >including invalid IO or IRQ parameters
> > >/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_tables.o: insmod
> > >/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_tables.o failed
> > >/lib/modules/2.4.18-3/kernel/net/ipv4/netfilter/ip_tables.o: insmod
> > >ip_tables failed
> > >iptables v1.2.5: can't initialize iptables table `filter': iptables who?
> > >(do you need to insmod?)
> > >Perhaps iptables or your kernel needs to be upgraded.
> > >[root server root]#
> > >
> > >Again on the stock 2.1.0 install - BETA8.
> > >
> > >Soo...what could cause iptables not to be set up right? I notice the IP
> > >range it hands out to clients is in the 192.168.0.x range....my Linksys
> > >BEFSR41 router hands out IP addresses to clients (which would be eth1
> > >here) are 192.168.1.x....no conflict there.  Or is there?  Does the
> > >192.168.1.101 IP it gets handed cause an issue?
> > >
> > >
> > >
> > >Greg Long
> > >http://www.maneuveringspeed.com/
> > >
> > 
> > 
> > 
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN redhat com
> > https://listman.redhat.com/mailman/listinfo/k12osn
> > For more info see <http://www.k12os.org>
> > 
> 
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://listman.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
> 

-- 
end
==================================
 .-- -... ---.. ... -.- -.--
Copyright (C) 2002 R P Herrold
      herrold owlriver com  NIC: RPH5 (US)
   My words are not deathless prose, 
      but they are mine.

       Owl River Company  
   "The World is Open to Linux (tm)"
   ... Open Source LINUX solutions ...
      info owlriver com 
         Columbus, OH





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]