From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: NAT issues on a VPN tunnel
Date: Fri, 5 Nov 2004 11:57:39 -0500 [thread overview]
Message-ID: <20041105165739.GA1553@bender.817west.com> (raw)
In-Reply-To: <CARBON5MNNmPrdKz1EQ00002b82@carbon.netsvcs.com>
On Fri, Nov 05, 2004 at 08:44:05AM -0800, Chris Lyon wrote:
> I am still trying to get a match rule going but it is saying something about
> libipt_match.so not being loaded. I did try to load it but it can't so I am
> digging around the kernel to find out what the hell is missing.
libipt_*.so are library file for the iptables command, not the kernel.
i am not aware of any file called "libipt_match.so" so i'm not sure what
that error means...but you need to be looking at the iptables side of
things, not the kernel.
are your kernel and userspace out of sync (i.e. you patched your kernel
from POM, and rebuilt the kernel but not the iptables package)?
-j
--
"I'll be deep in the cold, cold ground before I recognize Missoura!"
--The Simpsons
next prev parent reply other threads:[~2004-11-05 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 0:35 NAT issues on a VPN tunnel Christopher Lyon
2004-11-03 2:43 ` Jason Opperisano
2004-11-03 10:48 ` John A. Sullivan III
[not found] ` <CARBONunxtkVO4alvoN00002350@carbon.netsvcs.com>
2004-11-03 15:49 ` Jason Opperisano
2004-11-05 6:42 ` Chris Lyon
2004-11-05 10:40 ` John A. Sullivan III
2004-11-05 16:44 ` Chris Lyon
2004-11-05 16:57 ` Jason Opperisano [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 15:40 Chris Lyon
2004-11-02 16:09 ` John A. Sullivan III
2004-11-02 17:02 ` Chris Lyon
2004-11-02 18:49 ` John A. Sullivan III
2004-11-02 20:05 ` Chris Lyon
2004-11-03 0:27 ` John A. Sullivan III
2004-11-03 0:24 ` Jason Opperisano
2004-11-03 15:06 ` Michael Gale
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=20041105165739.GA1553@bender.817west.com \
--to=opie@817west.com \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.