similar to: No subject

Hi, Best wishes to all for this new year. Trying to connect my Laptop (HSDPA) to MainPC (DSL). Both running Windows XP. Laptop host file: Address = 41.208.50.176 Subnet = 10.0.0.2 -----BEGIN RSA PUBLIC KEY----- ... -----END RSA PUBLIC KEY----- MainPC host file: Address = 41.242.172.108 Subnet = 10.0.0.1 -----BEGIN RSA PUBLIC KEY----- ... -----END RSA PUBLIC KEY----- Tried alternate Subnet

Hello, I'm trying to test a tinc vpn between two Linux hosts on the same ethernet. If I start tinc on both sides as 'tinc -n test --bypass-security --debug=5' I can ping both machines from each other and tcpdump shows that the packets pass through the tun-device created by tinc. Connection from 192.168.192.17 port 32852 Sending ID to (null) (192.168.192.17 port 32852): 0 helix 17

Hi Marek I managed to setup everything in openwrt. However I am getting errors when trying to run tinc daemon. Below is my debug output. Please help.. How do I fix tunnel interface error? root at OpenWrt:/etc/tinc/vpn# tincd -n vpn -D -d3 tincd 1.0.21 (Mar 9 2014 18:26:59) starting, debug level 3 /dev/net/tun is a Linux ethertap device Executing script tinc-up ifconfig: SIOCGIFFLAGS: No

You know I think I've seen this once before. Got ID from db1 (10.130.39.180 port 655): 0 db1 17 Sending METAKEY to db1 It looks like it's communicating properly but there is a problem with your keys. Can you rename and regenerate your keys? On a project I'm working on when we transferred our keys to another client it put Carriage returns so there was a key mismatch. Try that and

Hi Guus, The first example was a manual connect, the second example was debug regards Robert >>> "Robert Horgan" <robert at nsasia.co.th> 13-Jun-18 10:21 AM >>> Hi, Are you sure? What happens if you manually telnet/socket 10.130.39.180 nsasia at web3:~$ telnet 10.130.39.180 655 Trying 10.130.39.180... Connected to 10.130.39.180. Escape

Hi, Are you sure? What happens if you manually telnet/socket 10.130.39.180 nsasia at web3:~$ telnet 10.130.39.180 655 Trying 10.130.39.180... Connected to 10.130.39.180. Escape character is '^]'. 0 db1 17 Connection closed by foreign host. Stopping the service and running debug I get: nsasia at web3:~$ sudo tincd -n gainplus -d5 -D tincd 1.0.33 starting, debug level 5

Hi, I've got a relatively simple tinc setup. I've got two "servers" that are on the public internet that act as routers for three "clients" that are behind NATs. Those servers are called aaaaa and bbbbb the clients are xxxxx, yyyyy and zzzzz Unfortunatly the servers have problems accepting a connection from the clients syslog on aaaaa: Sep 29 18:28:58 schuerrer

Yes, I am sure but added another broader rule: nsasia at db1:~$ sudo ufw allow from any port 655 proto udp same result for debug example. regards Robert >>> Rafael Wolf <rfwolf at gmail.com> 13-Jun-18 5:32 PM >>> Telnet will only do tcp not udp which tinc works on. Are you sure udp 655 is open? On Wed, Jun 13, 2018, 3:51 AM Robert Horgan <robert

Hello! I have encountered a bug using tincd with Microsoft Windows: Below you'll find my Setup and my Logs. In short, i do the following: 1. office running tincd 1.0.7 and waiting for connections (no ConnectTo, but this does not resolve the issue) 2. the supporter starts up tincd 1.0.7 on windows (native) 3. ping from windows ("support") to the office: Here the error occours:

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

Hi. I'm in desperate need of some good advice. I have a tinc network with 16 nodes. It's a star topology where all nodes are connecting to the one node (Node1) that have a static IP. Node 1 accepts incomming connections Node 2 through 16 connects to Node1 One of the nodes (Node5) stopped working a while ago (2 - 3 weeks or so), other than that everything was working fine. Today I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello! i would like to use tinc with public keys which are extracted from x509 certificates. the only public key format i was able to extract from certificates with openssl commands looked like this: - -----BEGIN PUBLIC KEY----- MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCwXDZs8EBb/JyZ9daB3Zk9WHxD

Hello, After upgrading my client system from Debian jessie to Debian stretch (which includes an update from tinc 1.0.24 to tinc 1.0.31), I am having trouble with my VPN: As long as I let tinc connect directly (no "Proxy" configuration option on the client), everything works fine: # tincd -n rath -D -d tincd 1.0.31 starting, debug level 1 /dev/net/tun is a Linux tun/tap device (tun

I have now got the tinc demons (on network OFFICES) on BranchB and BranchA talking to each other, see below for log from BranchB. For some trouble shouting issues relating to OsX see at the end of my e-mail. However, I have not yet achieved the network connectivity/routing that I would like. The aim is: BranchB is a laptop I would like to connect it (via tinc) to my office network, so that

Hi there I have the following setup Home - Main Tinc server with public IP running on PfSense work - tinc client running behind a CISCO ASA firewall with public IP running on Windows 10 offsite - tinc client running on tomato router behind a double NAT Home & offsite connect & i can see all PCs & devices & connect to them easily, on either side work to Home or offsite connects

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greeting- I have tinc on the following: 2 - x86 FreeBSD boxes 1 - ARM FreeBSD box 1 - x86 Macintosh All the x86 boxes can speak with each other, but none of the x86 boxes can speak with the ARM box. The ARM box says: [root at beaglebone /usr/local/etc/tinc/wdl]# tincd -D -n wdl tincd 1.0.24 (Mar 8 2015 14:55:57) starting, debug level 0

Hi, I've been running tinc for a couple of months and it's great, but I have a periodic problem which maybe you guys can figure out. I operate a 3-node tinc VPN, lets say A, B and C. A / \ B --- C The problem is that after a while, node C can't exchange data with node B. It works fine (ping and other traffic) for about 10 minutes, then fails. Here is some debug

Hello everybody, Here are some thoughts about the authentication scheme to be used in tinc. The current scheme (see CVS version, revision CABAL) does this: Client Server --------------------------------------- send_id(u) send_challenge(R) send_chal_reply(H) send_id(u) send_challenge(R)

Dear tinc-list, I am a happy tinc user for many years and am using several different VPNs. However today I was unable to add a new server to my "backbone" VPN. I hope it is okay that I write this issue to this list as hours of googling did not help. My setup consists of several servers, all tincing happily ever after. "kallisto" as one of them is happy talking to other

Hello, I'm using tinc for a few years now and that this is my first post to this list tells a lot about the quality of tinc, I think. It's just great, thanks a lot for your fine work! Recently I've discovered these messages in my syslog: Dec 28 16:34:06 vdr tinc.grue[9731]: Possible intruder ix (192.168.178.25 port 60882): wrong keylength Dec 28 16:34:06 vdr tinc.grue[9731]: Error