From: Askar Ali Khan <askarali@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: How to upgrade iptables
Date: Wed, 30 Jun 2004 10:41:58 +0500 [thread overview]
Message-ID: <a0f69e504062922425fbe9f12@mail.gmail.com> (raw)
In-Reply-To: <200406291602.37397.Antony@Soft-Solutions.co.uk>
yes use the same method if for remving iptable (binary package) you
used to installed it for example if it is RH or FC then use rpm -e
iptables or removepkg iptables (for slack)
and other method for other distros.
:)
On Tue, 29 Jun 2004 16:02:37 +0100, Antony Stone
<antony@soft-solutions.co.uk> wrote:
>
> On Tuesday 29 June 2004 3:44 pm, boka wrote:
>
> > Hi !
> >
> > After sucessfully build of new version of iptables, i have checked if
> > the rules are ok to new version. My previous version was 1.2.10.
>
> Did you previously build 1.2.10 on your system in the same way?
>
> If not (eg: if you installed one from a package manager, and you build the
> other from source), then you may have two different binaries (plus various
> bits of libraries) in more than one place on your system.
>
> As a quick check, what does "whereis iptables" suggest?
>
> For a longer list of files involved, see whether "locate iptables" seems to
> show duplicates etc.
>
> If you do have more than one version installed, I suggest removing the older
> one (using the same method as was used to install it), and then reinstalling
> the new one.
>
> If you built them both from source, make sure the install paths are the same
> on both occasions.
>
> I've commonly seen iptables in either /sbin or /usr/sbin, and sometimes even
> /usr/local/sbin
>
> Hope this helps,
>
> Regards,
>
> Antony.
>
> --
> Most people have more than the average number of legs.
>
> Please reply to the list;
> please don't CC me.
>
>
prev parent reply other threads:[~2004-06-30 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 14:44 How to upgrade iptables boka
2004-06-29 15:02 ` Antony Stone
2004-06-30 5:41 ` Askar Ali Khan [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=a0f69e504062922425fbe9f12@mail.gmail.com \
--to=askarali@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox