similar to: TINC 1.0pre2: unable to access one private network

Displaying 20 results from an estimated 1100 matches similar to: "TINC 1.0pre2: unable to access one private network"

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 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 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 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 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 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 May 24
3
FW: Almost ...
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
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
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
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 =
2001 Jun 01
2
Error: cannot route packet - please help
Hi, I?m fighting with a silly problem: my syslog tells me tinc cannot route a packet. I can use a telnet or the good ol ping, it is the same effect. When I?m pinging from the laptop (172.16.11.2) the network address (172.16.11.0) or any address numerically lower than the laptops address, the packet gets routed, otherwise not. And when I ping the network address, I get the reply twice, as to be
2000 Nov 22
1
Configuration Trouble
I have succeeded in getting two tinc1.0pre3 hosts to connect, but I can't ping one from the other. I can ping the local tap interfaces. tcpdump shows that icmp echo requests are received by the other host, but no replies are sent. The two hosts are North and South. It is the same pinging North to South and South to North. The hosts are configured as follows: South: Debian 2.2
2001 Feb 22
1
tincd running, but ping test doesn't work!
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
2001 Nov 08
1
ethertap dropping packets?
Hello, I'm having some routing issue with my tinc setup. I'm running a fairly basic VPN configuration between two networks: ------- Site A: ------- --- tinc-up --- #!/bin/sh /sbin/ifconfig tap0 hs ether fe:fd:00:00:00:00 /sbin/ifconfig tap0 10.11.1.2 netmask 255.0.0.0 /sbin/ifconfig tap0 -arp ---- tinc.conf --- Name = orca Hostnames = no InterfaceIP = 63.108.71.7 KeyExpire =
2001 Jun 22
1
book on tinc
Hi Ivo and Guus, We are writing a book on building VPNs for Linux and a part of it describes tinc. I wanted to make sure that your opinion, as tinc authors and developers, is reflected. First, let me ask a couple of technical questions. 1. If there are two hosts, foo and bar, that are to be connected via tinc, and each host should only have _one_ IP address (i.e. nmask is /32), would the
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
2002 Mar 07
3
I can't ping across gateway
Hi Who concern, I setup TINC VPN follow these. 192.168.1.x / 24 (Client groups) | 192.168.1.1 (eth1) (GW1) 202.44.34.206 (eth0) || Internet || 202.44.45.14 (eth0) (GW2) 192.168.2.1 (eth1)
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