From: "Yossi Weihs" <yw@seafire.com>
To: "'Jan Engelhardt'" <jengelh@medozas.de>
Cc: <netfilter-devel@vger.kernel.org>
Subject: RE: newbie: writing custom target, need help with getting it to work
Date: Mon, 9 Aug 2010 00:23:32 -0400 [thread overview]
Message-ID: <013501cb377a$a04e60a0$e0eb21e0$@com> (raw)
In-Reply-To: <alpine.LSU.2.01.1008082312200.20773@obet.zrqbmnf.qr>
OK - xt_TAP.ko is not getting loaded by iptables. I can modprobe it
manually, but iptables won't load it. Trying telling iptables which modprobe
to use, but no luck. xt_TEE.ko is getting loaded fine, and I cloned my
module off it ... I feel we're getting close.
-YW
-----Original Message-----
From: netfilter-devel-owner@vger.kernel.org
[mailto:netfilter-devel-owner@vger.kernel.org] On Behalf Of Jan Engelhardt
Sent: Sunday, August 08, 2010 5:13 PM
To: Yossi Weihs
Cc: netfilter-devel@vger.kernel.org
Subject: RE: newbie: writing custom target, need help with getting it to
work
On Sunday 2010-08-08 23:09, Yossi Weihs wrote:
>I have added the env variable, but saw no change.
Make sure that xt_TAP.ko is then actually loaded.
>going on? I know my module is calling xt_register_targets(), is there a
>way for me to check the contents of its tables?
iptables -vvL
should print the semi-raw dump of the table before trying to resolve
targets.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel"
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:[~2010-08-09 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 20:20 newbie: writing custom target, need help with getting it to work Yossi Weihs
2010-08-08 20:28 ` Jan Engelhardt
2010-08-08 21:09 ` Yossi Weihs
2010-08-08 21:13 ` Jan Engelhardt
2010-08-09 4:23 ` Yossi Weihs [this message]
2010-08-09 6:52 ` Jan Engelhardt
2010-08-08 20:34 ` Jan Engelhardt
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='013501cb377a$a04e60a0$e0eb21e0$@com' \
--to=yw@seafire.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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 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.