Enable ipv6 addresses in Firewall logs
| Message ID | 568E5375.1040906@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 7056E60EC8 for <patchwork@ipfire.org>; Thu, 7 Jan 2016 13:01:00 +0100 (CET) Received: from hedwig.ipfire.org (localhost [IPv6:::1]) by mail01.ipfire.org (Postfix) with ESMTP id 0C263A78; Thu, 7 Jan 2016 13:01:00 +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 F20A8A5F for <development@lists.ipfire.org>; Thu, 7 Jan 2016 13:00:57 +0100 (CET) Received: (qmail 11713 invoked from network); 7 Jan 2016 12:00:56 -0000 Received: from unknown (HELO mail.eitelwein.net) (postmaster@bncmfdox.mail.selfhost.de@93.229.67.100) by mailout.selfhost.de with ESMTPA; 7 Jan 2016 12:00:56 -0000 Received: from localhost (mail.eitelwein.net [IPv6:2001:4dd0:ff00:89e5::208]) by mail.eitelwein.net (Postfix) with ESMTP id C6BA4238 for <development@lists.ipfire.org>; Thu, 7 Jan 2016 13:00:53 +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 N2UC3wtNVD7p for <development@lists.ipfire.org>; Thu, 7 Jan 2016 13:00:53 +0100 (CET) Received: from [IPv6:2001:4dd0:ff00:89e5:2437:bfa4:d2bb:2c74] (unknown [IPv6:2001:4dd0:ff00:89e5:2437:bfa4:d2bb:2c74]) by mail.eitelwein.net (Postfix) with ESMTPSA id 90BB6EA for <development@lists.ipfire.org>; Thu, 7 Jan 2016 13:00:53 +0100 (CET) To: development@lists.ipfire.org From: Michael Eitelwein <michael@eitelwein.net> Subject: [PATCH] Enable ipv6 addresses in Firewall logs Message-ID: <568E5375.1040906@eitelwein.net> Date: Thu, 7 Jan 2016 13:00:53 +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. 7, 2016, 11 p.m. UTC
Enable correct display of ipv6 entries in Firewall log pages of web UI.
3 main changes:
- Fill $iface and $out from PHYSIN and PHYSOUT when looking at bridged packets, othwerwise fill from IN and OUT
- Recognize ipv4 and ipv6 address style for $srcaddr and $dstaddr
- Match color coding of tables to pie charts (see seperate patch sent earlier)
I am using the bridged ipv6 setup as proposed in the wiki. I do not think this breaks anything when not using ipv6. So it would be nice to include this even if ipv6 is not officially supported yet. It is quite useful when using the ipv6 setup.
Signed-off-by: Michael Eitelwein <michael@eitelwein.net>
---