Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A8FD718DA1 for ; Fri, 11 Dec 2015 17:56:50 +0000 (UTC) Received: (qmail 31954 invoked by uid 500); 11 Dec 2015 17:56:50 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 31898 invoked by uid 500); 11 Dec 2015 17:56:50 -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 31887 invoked by uid 99); 11 Dec 2015 17:56:50 -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; Fri, 11 Dec 2015 17:56:50 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id DFA5DE057A; Fri, 11 Dec 2015 17:56:49 +0000 (UTC) From: wilderrodrigues To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: Setup routes for RFC 1918 ip space Content-Type: text/plain Message-Id: <20151211175649.DFA5DE057A@git1-us-west.apache.org> Date: Fri, 11 Dec 2015 17:56:49 +0000 (UTC) Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/1214#issuecomment-164003619 Put some time in reading the RFC - yes, I actually did - and also went through the code (with the latest changes). It LGTM :+1: I think last @terbolous comment was sent just after @remibergsma made the change, which checks if the pub IP is within the range reserved by the RFC. Thanks for the fix, @remibergsma ! Cheers, Wilder --- 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. ---