From: "Brian Mearns" <mearns.b@gmail.com>
To: netfilter@vger.kernel.org, linux@arcoscom.com
Subject: Re: Is p-o-m still the correct thing to use?
Date: Fri, 29 Aug 2008 08:23:05 -0400 [thread overview]
Message-ID: <4df3a1330808290523j1f2de25bmcee66202cd64eefe@mail.gmail.com> (raw)
In-Reply-To: <48B7CF95.2080900@gmail.com>
No, I don't have any TARPIT modules in either folder. Does that means
I have to patch the kernel? because I thought xtables didn't require
that. Or is there a way to just copy it in?
Thanks,
-Brian
ArcosCom Linux User wrote:
>
> Has you the kernel module for TARPIT (look for it into kernel modules,
> usually into /lib/modules/$(uname -r)/kernel/net/netfilter or
> .../net/ipv4/netfilter).
>
> Or perhaps the problem was that you have the "ipt" version and the "xt"
> version and there is a problem with them at the same time.
>
> Regards
>
> El Vie, 29 de Agosto de 2008, 2:37, Brian Mearns escribió:
>>
>> Thanks for the help Jan and Andrew. I've got xtables (combined) and it
>> built and installed fine. When I run iptables --version, it matches
>> what's given in the versions file in the source distribution. My problem
>> is that the TARPIT target doesn't seem to be recognized. When I try to
>> add a rule with the TARPIT target, it says "iptables: No
>> chain/target/match by that name". I've tried using rules that work
>> otherwise, for instance, changing from DROP to TARPIT, and it still
>> doesn't work, so it's not the rest of the rule that is the problem.
>>
>> I found libxt_TARPIT.so in /usr/local/libexec/xtables/. Is it in the
>> wrong spot or something? Also, my service runs from /sbin/iptables, but
>> this is soft linked to /usr/local/sbin/iptables: could this be part of
>> the problem? I did this so my package manager doesn't overwrite it any
>> point, but maybe it was a bad idea?
>>
>> Any help would be great.
>>
>> Thanks,
>> -Brian
>>
>> Jan Engelhardt wrote:
>>>
>>> On Tuesday 2008-07-29 06:25, Brian Mearns wrote:
>>>
>>>> Thanks a lot for the help, Andrew. The iptables source I have
>>>> doesn't have a configure script...oh, but it does have an autogen
>>>> script. I guess I was probably supposed to use that first. But it's
>>>> a moot point, apparently, because of xtables, so I will be
>>>> switching to that.
>>>
>>> Released tarballs should have configure; for autogen, you usually
>>> need (even more) developer tools than you do without, like
>>> autoconf, automake, and the other autowhatevers.
>>>
>>> No moot point; iptables still is, as of today, the name of the
>>> userspace package and control program.
>>
>> --
>> 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
>>
>
>
prev parent reply other threads:[~2008-08-29 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 1:25 Is p-o-m still the correct thing to use? Brian Mearns
2008-07-26 9:52 ` Andrew Schulman
2008-07-29 10:25 ` Brian Mearns
2008-08-05 19:50 ` Jan Engelhardt
2008-08-29 0:37 ` Brian Mearns
2008-08-29 11:53 ` Jan Engelhardt
2008-08-29 12:28 ` Brian Mearns
[not found] ` <37034.89.107.243.1.1219995640.squirrel@www.arcoscom.com>
[not found] ` <48B7CF95.2080900@gmail.com>
2008-08-29 12:23 ` Brian Mearns [this message]
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=4df3a1330808290523j1f2de25bmcee66202cd64eefe@mail.gmail.com \
--to=mearns.b@gmail.com \
--cc=linux@arcoscom.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