Displaying 20 results from an estimated 5000 matches similar to: "Using a tinc vpn as a default route"
2001 Mar 08
2
Tinc behind firewall?
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
2002 May 28
1
tinc vpn over http-tunnel
Hi Guus,
I?m using tinc since 1.0pre4 (and still use pre4) - it?s a great thing.
Since these day?s a part of my VPN relies on a http-tunnel (because you
used a single TCP connection as carrier). With 1.0pre4 that was very
easy to setup using the TCPonly setting.
But with 1.0pre5 it seems you changed the carrier connection setup, so
that my old setup didn?t work anymore. In the meantime you
2002 Feb 25
1
problem with tinc pre5
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 =
2000 Jun 23
2
tinc 0.3.3 vs. 1.0pre2
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,
2000 Sep 10
2
tinc SECURITY INFORMATION - Unauthorized access to VPN
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
2000 Sep 10
2
tinc SECURITY INFORMATION - Unauthorized access to VPN
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
2002 Feb 13
1
keyword TCPOnly in release 1.0pre5
Hi,
I've successfully running tinc1.0pre4 between two locations on SuSE
Linux 7.1 in a special masquerading Firewall environment, so that I'm
using the TCPonly keyword in the host files to get a connection.
Otherwise I would get the message 'Received UDP packet on port 655 from
unknown source <ipaddress in hex:port>'.
After upgrading to 1.0pre5 I'm getting this message
2002 Feb 25
1
Bugs in 1.0pre5
Hello,
I set up a tinc vpn network with tinc 1.0pre5 on Mandrake 8.1
Please take note of the following troubles i noticed
1) In the config files, the name of the variables are case sensitive
2) the BindToInterface seems to be faulty. I removed the line, now
everything work, except the security aspect..
3) I HAD to add a Subnet=<full address of the local tinc device> in
the
hosts file, or
2001 Dec 10
4
tinc dies after some days/weekes of normal activity
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
2000 Nov 08
1
socket leakage patch
We have been fighting with intermittent connections here and have noticed that
tinc seems to use up its supply of file descriptors.
After a whole bunch of
Nov 8 03:51:23 tserver tinc.calgary[23909]: Could not set up a meta connection.
Nov 8 03:51:23 tserver tinc.calgary[23909]: Still failed to connect to other. Will retry
Nov 8 03:51:33 tserver tinc.calgary[23909]: 10.38.9.1:8193: Connection
2000 Jun 11
3
TINC 1.0pre2 problem
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
2002 Nov 21
2
TINC (vpn daemon) has stopped working after compiling kernel
Hi folks,
after recompiling of kernel (need quota support), tinc daemon has
stopped working. Messages from log file are:
...
Nov 21 14:45:02 m61 tinc.sunnet[326]: tincd 1.0pre7 starting
Nov 21 14:45:02 m61 tinc.sunnet[326]: /dev/net/tun is a Linux ethertap
device
Nov 21 14:45:02 m61 tinc.sunnet[326]: Process 327 (tinc-up) exited with
non-zero status 255
Nov 21 14:45:02 m61 tinc.sunnet[326]:
2000 Jun 12
0
TINC 1.0pre2: unable to access one private network (fwd)
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
2002 May 12
1
tinc version 1.0pre7 hangs
Hello,
I am running the staticly linked version, tinc version 1.0pre7 (built
Apr 9 2002 14:00:34, protocol 14) on four Debian potato systems. The
kernels are all 2.2.19. The vpn is set up as a star with one hub and
three spokes. The hub and one of the legs share the same ISP and are
on the same subnet. Both the other two legs are on different ISP's.
All the systems are running masquerading
2001 Jan 10
2
1.0pre3 difficulties
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
2001 Feb 12
4
Performance VPN over the internet
Hi 'tinc users'
I'm new whit tinc and this mail-list.
I like to build a vpn over the internet between two sites in Holland and
Germany. Are there some experience whit the performance (turn-a-round en
bandwidth) of a link. I want to use it for a 1,5Mb connection.
Greetings, Fred Krom.
-
Tinc: Discussion list about the tinc VPN daemon
Archive:
2002 Apr 09
1
[Announcement] Version 1.0pre7 released
With pleasure we announce the release of version 1.0pre6. Here is a
summary of the changes:
* Don't do blocking read()s when getting a signal.
* Remove RSA key checking code, since it sometimes thinks perfectly good RSA
keys are bad.
* Fix handling of subnets when prefixlength isn't divisible by 8.
This version features only small bugfixes. It is fully compatible with
1.0pre6.
--
2002 Apr 09
1
[Announcement] Version 1.0pre7 released
With pleasure we announce the release of version 1.0pre6. Here is a
summary of the changes:
* Don't do blocking read()s when getting a signal.
* Remove RSA key checking code, since it sometimes thinks perfectly good RSA
keys are bad.
* Fix handling of subnets when prefixlength isn't divisible by 8.
This version features only small bugfixes. It is fully compatible with
1.0pre6.
--
2000 Aug 27
4
[URGENT] tinc has a security hole of about 50 million km^2
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:
2001 May 25
4
tinc 1.0pre4 released
Hello everybody,
I have just released tinc 1.0pre4. Changes:
- New authentication protocol (better security, and faster too).
- TCPonly and IndirectData are back (but not fully tested).
- Documentation revised, it's really up to date with the released package now.
- tincd -K now stores public/private keys in PEM format, but keys of 1.0pre3
can still be used.
- Faster and more secure