PATCH 3/5] Firewall chain was not extracted correctly when ipv6 uses bridge
Message ID | 569296D2.8090904@eitelwein.net |
---|---|
State | Dropped |
Headers |
Return-Path: <development-bounces@lists.ipfire.org> Received: from mail01.ipfire.org (mail01.tremer.info [172.28.1.200]) by septima.ipfire.org (Postfix) with ESMTP id 6250F612C4 for <patchwork@ipfire.org>; Sun, 10 Jan 2016 18:37:27 +0100 (CET) Received: from hedwig.ipfire.org (localhost [IPv6:::1]) by mail01.ipfire.org (Postfix) with ESMTP id DD21CA87; Sun, 10 Jan 2016 18:37:26 +0100 (CET) Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=82.98.82.95; helo=outgoing.selfhost.de; envelope-from=michael@eitelwein.net; receiver=development@lists.ipfire.org Received: from outgoing.selfhost.de (out.selfhost.de [82.98.82.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPS id 29B58A54 for <development@lists.ipfire.org>; Sun, 10 Jan 2016 18:37:24 +0100 (CET) Received: (qmail 20421 invoked from network); 10 Jan 2016 17:37:23 -0000 Received: from unknown (HELO mail.eitelwein.net) (postmaster@bncmfdox.mail.selfhost.de@91.16.28.51) by mailout.selfhost.de with ESMTPA; 10 Jan 2016 17:37:23 -0000 Received: from localhost (mail.eitelwein.net [IPv6:2001:4dd0:ff00:89e5::208]) by mail.eitelwein.net (Postfix) with ESMTP id 3105921F; Sun, 10 Jan 2016 18:37:22 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at eitelwein.net Received: from mail.eitelwein.net ([192.168.123.208]) by localhost (vscan.eitelwein.net [192.168.123.208]) (amavisd-new, port 10024) with ESMTP id 6xaq_9SESlGz; Sun, 10 Jan 2016 18:37:22 +0100 (CET) Received: from [IPv6:2001:4dd0:ff00:89e5:58bd:f3ea:398b:4cbd] (unknown [IPv6:2001:4dd0:ff00:89e5:58bd:f3ea:398b:4cbd]) by mail.eitelwein.net (Postfix) with ESMTPSA id BC704A9; Sun, 10 Jan 2016 18:37:21 +0100 (CET) To: development@lists.ipfire.org From: Michael Eitelwein <michael@eitelwein.net> Subject: PATCH 3/5] Firewall chain was not extracted correctly when ipv6 uses bridge Message-ID: <569296D2.8090904@eitelwein.net> Date: Sun, 10 Jan 2016 18:37:22 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: development@lists.ipfire.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: IPFire development talk <development.lists.ipfire.org> List-Unsubscribe: <http://lists.ipfire.org/mailman/options/development>, <mailto:development-request@lists.ipfire.org?subject=unsubscribe> List-Archive: <http://lists.ipfire.org/pipermail/development/> List-Post: <mailto:development@lists.ipfire.org> List-Help: <mailto:development-request@lists.ipfire.org?subject=help> List-Subscribe: <http://lists.ipfire.org/mailman/listinfo/development>, <mailto:development-request@lists.ipfire.org?subject=subscribe> Errors-To: development-bounces@lists.ipfire.org Sender: "Development" <development-bounces@lists.ipfire.org> |
Message
Michael Eitelwein
Jan. 11, 2016, 4:37 a.m. UTC
Fixing a bug in previous patch.
Signed-off-by: Michael Eitelwein <michael@eitelwein.net>
---
html/cgi-bin/logs.cgi/firewalllog.dat | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)