Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0B9E8200BB4 for ; Tue, 1 Nov 2016 12:01:26 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0A46E160AF7; Tue, 1 Nov 2016 11:01:26 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 46837160AE5 for ; Tue, 1 Nov 2016 12:01:25 +0100 (CET) Received: (qmail 18191 invoked by uid 500); 1 Nov 2016 11:01:24 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 18180 invoked by uid 99); 1 Nov 2016 11:01:24 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Nov 2016 11:01:24 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id F1622E0FC4; Tue, 1 Nov 2016 11:01:23 +0000 (UTC) From: wido To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1743: CLOUDSTACK-8326: Always fill UDP checksums in DHCP r... Content-Type: text/plain Message-Id: <20161101110123.F1622E0FC4@git1-us-west.apache.org> Date: Tue, 1 Nov 2016 11:01:23 +0000 (UTC) archived-at: Tue, 01 Nov 2016 11:01:26 -0000 Github user wido commented on the issue: https://github.com/apache/cloudstack/pull/1743 Thanks @ustcweizhou for the pointer. It was already fixed in fw_router, but not in fw_vpcrouter there. How does this look? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---