similar to: Problem with more than two Subnets!

Hi, I'm getting this weird error in the logs when starting tinc "Creating metasocket faile: Address family not supported by protocol" I've tried explicitly putting AddressFamily = ipv4 in the tinc.conf file but it doesn't seem to make a difference. The IP's i'm using for the vpn are 10.0.x.x Thanks for your assistance, R. Schwarzenberg -------------- next part

I'm currently running tinc-pre6 on 2 nodes in a larger network. My Laptop (Lassulus), lan ip: 192.168.2.100, tinc-ip: 10.243.0.2 My Server (alphalabs), lan ip: 192.168.2.103, tinc-ip: 10.243.1.10 internet vserver (slowpoke), no lan ip, tinc-ip: 10.243.232.121 Everything works fine until both nodes are in the same LAN. The first 2-3 minutes everything is fine. Pings between the machines go

hallo, today I have updated the first node of our tinc clout (33 tinc nodes currently) to 1.0.12 - all the others still use 1.0.10 or 1.0.11. It seems the whole tinc link to already activated connections pauses when there is a name resolution or authentication timeout. Feb 5 14:44:29 fwhh tinc.chaos[16262]: Already connected to royksopp Feb 5 14:45:00 fwhh tinc.chaos[16262]: Error while

First off, I would like to express my appreciation for the tinc software, it has been such a great vpn solution for what i need, its amazing. I am setting up another node on the vpn. "KVM" is my public facing node, "MacbookAir" is my workstation, "NewNode" is my node i have recently configured and the one with the issue presumably. NewNode and MacbookAir are on the

I have 2 nodes nodeA and nodeB I'm using tinc 1.1pre11 -- nodeA(fd80:2015:2105:abcd::1) : $ ip -6 route fd80:2015:2105:abcd::1 dev tun0 proto kernel metric 256 fd80:2015:2105:adcd::/64 dev tun0 metric 1024 fe80::/64 dev eth0 proto kernel metric 256 $ ping6 fd80:2015:2105:abcd::1 PING fd80:2015:2105:abcd::1(fd80:2015:2105:abcd::1) 56 data bytes 64 bytes from fd80:2015:2105:abcd::1:

Hi, I've been struggling for almost a week now, but I can't get the following setup to work. At home I have class A network: 10.0.0.0/16 with a masquerading gateway 10.0.0.1 running tinc. At work (http://www.eastsite.nl) we have a 192.168.0.0/24 network. The gateway is called 'ed' I've set up tinc on 'gateway' and everything is working fine from

Hi , I've added one node to my tinc mesh , with forwarding off , and the network got splitted into several pieces !!, the thing is that , the node with forwarding off is connected to all hosts , directly with connect to , and seems like that for some nodes the shortest path , that the tinc network can find is through the node with forwarding off , here are the results of my first ping to all

Dear R users, I am having problems loading the akima package. I use Windows XP, and R version 2.12.1. When I try to load the package I get this error message: Error: package ''akima'' is not installed for ''arch=i386'' Any help appreciated and thanks you for your time. Carlos Montenegro Silva Magíster en Estadística Departamento Evaluación de Recursos División

Hello! I use tincd to interconnect 3 LANs: A, B and C. So long, it works fine: everybody reaches everybody. But I want a different behavior: A and B should be allowed to talk, as should B and C. I tried to simply delete the host-files on the nodes that should not be allowed to talk to eachother: A has a hostfile from B B has a hostfile from A and C C has a hostfile from B But this is no

i need forwarding off , cause i need a central node , which is connected directly to all the network , directly , so it can usually upload content directly , without slowing down other nodes in the network , i also don't want it to act as a forwarder , since ,it only has 2mbps of bandwidth , and i don't want it for that purpose , is there any other way to fix this problem ? On 16 March

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

Hello, I have been reading through the documentation and trying to set up a very small VPN as a test for a larger rollout that I would like to complete in the future but cannot get this working. The configuration seems like it should be relatively simple, so I'm most likely missing something basic but I just cannot see what I'm doing wrong. At the moment I am trying to get this working

Hello Peter, Your question is similar to my recent question, and I have a similar Ping problem.But yours, with two Tinc networks, is more complex than mine. All I can say, and I hope it helps, is that in my case I have found my Ubuntu Tinc Server nodes do not like being specified as a address on the same network as the local LANsSo I have a specific network for the Tinc Server nodes, and in this

Tinc team: I'm creating a vpn for my work laptop and vps and got trapped, here are my config files: on laptop: *tinc.conf Name = envy13 Device = /dev/net/tun ConnectTo = main *hosts/main Address = <my vps ext ip address> Port = 655 Subnet = 10.0.0.1/32 *hosts/envy13 Port = 655 Subnet = 10.0.0.2/32 *tinc-up #!/bin/sh ip link set myvpn up ip addr add 10.0.0.2/32 dev myvpn ip route add

Hello folks, I have the following problem: tincd is complaining about a missing name or so but i cannot find any mistake in the configuration. It is similar to all my other tinc nodes. here are the details: # ls -l /etc/tinc/ffnw/ drwxr-xr-x 3 root root 4096 Aug 1 10:43 hosts -rw------- 1 root root 1680 Jul 31 21:54 rsa_key.priv -rw------- 1 root root

Hi ! I want to setup tinc 1.0 pre4 with kernel 2.4.5 I didn't find information about settings of tun/tap device I did in kernel - [*] Prompt for development and/or incomplete code/drivers Network device support <M> Universal TUN/TAP device driver support in /etc/modules.conf - alias char-major-10-200 tun mknod -m 600 /dev/tun c 10 200 chown 0.0 /dev/tun In mailing list archive I

I've been trying out IPv6 networking with tinc and noticed that it will not route smaller segments than /48 If I try to run ip -6 route add aaaa:bbbb:cccc:dddd::/64 dev tun0 I get network unreachable However if I run ip -6 route add aaaa:bbbb:cccc::/48 dev tun0 it works fine Is this is a limitation in tinc or the kernel network stack itself? -------------- next part -------------- An HTML

Hello all, I would like to connect two IPv4-only networks through global IPv6-only network with tinc. Could anyone tell me how to configure tinc.conf and the other config files? Thanks in advance, Ichiro Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://tinc.nl.linux.org/

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gus & Tinc-VPN List: It looks like I need to run 2 instances of tincd on each server. 1 instance of tincd will responsible for running a VPN over the LAN on eth1. This means Class C addresses from 10.0.1.10 -> 10.0.1.250 Another instance of tincd will be responsible for running a VPN over the WAN on eth0. This means Class C addresses from

Hello Julien, Am Mon, 14 Jan 2019 22:15:47 +0100 schrieb Julien dupont <marcelvierzon at gmail.com>: > ** Test 1 ** > On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.3' > When pinging 192.168.1.1 from client 1, with no success, I see no packet > passing. Sorry - the tcpdump command should end with "192.168.1.1" instead of