From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Duplicate files created by 'iptables 1.6.0' and 'ebtables 2.0.10-4'
Date: Fri, 08 Apr 2016 23:42:03 +0200 [thread overview]
Message-ID: <570825AB.1020907@ipfire.org> (raw)
In-Reply-To: <1460142217.30749.408.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Hi,
On 08.04.2016 21:03, Michael Tremer wrote:
> Are you sure we have the requirements switched on in our kernel?
No, I'm definitely NOT sure! I'm not so deep into the current kernel
options to make a secure statement about this.
Furthermore, since I'm at work again (holidays are over, *sigh*), I
hadn't the time to test this more extensive. I had to put it on my long
term ToDo-list. The last build - without 'ebtables' - was built without
errors, but I didn't test it ONLINE yet! Right now I have the feeling
this will require a lot of adjustments to get it really running.
For now, the best will be to stay on the current release.
Best,
Matthias
> -Michael
>
> On Fri, 2016-04-01 at 17:06 +0200, Matthias Fischer wrote:
>> Hi,
>>
>> On 01.04.2016 08:21, Matthias Fischer wrote:
>> >
>> > >
>> > > >
>> > > > Maybe we should stay on the last release?!
>> > For now, I'd say 'Yes'! I'll take a closer look at it!
>> For the records:
>> Right now I'm running a testbuild, based on 'next', with 'iptables
>> 1.6.0' but *without* 'ebtables'. We'll see.
>>
>> Best,
>> Matthias
>>
>
next prev parent reply other threads:[~2016-04-08 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2016-03-29 18:37 Matthias Fischer
2016-03-29 21:00 ` Michael Tremer
2016-03-29 22:06 ` 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=570825AB.1020907@ipfire.org \
--to=matthias.fischer@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