From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2C987138206 for ; Thu, 18 Jan 2018 14:17:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 86EB9E0870; Thu, 18 Jan 2018 14:16:55 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 24657E085E for ; Thu, 18 Jan 2018 14:16:54 +0000 (UTC) Received: from [192.168.1.100] (c-98-218-46-55.hsd1.md.comcast.net [98.218.46.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id 90A47335C31 for ; Thu, 18 Jan 2018 14:16:52 +0000 (UTC) Subject: Re: [gentoo-user] openvpn client IP address To: gentoo-user@lists.gentoo.org References: <5a2fa99a-131c-4b35-8aa3-7fc0eb1ec9ea@sys-concept.com> From: Michael Orlitzky Message-ID: Date: Thu, 18 Jan 2018 09:15:55 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <5a2fa99a-131c-4b35-8aa3-7fc0eb1ec9ea@sys-concept.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Archives-Salt: 5c3c88f9-a81d-409f-a3ca-57d428fc079f X-Archives-Hash: 3a7907dede1f5e89415315f0d1f0e026 On 01/17/2018 09:51 PM, thelma@sys-concept.com wrote: > How openvpn client obtains IP address from the server? > > On the sever in server.conf I had: > server 192.168.139.0 255.255.255.0 > route 10.0.0.0 255.255.255.0 192.168.139.7 > > On server in ccd/ I had client.file: > ifconfig-push 192.168.139.3 255.255.255.0 Two things to check: First, the client configuration directory needs to be specified in the server configuration file with the "client-config-dir" directive. In your case, it looks like you need client-config-dir ccd but try an absolute path if that doesn't work for you. The second is the naming convention for the client configuration files themselves. The files in "ccd" need to match the common names on the certificates of your clients exactly, IIRC. So instead of "client.file", you probably want just "client".