From: Brian Mearns <mearns.b@gmail.com>
To: Andrew Schulman <andrex@alumni.utexas.net>
Cc: netfilter@vger.kernel.org
Subject: Re: Is p-o-m still the correct thing to use?
Date: Tue, 29 Jul 2008 06:25:54 -0400 [thread overview]
Message-ID: <488EF032.5020000@gmail.com> (raw)
In-Reply-To: <s7sl841gefisi4k0lreotlvqbmq9kfl99u@4ax.com>
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.
Thanks,
-Brian
Andrew Schulman wrote:
>> The latest version of POM seems to be from 2004, and I saw some
>> references in the mailing list archive seeming to indicate that is'
>> being deprecated, but is there anything to replace it?
>
> For POM-ng, if you look in the snapshot directory of the FTP server, you'll find
> daily versions up to yesterday. However, I recently tried to use on of those to
> install the condition patch, and it failed for reasons that I wasn't able to
> figure out in 30 mins. or so of research.
>
> POM has now been superseded by xtables-addons
> (http://jengelh.medozas.de/projects/xtables/). Unfortunately the netfilter site
> hasn't been updated yet to reflect this. Discussion threads on that in this
> forum within the last week:
>
> POM Xtables???
> patch-0-matic problems..?
>
> At first I was annoyed at yet another big change in netfilter patching, but
> xtables-addons is better because it doesn't require you to patch either your
> kernel or iptables.
>
>> I'd really like to patch in TARPITs, but the latest POM does not work
>> with the latest iptable src ("doesn't look like a iptables source code
>> directory to me.")
>
> You have to run ./configure in your iptables source dir first. Not sure if that
> used to be the case-- I think it wasn't.
>
> That gets to wny I always used to hate using POM. It was unique and volatile--
> about once a year someone would change something and my script would break and
> I'd have to go back and figure it all out again. Good riddance, I say.
>
> Good luck,
> Andrew.
>
> --
> 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-07-29 10:25 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 [this message]
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
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=488EF032.5020000@gmail.com \
--to=mearns.b@gmail.com \
--cc=andrex@alumni.utexas.net \
--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