ip_tables_names not showing any results.. please help

ip_tables_names not showing any results.. please help

[123plaza Malls]

Hi All,

Please forgive my ignorance, but being an inexperienced linux user I
managed to break something with my iptables, mainly that now the command
"cat /proc/net/ip_tables_names" does NOT returns any tables (i.e. nat,
mangle, and filter). Is there any way to fix this?

Notes: I am using redhat 9 and firewall rules set by lokkit are working
ok. Also I reinstalled rpms for lokkit and iptables.

Thanks in Advance

-Ignacio

Re: ip_tables_names not showing any results.. please help

[Antony Stone]

On Sunday 02 May 2004 5:58 pm, 123plaza Malls wrote:

> Hi All,
>
> Please forgive my ignorance, but being an inexperienced linux user I
> managed to break something with my iptables

What were you doing when it broke?   Recompiling your kernel?   Recompiling 
iptables?   Fiddling with the startup scripts?  Un/Installing netfilter RPMs?

The /proc filesystem is a window into the innards of your kernel, so I suspect 
you've recompiled or loaded a kernel which does not have netfilter support, 
or you have unloaded all your netfilter modules (I'm not quite sure if that 
last one would cause this as I don't use modules, but it seems likely).

Regards,

Antony.

-- 
The difference between theory and practice is that in theory there is no 
difference, whereas in practice there is.

                                                     Please reply to the list;
                                                           please don't CC me.

Re: ip_tables_names not showing any results.. please help

[ignaciob]

> On Sunday 02 May 2004 5:58 pm, 123plaza Malls wrote:
>
>> Hi All,
>>
>> Please forgive my ignorance, but being an inexperienced linux user I
>> managed to break something with my iptables
>
> What were you doing when it broke?   Recompiling your kernel?
> Recompiling
> iptables?   Fiddling with the startup scripts?  Un/Installing netfilter
> RPMs?

The last thing I remember doing was 2 things:

1) Modify a script I use via cron.hourly used to clear iptables blocking
entries set by portsentry, AND made a mistake when calling a command to
clear history files. The script with the mistake looks like this:

----%<-----------------------------------------
#!/usr/bin/perl

# Script: iptables.restart
#
# Use on cron.hourly to restart (flush) iptables that may be
# polluted with ecessive IPs blocked by portsentry intrusion
# detection
#
# IMPORTANT NOTE:
#
# Change the next line to 0 instead of 1 to enable this script.
# By default it will be disabled and will not do anything.
#

$disabled = 0;

exit if $disabled;

# Clear and reload original iptables file
my $results_01 = `service iptables restart` or print STDERR "couldn't exec
\"service iptables restart\": $!";

# Clear porsentry local blocked history files
my $results_02 = `/bin/cat /dev/null > /bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.atcp`;

my $results_03 = `/bin/cat /dev/null > /bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.audp`;

my $results_04 = `/bin/cat /dev/null > /bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.stcp`;

my $results_05 = `/bin/cat /dev/null > /bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.sudp`;

my $results_06 = `/bin/cat /dev/null > /bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.tcp`;

my $results_07 = `/bin/cat /dev/null > /bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.udp`;

When run the script bombed, although do not see how this could have caused
the problem other that the faulty lines where executed immediately after
restarting iptables. Notice the errors in the double entries for
"`/bin/cat /dev/null > ", the correct code should be:

my $results_02 = `/bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.atcp`;

my $results_03 = `/bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.audp`;

my $results_04 = `/bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.stcp`;

my $results_05 = `/bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.sudp`;

my $results_06 = `/bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.tcp`;

my $results_07 = `/bin/cat /dev/null >
/var/log/portsentry/portsentry.blocked.udp`;


2) Other than this recently upgraded the kernel to latest (rpm) version
from redhat

Is any way I can get things back to normal again?



-----------------------------------------
This email was sent using SquirrelMail.
   "Webmail for nuts!"
http://squirrelmail.org/

Re: ip_tables_names not showing any results.. please help

[Antony Stone]

On Sunday 02 May 2004 8:49 pm, ignaciob@123plaza.com wrote:

> > On Sunday 02 May 2004 5:58 pm, 123plaza Malls wrote:
> >> Hi All,
> >>
> >> Please forgive my ignorance, but being an inexperienced linux user I
> >> managed to break something with my iptables
> >
> > What were you doing when it broke?   Recompiling your kernel?
> > Recompiling
> > iptables?   Fiddling with the startup scripts?  Un/Installing netfilter
> > RPMs?
>
> The last thing I remember doing was 2 things:
>
> 1) Modify a script I use via cron.hourly used to clear iptables blocking
> entries set by portsentry, AND made a mistake when calling a command to
> clear history files.
>
> 2) Other than this recently upgraded the kernel to latest (rpm) version
> from redhat

I would say that item number 2 has caused your problem.

1. Reboot using the previous kernel version and check whether the problem goes 
away.

2. Check whether the new kernel includes netfilter support.

3. Check (if you are using modules) whether you have the correct version of 
netfilter modules for the new kernel.

4. If none of the above solves the problem, ask on a Red Hat support mailing 
list.

Regards,

Antony.

-- 
There's no such thing as bad weather - only the wrong clothes.

 - Billy Connolly

                                                     Please reply to the list;
                                                           please don't CC me.