Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ryan Pagquil <ryan_pagquil@axisglobal.com>
To: fabrice@netfilter.org
Cc: netfilter@lists.netfilter.org
Subject: Re: where can i find libipt_ipv4options.so?
Date: Wed, 14 Jul 2004 08:29:55 +0000	[thread overview]
Message-ID: <1089793795.3044.245.camel@mis1> (raw)
In-Reply-To: <200407141407.44978.fabrice@netfilter.org>

fabrice,
	i'm new in patching iptables, would you mind if you give me some
instructions done by you, so that i can based my procedure with the one
you have done? 
	why does some package of iptables in other distributions includes
libipt_ipv4options.so? just curious....

thanks for the help,

On Wed, 2004-07-14 at 06:07, Fabrice MARIE wrote:
> Hello,
> 
> On 13 July 2004 pm 17:20, Ryan Pagquil wrote:
> > Guys,
> > 	I'm generating scripts using FWBuilder, when i specify IP protocol on
> > my firewall rules and compile it then run the script generated by
> > FWBuilder, iptables prompt me that libipt_ipv4options.so file can't be
> > found. how can i install this file?
> 
> Downoad the latest version of iptable from CVS, latest version of patch-o-matic-ng from
> CVS. Then patch your kernel with the ipv4options patch. Recompile and install your new kernel.
> Recompile and install your new iptables tool. Then it should work.
> 
> Have a nice day,
> 
> Fabrice.
> --
> Fabrice MARIE
> 
> "Silly hacker, root is for administrators"
>        -Unknown
-- 
Ryan



  reply	other threads:[~2004-07-14  8:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13  9:20 where can i find libipt_ipv4options.so? Ryan Pagquil
2004-07-14  6:07 ` Fabrice MARIE
2004-07-14  8:29   ` Ryan Pagquil [this message]
2004-07-15  5:32     ` Fabrice MARIE
2004-07-15  6:32       ` Ryan Pagquil
2004-07-15  8:19       ` Ryan Pagquil
2004-07-22  7:41   ` Ryan Pagquil

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=1089793795.3044.245.camel@mis1 \
    --to=ryan_pagquil@axisglobal.com \
    --cc=fabrice@netfilter.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox