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 83585200B76 for ; Tue, 30 Aug 2016 16:40:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 81D70160ABA; Tue, 30 Aug 2016 14:40:25 +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 C1EB3160AAF for ; Tue, 30 Aug 2016 16:40:24 +0200 (CEST) Received: (qmail 25804 invoked by uid 500); 30 Aug 2016 14:40:23 -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 25793 invoked by uid 99); 30 Aug 2016 14:40:23 -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, 30 Aug 2016 14:40:23 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 7568DE040F; Tue, 30 Aug 2016 14:40:23 +0000 (UTC) From: serg38 To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1668: Fixing test_router_dhcp outside ping response as it ... Content-Type: text/plain Message-Id: <20160830144023.7568DE040F@git1-us-west.apache.org> Date: Tue, 30 Aug 2016 14:40:23 +0000 (UTC) archived-at: Tue, 30 Aug 2016 14:40:25 -0000 Github user serg38 commented on the issue: https://github.com/apache/cloudstack/pull/1668 @borisstoyanov This PR can be probably closed since the issue with correct ping responses is being addressed globally in PR1651 --- 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. ---