From: Neil Brown MIME-Version: 1.0 Message-ID: <16646.13395.513312.673666@...253...> In-Reply-To: message from James Yonan on Tuesday July 27 References: <16645.47913.650600.619643@...253...> Subject: [Openvpn-devel] Re: [PATCH - 2 of 4] minimal change to PUSH_DEFINED Sender: openvpn-devel-admin@lists.sourceforge.net Errors-To: openvpn-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue Jul 27 03:55:02 2004 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: James Yonan Cc: openvpn-devel@lists.sourceforge.net On Tuesday July 27, jim@...41... wrote: > PUSH_DEFINED is currently unused, so overall I don't have any problem with > this. Probably when something gets written that needs PUSH_DEFINED, the > subtletes of how it should operate will become more apparent. > It was used in beta6 which is what I was working on when I found the need for this patch. In options_string, it read: if (tt && !PUSH_DEFINED(o) && !PULL_DEFINED(o)) { const char *ios = ifconfig_options_string (tt, remote, o->ifconfig_nowarn, gc); if (ios && strlen (ios)) buf_printf (&out, ",ifconfig %s", ios); } beta7 reads if (tt && o->mode == MODE_POINT_TO_POINT && !PULL_DEFINED(o)) { const char *ios = ifconfig_options_string (tt, remote, o->ifconfig_nowarn, gc); if (ios && strlen (ios)) buf_printf (&out, ",ifconfig %s", ios); } which may well be fixing the same problem that I saw. NeilBrown