Yann, sorry for the incredibly late response. I've been doing a crappy job as a vtun maintainer.
On Thu, Apr 24, 2008 at 18:11, Yann E. MORIN <[EMAIL PROTECTED]> wrote: > While investigating, I set compression to 'no', retried the connection, and > then the session was working. > > I tried the following: > - using no compression is OK > - using zlib compression at any level (0..9) is OK > - using lzo compression at any level (0..9) makes vtund segfault. Thanks for your research. I looked around and found the same symptoms: https://bugs.launchpad.net/ubuntu/+source/vtun/+bug/57974 http://sourceforge.net/mailarchive/forum.php?thread_name=48716DED.5040506%40room52.net&forum_name=vtun-devel > Which encouraged me to go and check the lzo package, and got me > down to: > http://bugs.debian.org/394695 > > which refers to upstream: > > http://sourceforge.net/mailarchive/message.php?msg_id=1127513474.14690.2.camel%40rock.sasdatalink.com > > Those two refer to liblzo1 (one), not liblzo2 which vtund is linked with. This looks suspiciously similar. I'm copying Peter (lzo2 maintainer) to see if he can shed some light on this, before submitting a bug report. All in all, this problem has a reasonable workaround, and doesn't break havoc on most systems, so I'll lower the severity to allow vtun to enter testing (and hopefully lenny!) Thanks! -- Martín Ferrari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
