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

RE: [K12OSN] 6.2.4.2. Checking for iptables



Unfortuntately, this does no good either.

I wonder why both services start in this defualt install if both can't
run at the same time?

I modified ipchains not to start but iptables still produces a similar
message, and suggests doing something with insmod.

It does the same thing even after a clean reinstall with ONLY one card -
eth0 which is the former eth1 when both were installed so we know it
works.

I might just try this on a different box, I just don't see how it could
be hardware when it runs RH7.3 without problem with one NIC, and even
the K12LTSP fine with network connectivity through eth1 when both NICS
are in.  This box isn't going to run a K12LTSP for long anyways, it's
just the most powerful one I have which could support several clients.

-----Original Message-----
From: k12osn-admin redhat com [mailto:k12osn-admin redhat com] On Behalf
Of Jim Wildman
Sent: Sunday, June 02, 2002 7:15 AM
To: k12osn redhat com
Subject: Re: [K12OSN] 6.2.4.2. Checking for iptables


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>





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