Displaying 20 results from an estimated 900 matches similar to: "FW: Almost ..."
2000 May 24
3
Almost ...
Hi all,
I have used tinc to get a vpn up and running I am almost there but have some
problems at the end.
My config:
Building A
Network 10.0.0.0
netmask 255.255.255.0
gateway 10.0.0.30
tap0 device on gateway machine 10.0.0.31
Building B
Network 10.2.0.0
netmask 255.255.255.0
gateway 10.2.0.154
tap0 device on gateway machine 10.2.0.155
from network A I can ping 10.2.0.154 but not the other
2000 May 25
0
FW: FW: Almost ... (fwd)
Whee :)
Met vriendelijke groet,
Guus Sliepen.
---------- Forwarded message ----------
Date: Thu, 25 May 2000 10:41:44 -0700
From: Matthijs Hoosemans <matthijs.hoosemans@recipeweb.com>
To: guus@warande3094.warande.uu.nl
Subject: FW: FW: Almost ...
Bedankt, alles werkt!!!
Groeten,
Matthijs
-
Tinc: Discussion list about the tinc VPN daemon
Archive:
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
2000 Jul 08
1
Problems starting up tincd with startupscript 1.0pre2-1.i386.rpm
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
2000 Aug 03
1
tinc config(?) problems
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
2000 Aug 20
1
debian/{rules,init.d} DESTDIR and $VPNMASK fixes
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
2000 Aug 21
0
Rewritten script /etc/init.d/tinc
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
2000 May 16
1
New config directive VpnMask
Hello Mads,
In case you never saw any mail from me, I'm tinc's co-author. It would be
helpful if you'd subscribe to the tinc developpers mailing list. It's not
high volume, but it eases communication.
There's a problem with tinc's boot scripts (at least the debian one, but
that's fixed now). The netmask of the tap devices should be larger than
the one specified with
2000 Jun 16
1
RedHat initialization script and bash2
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
+++
2000 Jun 12
0
TINC 1.0pre2: unable to access one private network
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
2000 Oct 17
2
setup problems
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
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
2000 Jul 27
1
Network confusion
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
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
2001 Jan 16
1
TINC and REDHAT
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
2000 May 31
0
1.0pre2
Hi all,
1.0pre2 is there.
[ I just noticed the included ChangeLog is empty -- oh well. ]
* This version has been internationalized; and a Dutch translation has
been included.
* Two configuration variables have been added:
* VpnMask - the IP network mask for the entire VPN, not just our
subnet (as given by MyVirtualIP). The Redhat and Debian packages
use this variable in their
2000 May 31
0
1.0pre2
Hi all,
1.0pre2 is there.
[ I just noticed the included ChangeLog is empty -- oh well. ]
* This version has been internationalized; and a Dutch translation has
been included.
* Two configuration variables have been added:
* VpnMask - the IP network mask for the entire VPN, not just our
subnet (as given by MyVirtualIP). The Redhat and Debian packages
use this variable in their
2001 May 08
4
tap1 problem
Hi Tinc Mailing-Group,
Having set up the kernel correctly, and got tinc running successfully,
I am now trying to get two VPNs running at once. Hence I need to
have two ethertap devices ( /dev/tap0 and /dev/tap1 ).
The first tap0 device was created thus:
mknod -m 600 /dev/tap0 c 36 16
chown 0.0 /dev/tap0
The second tap1 device was created too:
mknod -m 600 /dev/tap1 c 36 17
chown 0.0 /dev/tap1
2000 Mar 25
3
RFH -> Request for Help.
Hello all,
I've been playing with tinc to setup a wan between two offices of the
company that I work for. I'm partially there but having a slight problem.
tinc comes up between the 2 machines (both 2.2.14 debian woody
machines), and I can ping from the vpn machine at office a, and get a
response from office b. However, if I ping any other machine across the
wan I can't get a