similar to: 1.0pre2

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 +++

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

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

I'm having a bit of a problem getting tinc up and running between a pair of RedHat (one 6.0, the other 6.1) boxes. It's installed and configured to the point where they can connect, but I'm not seeing any traffic passing between the two systems. System A looks like - tinc.conf: # Sample tinc configuration. # Insert your own ip numbers instead of the placeholders, # and be sure to use

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

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

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.

Hi Ivo, --On Freitag, 23. Juni 2000 01:15 +0200 Ivo Timmermans <zarq@icicle.yi.org> wrote: > I'm not sure I fully understand your patch. This is not so important since I'm trying to get 1.0pre2 running. Although I had no luck so far, I'll point out what's going wrong at the end of this mail. > For instance, you force a > key exchange when the connection is made,

Hi all, It seemed like a good idea to post updates here every now and then about the progress of the development of tinc. Right now, we're mainly hunting bugs. While doing this, we stumbled upon some shortcomings of the meta protocol, possibly dangerous. So Guus and I are now working on a new protocol, which will be incompatible with the standing 0.3 protocol (version 4). Whether or not

Mads Kiilerich wrote: > Right now at this moment we have reached a level where I have > no further patches! :-) great! :) Guus is now doing a last protocol change, after that is tested, I'm going to make 1.0pre1 official, including an rpm (deb will have to wait due to some difficulties). > I don't think a configuration program will be needed. VPN is not > for

Viraj Alankar wrote: > I've successfully setup tinc-1.0pre1 but I notice on my firewall > that it requires fragmented UDP packets to be let in in order to work > properly. Is there any way to avoid this? [ This is true. We don't inherit the DF (Don't Fragment) flag onto the UDP data, so path MTU discovery doesn't work. We have to fix this. ] Yes, you can avoid this

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

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

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

Announcing Moo-Tiff for FreeBSD 2.1. Sender: owner-freebsd-announce@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Moo-Tiff is a 100% compatible port of OSF/Motif 2.0 for FreeBSD 2.1, built from the official OSF sources and run through the OSF VTS (Validation Test Suite). If it works with OSF/Motif 2.0 on any platform, it can now work on FreeBSD 2.1 with Moo-Tiff ! Moo-Tiff is priced at

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

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