Hello Kevin,
first thank you for spending your time helping to make Debian better
with this bug report.
This bug was first filled against release 2.1~rc11-1. At Debian the
last supported release is 2.4.0-6.
The error no longer occurred during a test with the current version.
So I close this 8 y
在 2010年12月20日星期一UTC+8下午7时40分02秒，openvpn.lzo-c...@spamgourmet.com写道：
> I just ran into this too on today's lenny.
>
> Adding a comp-lzo directive fixes the issue for lenny. Ie: even if it
> starts with a "no" setting, eg:
>
> openvpn --client --remote remote.example.com --cert client.cer --key
I just ran into this too on today's lenny.
Adding a comp-lzo directive fixes the issue for lenny. Ie: even if it
starts with a "no" setting, eg:
openvpn --client --remote remote.example.com --cert client.cer --key
client.key --verb 4 --dev tun --ca ca.cer --comp-lzo no
Suggestion: set it by
On Sat, Jun 20, 2009 at 07:24:14PM -0400, Kevin Otte wrote:
> Package: openvpn
> Version: 2.1~rc11-1
> Severity: normal
>
>
> Sample entry from /var/log/syslog:
> Jun 20 19:13:11 tardis ovpn-nivexlan[2272]: write to TUN/TAP : Invalid
> argument (code=22)
>
> This mesage is logged once every minu
Package: openvpn
Version: 2.1~rc11-1
Severity: normal
Sample entry from /var/log/syslog:
Jun 20 19:13:11 tardis ovpn-nivexlan[2272]: write to TUN/TAP : Invalid
argument (code=22)
This mesage is logged once every minute since upgrading from etch to lenny.
The tunnel is up and functioning, but it
5 matches
Mail list logo
