search for: galabov

...r/local/src/tinc-1.0pre4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/tinc-1.0pre4' make: *** [all-recursive-am] Error 2 ====================== Can you help me why I get this ? On this mashine I got compiled tinc-pre3 version without problems. Kosta Galabov Studio VISIA - System admin www.visia.com - Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://tinc.nl.linux.org/

...a lot with the lock options and tried to remove the DENY_FCB - setting "share modes = no" but nothing helped - I have this problem. So please advice - how can I prevent this file locking when connection between master and client disappears ? For me this look like a bug. Regards Kostadin Galabov Netclime Inc.

.../etc --with-openssl-include=/usr/local --with-openssl-lib=/usr/local/ and no success. Please tell me which files are you looking for when you looking for openssl-lib, to be sure a pointing to the correct ones. I think you look for libssl.a and libcrypto.a which are in /usr/local/lib Regards Kosta Galabov -------------- next part -------------- An HTML attachment was scrubbed... URL: http://brouwer.uvt.nl/pipermail/tinc/attachments/20030206/a144a9e5/attachment.html

Hello, I successfully use tinc for one year in a configuration with several subnets (about 5-7 subnets) and one main server. Sometimes tinc dies with the error message: Error while waiting for input: Bad file descriptor If it happens, this happens immediately, when one subnet has disconnected. tinc (on the main server) tries then to disconnect all currently connected subnets and while

Hi, I'm using tinc 1.pre3 with kernel 2.4.3 and it was working fine. I upgraded my kernel to 2.4.10 and tinc stopped working with the following error in syslog: ======= tinc.vpn1[236]: Error while reading from ethertap device: File descriptor in bad state ========= Does anyone had this problem and can you help me with it ? - Tinc: Discussion list about the tinc VPN daemon Archive:

...arting Tincd gives me the following error: " tinc.vpn1[2611]: Error while reading from ethertap device: File descriptor in bad state" Once I had this error and you advised me to recompile tinc, so I did it now, but now it hasn't helped. So any help from you would be appreciated Kosta Galabov Sysadmin Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://tinc.nl.linux.org/

Hi, this is not a problem, but more explaination. I have four networks connected via tinc - A, B, C and D. B, C and D connect to A. What is odd to me is that B and C communicate directly (without going to A); while all communication to D network goes via A. When I turned more verbose logging on tinc, I show a line like this: "adding route to VPN_NAME vi MASTER_VPN_NAME". Why does it

Hi all, I have the following question. If the master tinc dies (the one that clients have ConnectTo option), does clients conntinue to communicate with each other ? I noteced the following. If there is some traffic between the clients and the master tinc dies - there is no problem. But if there is no traffic between clients and the master dies, then when I try to access some different than master

I installed Tinc and started on two mashines. both connect and say everything is OK. But then when I try to ping through the VPN I get the following errors in syslog: on server: rtr-us tinc.vpn_net[911]: Metadata socket read error for BG_VPN (x.x.x.x - inet ip of client): No such process and on client ns tinc.vpn_net[301]: Incoming data socket error: Connection refused what does it mean as on my

It didn't help :( When I did ping to 192.168.1.1 from client machine I got the following in syslog: May 8 08:55:54 ns tinc.vpn_net[726]: Sending packet of 100 bytes to US_VPN (x.x.x.x - inetIP) May 8 08:55:55 ns tinc.vpn_net[726]: Incoming data socket error: Connection refused tcpdump -i tap0 gives this: 08:49:13.919331 ns.iris.bg > 192.168.1.1: icmp: echo request 08:49:14.919323

...broken BIOS detected, last ditch attempt with drive = 9F isolinux: Loading main image from LBA = 00031A21 isolinux: Sectors to load = 0004 isolinux: Disk error 01, AX = 4221, Drive 9F ===================== So any info would be appreciated, even one thats says that its BIOS fault. Regards Kostadin Galabov System Administrator Netclime Inc.