Hello,
trying to start tinc I get the following at the client:
Apr 17 16:34:50 otto tincd[10238]: tincd 0.3.3 starting, debug level 1.
Apr 17 16:34:50 otto tincd[10238]: Generating 128 bits keys.
Apr 17 16:34:50 otto tincd[10238]: Ready: listening on port 655.
Apr 17 16:34:50 otto tincd[10238]: Connected to xxx
Apr 17 16:34:50 otto tincd[10238]: Memory exhausted; exiting.
- on a machine with 80 Mb ram...
I can also see the following:
[root@otto tinc-0.3.3]# genauth 100
Generating 128 bits numberSegmentation fault (core dumped)
[root@otto tinc-0.3.3]# genauth 100
Generating 128 bits numberSegmentation fault (core dumped)
[root@otto tinc-0.3.3]# genauth 100
Generating 128 bits numberSegmentation fault (core dumped)
[root@otto tinc-0.3.3]# genauth 100
Generating 128 bits numberSegmentation fault (core dumped)
[root@otto tinc-0.3.3]# genauth 100
Generating 128 bits number128 8e50e221ab126fe66f2423996019022b
[root@otto tinc-0.3.3]# genauth 100
Generating 128 bits number128 39757ba4124c00cc48bcdc77ceda4027
[root@otto tinc-0.3.3]# genauth 100
Generating 128 bits numberSegmentation fault (core dumped)
[root@otto tinc-0.3.3]# genauth 100
Generating 128 bits numberSegmentation fault (core dumped)
[root@otto tinc-0.3.3]# gdb genauth core
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License,
and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty"
for details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `genauth 100'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libgmp.so.2...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0 0x4008d129 in chunk_free (ar_ptr=0x40121d60, p=0x8049cd8) at malloc.c:3111
3111 malloc.c: No such file or directory.
(gdb) where
#0 0x4008d129 in chunk_free (ar_ptr=0x40121d60, p=0x8049cd8) at malloc.c:3111
#1 0x4008cfba in __libc_free (mem=0x8049ce0) at malloc.c:3023
#2 0x400854ab in _IO_new_fclose (fp=0x8049ce0) at iofclose.c:61
#3 0x80489d0 in main ()
#4 0x4004b9cb in __libc_start_main (main=0x8048800 <main>, argc=2,
argv=0xbffffaa4,
init=0x80485f8 <_init>, fini=0x8048acc <_fini>,
rtld_fini=0x4000ae60 <_dl_fini>,
stack_end=0xbffffa9c) at ../sysdeps/generic/libc-start.c:92
(gdb)
I'm running an updated Red Hat 6.2 with the standard kernel and
gmp 2.0.2.
At the server side:
Apr 17 16:34:13 lightning tincd[8253]: Connection from xxx
Apr 17 16:34:13 lightning tincd[8253]: Receive failed: Success
Apr 17 16:34:13 lightning tincd[8253]: Closing connection with xxx
The success message seems a bit confusing...
Have you seen something like that before?
tinc does not seem to be widely used, even though it has the
advantage of not requiring any special kernel modules. Is it
"production quality"?
--
Mads Kiilerich Sys.Adm. Stud.Polyt
Mads@Kiilerich.com Tel. +45 38 16 26 00 Mob. +45 26 20 07 73
M?ntmestervej 12B 1th, DK-2400 NV, Denmark
"To be, or not to be; that is the question." Shakespeare
"The question is minus one using 2's complement!" Me
-
Tinc: Discussion list about the tinc VPN daemon
Archive: http://mail.nl.linux.org/lists/
Tinc site: http://ftp.nl.linux.org/pub/linux/tinc/
