Re: [Openvpn-devel] OpenVPN 2.3.0 released

Hi all, Samuli Seppänen wrote: The OpenVPN community project team is proud to release OpenVPN 2.3.0. It can be downloaded from here: This release includes two bug fixes. A full list of changes is available here:

[Openvpn-devel] OpenVPN 2.3.0 released

The OpenVPN community project team is proud to release OpenVPN 2.3.0. It can be downloaded from here: This release includes two bug fixes. A full list of changes is available here:

Re: [Openvpn-devel] Correct Man Page: client-to-client

On Tue, 8 Jan 2013 07:41:59 -0600, Eric Crist wrote: > I'm certain this is the behavior for TAP, but I'll do some due-dilligence > and generate a few different scenarios and verify. It's entirely > possible this behavior is only present with the TAP adapter. I'll post > my findings later this w

Re: [Openvpn-devel] Correct Man Page: client-to-client

I'm certain this is the behavior for TAP, but I'll do some due-dilligence and generate a few different scenarios and verify. It's entirely possible this behavior is only present with the TAP adapter. I'll post my findings later this week. - Eric F Crist On Jan 8, 2013, at 02:52:01, Ge

[Openvpn-devel] fix build with automake 1.13(.1)

Hello everybody, AM_CONFIG_HEADER has been deprecated for some time, finally it is removed on automake 1.13. The attached patch replaces it with AC_CONFIG_HEADERS and fixes build process with latest automake. Please apply. -- main(a){char*c=/*Schoene Gruesse */"B?IJj;M

Re: [Openvpn-devel] Correct Man Page: client-to-client

Hi, On Mon, Jan 07, 2013 at 09:38:02PM +0100, Davide Brini wrote: > The current documentation looks correct to me. When using client-to-client, > traffic is not exposed on the tun interface; when not using > client-to-client, traffic shows up on the tun interface and can be > firewalled (eg with i