similar to: In case you were wondering...

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

Dear Tinc Experts, I have been struggling for some time now, with Tinc pre3, and firewall rulesets and routing. I did once manage to get Tinc to work okay in a test-bed environment. I then tried to set it up for a 'real-life' setup and cannot get it to work properly. My real-life setup looks like this: Network A: 192.168.1.0 / 255.255.255.0 192.168.1.7 tap1 device gateway >

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

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

Mike, you can use ifconfig, it should work fine. It can be something like this: #!/bin/sh ifconfig $INTERFACE 172.20.0.1 netmask 255.255.0.0 It no need to add up at the end of ifconfig string. And "ip route" can be skipped too. On Fri, Feb 26, 2016 at 5:23 PM, Mike Purvis <mpurvis at clearpathrobotics.com> wrote: > Hi Maxim, > > > Not much to it: > >

Lets view your tinc.conf On February 26, 2016 6:41:30 PM GMT+03:00, Mike Purvis <mpurvis at clearpathrobotics.com> wrote: >Hi Maxim, > >I'm having the same result, though I got some more output with debug >level >5; it's definitely failing to create the specified tincdev0 network >device. >Is there something I need to change on OS X to enable that? See: >

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

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 =

Hi, I have some problems getting tinc up and running an a Mac OS X and Linux machine. I was able to compile tinc on Linux and Mac and I configured it as fare as the daemons speak to each other (PING/PONG works fine, a -USR2 shows both edges). The problem is, that a real ping does not work. It gets sent over to the other machine but I never get a reply. Does anyone know why this happens? Note

Beste tinc-developer, Ik moet van mijn baas een aantal VPN's aanleggen en ben nu thuis bezig om te testen. Ik heb 2 computers in een thuisnetwerkje (totaal 6 computers) geinstalleerd met SuSe 7.3, daar de klanten dit ook hebben. De computers zijn verbonden met een switch. Dit is de inhoud van mijn bestanden: Op computer 1 genaamd suse met ip 192.168.0.99 netmask 255.255.255.0

Hi folks, Sorry to trouble you all - I'm having some trouble getting tincd up and running - I suspect I'm having problems with subnets. Any help would relaly be appreciated! At the moment I'm trying to get two linux boxes, both of which are running as NAT routers for their respective networks to talk. My goal is to allow staff to connect to the corporate network from their laptops

I read tinc documentation part: " For Branch A BranchA would be configured like this: In /etc/tinc/company/tinc-up: # Real interface of internal network: # ifconfig eth0 10.1.54.1 netmask 255.255.0.0 ifconfig $INTERFACE 10.1.54.1 netmask 255.0.0.0 ... Note that the IP addresses of eth0 and tap0 are the same. This is quite possible, if you make sure that the netmasks of the

Hi, Guus Thanks a lot for your suggestion, actually I did something else as below. But one question here is if I don’t add "/sbin/ifconfig myvpn 10.0.0.1 netmask 255.255.255.0”, it seems the crontab wouldn’t trigger tinc-up, and then the ip addr of myvpn wouldn’t be configured, then it will prompt the error of "Can't write to Linux tun/tap device (tun mode) /dev/net/tun:

Hi! I've successfully installed tinc on Solaris 8 x86. Everything seem to work ok except for one thing, I get 5kb/s transfer rates over a 100mbit TP connection. Is this a known problem or have I made some mistakes? My setup is really simple: anna(Win XP - Tinc 1.0.2 using the Win32-TAP driver) <=> LAN <=> sara (Solaris 8 x86 - Tinc 1.0.2 using the TUN/TAP 1.1 driver, OpenSSL

Hello to all i have set up two tincd as mentioned on this site: http://mia.ece.uic.edu/~papers/volans/tincd.html but all i get on the client side is: [ root@mondhexe ]: # tail -f /var/log/tinc.log Trying to connect to naturstrom (80.132.178.186 port 655) Timeout from naturstrom (80.132.178.186 port 655) during authentication Closing connection with naturstrom (80.132.178.186 port 655) Trying to

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

If you are running Lollipop / Android 5.x on your Nexus 5, then you are probably seeing the same issue I was with it. lollipop seems to change networking quite a bit in that it's using iptables / and `ip rule list` extensively for per-user settings. I think http://www.linux.org/threads/debugging-nat-prerouting-issues-iptables.7136/ is relevant if you see running in to the same issue, it's

using 1.0pre5 A: tinc.conf ------------ Name = A PrivateKeyFile = /usr/local/etc/tinc/vpn/rsa_key.priv Device = /dev/tap0 ConnectTo = B A: tinc-up --------- #!/bin/sh modprobe ethertap ifconfig tap0 hw ether fe:fd:00:00:00:00 ifconfig tap0 192.168.0.3 netmask 255.255.0.0 ifconfig tap0 -arp B: tinc.conf ------------ Name = B PrivateKeyFile = /usr/local/etc/tinc/vpn/rsa_key.priv Device =

SELinux is considered as the biggest problem. On Thu, Mar 26, 2015, 22:37 Andrea Squeri <andrea.squeri at gmail.com> wrote: > Yes. The problem is lollipop. I tried to install tinc on my brother's > device which mount a cyano 10.1( android 4.2.2) and it works. > I don't understand which is the problem with lollipop. Is there a > firewall that block the packets? >

On Fri, Apr 24, 2015 at 10:26:18PM +0200, Sven-Haegar Koch wrote: > > #!/bin/sh > > ifconfig $INTERFACE 10.96.x.y > > Won't a netmask of 255.255.255.255 be better than not specifying any? > Otherwise it falls back to old classful adressing and would assume > 10.0.0.0/8 - which is clearly always wrong. [...] Or are tun devices > different in this regard? Hm, it