similar to: New config directive VpnMask

THis is the modified script that came with tinc 1.0pre2, and it now uses ifconfig in stead of ip-route. I changed the syntax to be correct (may already have been fixedin a newer version), it now checks whether or not there is a '/dev/tapX' or a '/dev/netlink/tapX' and it checks if there is a module or not. I also added the force_connect and the reload options. Force_connect send

G'day, I've just downloaded the tinc-1.0pre3 and compiled it - it seems to work fine. I tried your tinc start script in the redhat directory, first adding the MyOwnVPNIP = 10.1.3.1/16 VpnMask = 255.255.0.0 to my tinc.conf file as suggested. But now when TINC is invoked, tinc exits with the following error. [root@platypus tinc-1.0pre3]# /usr/local/sbin/tincd -n wurley.vpn Failed to

Hello, regarding the debian init.d script, a perl rewrite of the shell script by Lubomir. The debian-specific (?) start-stop-daemon is used. It uses its own pid-file handling instead of the one build into tinc. Bug or feature? "old" ifconfig and route commands are used instead of iproute commands. Bug or feature? regards, -- Mads Kiilerich Sys.Adm. Cand.Polyt

Hi, Although Im dutch too, Ill write this in english. I got a similar problem then the one on the helpforum. Ill paste my setup first server tincd.conf ---- ListenPort = 8089 MyOwnVPNIP = 192.168.100.1/24 #VpnMask = 255.255.255.0 TapDevice = /dev/tap0 Passphrases=/usr/local/etc/tinc/passphrases server tapdev ---- tap0 Link encap:Ethernet HWaddr FE:FD:C0:A8:6F:01 inet

Whens the point and click GUI coming out? All kidding aside, I seem to be confused about some of the network settings. Essentially all I want is a secure tunnel from machine A to B on two different physical networks, but I can't seem to get there. Just to get things figured out I've got two machines on the same physical network, mach A: 192.168.0.1, mach B: 192.168.0.3. bcast is

Installing the new tinc on a system (Mandrake 7.0) that uses bash2 as it shell turned up a problem with the redhat initialization script. Attached is a patch to make it functional for both bash and bash2. - Jamie -------------- next part -------------- diff -uNr tinc-1.0pre2.org/redhat/tinc tinc-1.0pre2/redhat/tinc --- tinc-1.0pre2.org/redhat/tinc Fri May 26 05:22:49 2000 +++

The two one-liner patches below are made against the current tinc CVS tree. The debian/rules patch replaces the prefix=blah on the "make install" line with DESTDIR=blah. The prefix is correctly set for /usr, but is overridden with the current make install. DESTDIR is the clean way to relocate the installation into the debian/tmp build dir. The second patch strips the newline off

Although we (the authors of tinc) have done our best to make tinc as secure as possible, an unfortunate combination of encryption and key exchange techniques has created a hole in at least all versions of tinc >= 0.3, including the current CVS version. Exploit: If somebody can intercept the meta protocol to a host that is running a tinc daemon, it is possible to decrypt the passphrase, which

Although we (the authors of tinc) have done our best to make tinc as secure as possible, an unfortunate combination of encryption and key exchange techniques has created a hole in at least all versions of tinc >= 0.3, including the current CVS version. Exploit: If somebody can intercept the meta protocol to a host that is running a tinc daemon, it is possible to decrypt the passphrase, which

On Sun, 11 Jun 2000, David Summers wrote: > Thanks for the great software package! The question I have is this: Thank you :) > My goal is to set up a triangle topology VPN between three sites and run > OSPF routing on all the sites so that if a link goes down between any two > sites the OSPF routing will reroute the packets that used to go between > the sites A <-> B to A

Hello, I'm trying to set up a vpn using tinc, so I installed tinc with the rpm version on my firewall as a listener. Setting up the tap device is no problem. The file /etc/tinc/tinc.conf looks like: TapDevice = /dev/tap0 MyVirtualIP = 192.168.2.1/24 Vpnmask = 255.255.255.0 When I start the script /etc/rc.d/init.d/tinc start it says something about missing /etc/tinc/nets.boot

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

> - Indirectdata finally REALLY REALLY works now! > - More precise debug messages Hmmm ... I can't prove that using the CVS code I checked out this morning. Everything works like yesterday: I can ping the peer but I canot go beyond: *** SERVER *** Jun 27 09:04:56 lemon tinc.9[10186]: tincd 1.0pre3 (Jun 27 2000 08:53:56) startin g, debug level 4 Jun 27 09:04:56 lemon tinc.9[10186]:

I am using tinc1.0pre1 pre2 is not yet available on the tinc site. The Var. VpnMask is unknown in version pre1. Netmask is 255.0.0.0 on tap0 on both gateways. Still the problem that you can ping the gateway on the other network but not the machines behind it. I've used the rpm download. -----Original Message----- From: Guus Sliepen [mailto:guus@warande3094.warande.uu.nl] Sent: Wednesday, May

Hi all, I just uploaded tinc 1.0pre1 to the server. I included and rpm, which has been made possible by the work of Lubom?r Bulej and Mads Kiilerich. Please test this version, so that any bugs left can be squished before 1.0 gets final. Also be aware that this version includes a new version of the protocol, and is thus NOT compatible with the protocol that 0.3 uses. Thanks for flying tinc.

Hi all, I just uploaded tinc 1.0pre1 to the server. I included and rpm, which has been made possible by the work of Lubom?r Bulej and Mads Kiilerich. Please test this version, so that any bugs left can be squished before 1.0 gets final. Also be aware that this version includes a new version of the protocol, and is thus NOT compatible with the protocol that 0.3 uses. Thanks for flying tinc.

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

Hello everyone, Today is exactly 10 years ago that tinc 1.0 was released. I would have hoped to celebrate this by releasing 1.0.22 and 1.1pre8 today, but this will instead happen in one week. Tinc 1.1 is close to becoming stable, and I hope to release 1.1.0 before the end of the year. The main features of tinc 1.1 are the improved security over tinc 1.0, and a much nicer interface that makes it

On Sun, 11 Jun 2000, gbarnett wrote: > Guus... I couldn't seem to get this to the mail list... could you post it > and/or answer it for me? Sure. > 2.3.4.5/tinc.conf > MyVirtualIP = 10.69.69.69/32 > TapDevice = /dev/tap0 > VPNMask = 255.255.255.0 Problem found (I think)! MyVirtualIP should be 10.69.69.69/29. Your VPNMask is correct. Idem for server B, where MyVirtualIP

Voor de duidelijkheid... ---------- Forwarded message ---------- Date: Sun, 11 Jun 2000 16:14:37 -0500 From: gbarnett <gbarnett@satx.rr.com> To: guus@sliepen.warande.net Subject: TINC 1.0pre2: unable to access one private network Guus... I couldn't seem to get this to the mail list... could you post it and/or answer it for me? Thx. I have been having problems configuring TINC