Matthias Andree said:
> On Tue, 30 Mar 2004, James Yonan wrote:
>
> > OpenVPN 2.0 -- Project Update and Release Notes
> >
> > I'm happy to announce that the first OpenVPN 2.0 beta is here, and well
> > ahead
> > of schedule. This is in large part thanks
On Tue, 30 Mar 2004, James Yonan wrote:
> OpenVPN 2.0 -- Project Update and Release Notes
>
> I'm happy to announce that the first OpenVPN 2.0 beta is here, and well ahead
> of schedule. This is in large part thanks to a generous contribution by
> Meetrix Inc. which has allowed me to work
On Wed, 31 Mar 2004 18:39:45 -, you wrote:
>Arkadiusz Patyk said:
>
>> Hi
>>
>> Two very significant things for me are:
>> 1. In my configurations, VPN users have different rights to resources
>> (access list on firewall - iptables). I have to know client IP to
>>
Arkadiusz Patyk said:
> Hi
>
> Two very significant things for me are:
> 1. In my configurations, VPN users have different rights to resources
> (access list on firewall - iptables). I have to know client IP to
> correctly setup firewall, how can i do this in 2.x ? How can
hi,
here is my small patch for the spec.in file in order not to overwrite
the old config files.
--- openvpn.spec.in.lfarkas 2004-03-31 18:11:14.0 +0200
+++ openvpn.spec.in 2004-03-31 18:13:25.0 +0200
@@ -34,9 +34,9 @@
%__install -c -m 755 %{name}.8
On Wed, Mar 31, 2004 at 12:31:13PM +0200, Alberto Gonzalez Iniesta wrote:
> Debian package available (for testing/unstable) at:
>
> http://tmp.inittab.org/~agi/openvpn_2.0_beta18-1_i386.deb
>
Sorry, that should read:
http://tmp.inittab.org/~agi/openvpn_2.0_test18-1_i386.deb
It's a test
On Tue, Mar 30, 2004 at 11:15:45PM -, James Yonan wrote:
> OpenVPN 2.0 -- Project Update and Release Notes
>
> I'm happy to announce that the first OpenVPN 2.0 beta is here, and well ahead
> of schedule. This is in large part thanks to a generous contribution by
> Meetrix Inc. which has
James Yonan wrote:
Farkas Levente said:
first of all THANKS!
James Yonan wrote:
* Add an internal routing capability to the OpenVPN server to allow
client-to-client communication, without going through the tun interface on the
server.
why this is needed? ans what