From: "Ukeme Noah" <ukeme.noah@gmail.com>
To: netfilter@vger.kernel.org, Steven Stromer <filter@stevenstromer.com>
Subject: Re: possible bug in call to libipt_state
Date: Mon, 31 Mar 2008 16:44:33 -0400 [thread overview]
Message-ID: <007801c89370$0848fb40$0600a8c0@windowsnxfi> (raw)
In-Reply-To: filter-4B6EC6.16121031032008@ger.gmane.org
What steps did you follow to debug your script before this conclusion.
ukeme noah
----- Original Message -----
From: "Steven Stromer" <filter@stevenstromer.com>
To: <netfilter@vger.kernel.org>
Sent: Monday, March 31, 2008 4:12 PM
Subject: possible bug in call to libipt_state
> Hi,
>
> On FC8, kernel 2.6.24.3-50.fc8 (and earlier, actually), iptables v1.3.8, I
> am receiving the following error when trying to load rules from a shell
> script:
>
> Couldn't load match '-state':/lib64/iptables/libipt_-state.so: cannot open
> shared object file: No such file or directory
>
> In fact, there is no such file or directory, because the call is being
> incorrectly made to 'libipt_-state.so', instead of 'libipt_state.so':
>
> # ls -la /lib64/iptables | grep state
> -rwxr-xr-x 1 root root 6888 2007-11-05 12:08 libip6t_state.so
> -rwxr-xr-x 1 root root 6888 2007-11-05 12:08 libipt_state.so
>
> I am not at all certain whether this is a problem in the Fedora iptables
> package, the kernel, or iptables itself. If anyone could help me locate
> the source of the call, and could also confirm that this really is a bug,
> I'll happily report it!
>
> Thanks,
> Steven Stromer
>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-31 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 20:12 possible bug in call to libipt_state Steven Stromer
2008-03-31 20:44 ` Ukeme Noah [this message]
2008-03-31 20:46 ` Eljas Alakulppi
2008-04-03 3:54 ` [solved] " Steven Stromer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='007801c89370$0848fb40$0600a8c0@windowsnxfi' \
--to=ukeme.noah@gmail.com \
--cc=filter@stevenstromer.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox