similar to: tinc doesn't listen/connect

Hi, Our VPN runs okay for some time, and every now and then one of the links (we have three hosts connected redundantly) just falls out with no reason. In the syslog I get several (strange?) messages: Feb 14 09:56:02 ophar tinc.pirnet[2816]: 212.187.121.188 port 655: Connection timed out Feb 14 09:56:02 ophar tinc.pirnet[2816]: Could not set up a meta connection to 212.187.121.188 Feb 14

Hi, I created a VPN succesfully with two internet-connected hosts. But both hosts also have a LAN attached to them. One LAN has NW address 10.1.1.0/24 and the other 10.1.3.0/24. How should I set up firewall rules (on the tinc-connected hosts) and route definitions (on the other hosts of the LANs) to let for example 10.1.1.11 connect to 10.1.3.12? I have been playing around a bit with some things

On Thu, Mar 08, 2001 at 11:51:53AM +0100, Marcel Loesberg wrote: > I'm going to build a VPN and I want to use either Tinc or FreeS/WAN. > I've started building the VPN with FreeS/WAN and I find things are getting > rather complicated. > I looks like Tinc is much easier to configure but in the FAQ and in what I've > seen of the documentation so far there is no mention of

Hi, I'm trying to set-up a VPN using Tinc 1.0pre3. When I start tincd I get the following in /var/log/messages. On the machine that listens for incomming connections: > Mar 16 17:23:24 vpn tinc[1168]: tincd 1.0pre3 starting > Mar 16 17:23:24 vpn tinc[1168]: Ready: listening on port 655 On the machine making the connection: > Mar 16 17:16:51 mail tinc[802]: tincd 1.0pre3 starting

Hi Tinc Mailing Group, I've got Tinc-1.0pre3 set up on two Redhat Linux 6.2 / kernel 2.2.18 servers. It compiles okay, it reads the configuration files okay, it makes a valid connection between the two tincd daemons. However, it does not route data from one subnet to the other subnet. I will describe my setup below, and if anyone can suggest why it is not working, can they please reply to put

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

Was running 1.0pre2 just fine, but had to move machines, so I figgured I'd give 1.0pre3 a try. After getting everything to build and figguring out the new config files, here's where I'm stuck. Start the server process (remote machine). Start the client process (local machine). In remote machine, the following shows up in syslog: tinc[2659]: Got SEGV signal In local machine, the

Sending your passphrase encrypted is all fine, but tinc sends the key with which it was encrypted about a second later... Anyone being able to intercept these two requests is authorized on the VPN. We need asymmetric authentication _now_. -- Ivo Timmermans -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size:

Hello, I have 2 hosts HostA and HostB HostA - 10.38.9.2, kernel 2.4.16, tincd from Debian package HostB - 10.38.9.223, kernel 2.2.17-21mdk, tincd from tarball package. HostA: ------------------------------ /etc/tinc/test4/tinc.conf Name = HostA ConnectTo = HostB TapDevice = /dev/misc/net/tun PrivateKeyFile = /etc/tinc/test4/rsa_key.priv /etc/tinc/test4/hosts/HostA Subnet = 10.0.0.0/8 Port =

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

> - 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]:

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

JitterBug notification ivo moved PR#9 from incoming to wishlist Message summary for PR#9 From: vdongen@hetisw.nl Subject: map Date: Sun, 2 Jul 2000 18:23:20 0200 (CEST) 0 replies 0 followups Notes: This is a nice idea on itself, but not really doable in tinc itself. What would be nice is the ability to control tinc realtime with some sort of GUI tool. This tool can then be used for much

Hi, here's a small list of things that need to be done, and the version when it should be ready. smartcard support 1.1 LDAP support 1.1 public/private keys for authentication 1.1 don't store passphrases in files that are called after IP addresses 1.0 use names to identify

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

Dear tincerers- Please help, I need to get this working *today* (ack!). I've installed tinc 1.0p3 on two machines fully updated rh7, "stockton" and "lodi", where "lodi" is trying to "ConnectTo" "stockton". When I start the tinc daemens on each side, this is what i get in my logs: Stockton: Feb 23 19:07:57 srouter tinc.pacheart[2794]: tincd

Dear tincerers- Please help, I need to get this working *today* (ack!). I've installed tinc 1.0p3 on two machines fully updated rh7, "stockton" and "lodi", where "lodi" is trying to "ConnectTo" "stockton". When I start the tinc daemens on each side, this is what i get in my logs: Stockton: Feb 23 19:07:57 srouter tinc.pacheart[2794]: tincd

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,

Hello, I got trouble installing tinc daemon. Every time when a connection comes in, the daemon crashes: Mar 6 18:32:56 localhost tinc.vpn[20703]: tincd 1.0pre3 (Feb 21 2001 02:32:50) starting, debug level 5 Mar 6 18:32:56 localhost tinc.vpn[20703]: Ready: listening on port 655 Mar 6 18:33:00 localhost tinc.vpn[20703]: Connection from 192.168.0.4 port 1135 Mar 6 18:33:00 localhost