From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Duplicate files created by 'iptables 1.6.0' and 'ebtables 2.0.10-4'
Date: Tue, 29 Mar 2016 22:00:15 +0100 [thread overview]
Message-ID: <1459285215.30749.226.camel@ipfire.org> (raw)
In-Reply-To: <56FACB57.1070109@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
Hi,
this actually should not happen. Why is iptables building ebtables stuff? Have
these two been merged? Can you disable it?
-Michael
On Tue, 2016-03-29 at 20:37 +0200, Matthias Fischer wrote:
> Hi,
>
> As I wrote before I'm testing with 'iptables 1.6.0'.
>
> While looking which files I would need to backup so I could run some
> tests on my production machine I found that 'iptables 1.6.0' and current
> 'ebtables 2.0.10-4' are building duplicate files.
>
> 'ebtables' puts them in '/usr/lib', 'iptables 1.6.0' in '/lib/xtables':
>
> libebt_802_3.so
> libebt_ip.so
> libebt_log.so
> libebt_mark_m.so
>
> What would be the best way to handle this? Comment in (which?) rootfile?
>
> As an info:
> 'iptables 1.6.0' was build with the new option '--disable-nftables',
> otherwise build failed: "fatal error: libnftnl/rule.h: No such file or
> directory".
>
> Best,
> Matthias
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-29 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 18:37 Matthias Fischer
2016-03-29 21:00 ` Michael Tremer [this message]
2016-03-29 22:06 ` Matthias Fischer
[not found] <1459464825.30749.255.camel@ipfire.org>
2016-04-01 6:21 ` Matthias Fischer
2016-04-01 15:02 ` Matthias Fischer
2016-04-01 15:06 ` Matthias Fischer
2016-04-08 19:03 ` Michael Tremer
2016-04-08 21:42 ` Matthias Fischer
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=1459285215.30749.226.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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