search for: metakey

...t to db1 (10.130.39.180 port 655) Connected to db1 (10.130.39.180 port 655) Sending ID to db1 (10.130.39.180 port 655): 0 web3 17 Sending 10 bytes of metadata to db1 (10.130.39.180 port 655) Flushing 10 bytes to db1 (10.130.39.180 port 655) Got ID from db1 (10.130.39.180 port 655): 0 db1 17 Sending METAKEY to db1 (10.130.39.180 port 655): 1 429 672 0 0 32B632E5E04DD553A58206EDE3F760472B5B1FCFB69319F6E5BD1D9C6B2B3E7D95903DBF0E7EFD0A7377916B5E8381C412E0478F4CAAF61454505327BE49C4462835E6BBA849D9FA4586D8906B730F85632DBFA2B287C77259A264BB51DC57C5258CE7888C81ABBC00BDEC910194A85F7D3FB771CB73644871B0417E2406...

...t to db1 (10.130.39.180 port 655) Connected to db1 (10.130.39.180 port 655) Sending ID to db1 (10.130.39.180 port 655): 0 web3 17 Sending 10 bytes of metadata to db1 (10.130.39.180 port 655) Flushing 10 bytes to db1 (10.130.39.180 port 655) Got ID from db1 (10.130.39.180 port 655): 0 db1 17 Sending METAKEY to db1 (10.130.39.180 port 655): 1 429 672 0 0 32B632E5E04DD553A58206EDE3F760472B5B1FCFB69319F6E5BD1D9C6B2B3E7D95903DBF0E7EFD0A7377916B5E8381C412E0478F4CAAF61454505327BE49C4462835E6BBA849D9FA4586D8906B730F85632DBFA2B287C77259A264BB51DC57C5258CE7888C81ABBC00BDEC910194A85F7D3FB771CB73644871B0417E2406...

...re xxxxx, yyyyy and zzzzz Unfortunatly the servers have problems accepting a connection from the clients syslog on aaaaa: Sep 29 18:28:58 schuerrer tinc.msch[4346]: Error during decryption of meta key for xxxxx (81.10.. port 56999) Sep 29 18:28:58 schuerrer tinc.msch[4346]: Error while processing METAKEY from xxxxx (81.10.. port 56999) Sep 29 18:29:23 schuerrer tinc.msch[4346]: Error during decryption of meta key for xxxxx (81.10.. port 57003) Sep 29 18:29:23 schuerrer tinc.msch[4346]: Error while processing METAKEY from xxxxx (81.10.. port 57003) Sep 29 18:29:50 schuerrer tinc.msch[4346]: Error du...

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 see what happens...

...t to db1 (10.130.39.180 port 655) Connected to db1 (10.130.39.180 port 655) Sending ID to db1 (10.130.39.180 port 655): 0 web3 17 Sending 10 bytes of metadata to db1 (10.130.39.180 port 655) Flushing 10 bytes to db1 (10.130.39.180 port 655) Got ID from db1 (10.130.39.180 port 655): 0 db1 17 Sending METAKEY to db1 (10.130.39.180 port 655): 1 429 672 0 0 32B632E5E04DD553A58206EDE3F760472B5B1FCFB69319F6E5BD1D9C6B2B3E7D95903DBF0E7EFD0A7377916B5E8381C412E0478F4CAAF61454505327BE49C4462835E6BBA849D9FA4586D8906B730F85632DBFA2B287C77259A264BB51DC57C5258CE7888C81ABBC00BDEC910194A85F7D3FB771CB73644871B0417E2406...

...CVS version, revision CABAL) does this: Client Server --------------------------------------- send_id(u) send_challenge(R) send_chal_reply(H) send_id(u) send_challenge(R) send_chal_reply(H) send_metakey(R) send_metakey(R) send_ack(u) send_ack(u) --------------------------------------- Other requests(E)... (u) Unencrypted, (R) RSA, using public key from the other side (H) SHA1, (E) Encrypted with symmetric cipher. Although tinc...

...ending ID to <unknown> (IP15 port 57815): 0 Node1 17.3 Sending 11 bytes of metadata to <unknown> (IP15 port 57815) Got ID from <unknown> (IP15 port 57815): 0 Node15 17.1 o2i_ECPublicKey failed: error:10067066:elliptic curve routines:ec_GFp_simple_oct2point:invalid encoding Sending METAKEY to Node15 (IP15 port 57815): 1 94 64 0 0 548E70..... Sending 525 bytes of metadata to Node15 (IP15 port 57815) Got METAKEY from Node15 (IP15 port 57815): 1 94 64 0 0 8254CB121..... Sending CHALLENGE to Node15 (IP15 port 57815): 2 C25C898C33..... Sending 515 bytes of metadata to Node15 (IP15 port 57...

...ity 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 while processing METAKEY from ix (192.168.178.25 port 60882) Could you give me a hint about the reason? I've compared the public keys and they match. Also, there's no problem to connect from host vdr to host ix via tinc... Thanks again! -- Markus Grunwald https://www.the-grue.de Fragen zur Mail? https://www.the...

...2.172.108 port 655) .. Closing connection with MainPC (41.242.172.108 port 655) MainPC extract (DSL): .. Connection from 41.208.50.180 port 8173 .. Sending ID to <unknown> (41.208.50.180 port 8173): 0 MainPC 17 .. Got ID from <unknown> (41.208.50.180 port 8173): 0 Laptop 17 .. Sending METAKEY to Laptop (41.208.50.180 port 8173): ... .. Got METAKEY from Laptop (41.208.50.180 port 8173): ... .. Sending CHALLENGE to Laptop (41.208.50.180 port 8173): ... .. Sending 259 bytes of metadata to Laptop (41.208.50.180 port 8173) .. Connection closed by Laptop (41.208.50.180 port 8173) Kind regard...

...rting, debug level 3 /dev/net/tun is a Linux tun/tap device (tun mode) Executing script tinc-up Listening on 0.0.0.0 port 655 Listening on :: port 655 Ready Connection from 2.2.2.2 port 35031 Sending ID to <unknown> (2.2.2.2 port 35031) Got ID from <unknown> (2.2.2.2 port 35031) Sending METAKEY to client1 (2.2.2.2 port 35031) Got METAKEY from client1 (2.2.2.2 port 35031) Sending CHALLENGE to client1 (2.2.2.2 port 35031) Got CHALLENGE from client1 (2.2.2.2 port 35031) Sending CHAL_REPLY to client1 (2.2.2.2 port 35031) Got CHAL_REPLY from client1 (2.2.2.2 port 35031) Sending ACK to client1...

...t when i try to use the first format: Trying to connect to mtx1 (172.16.1.1 port 655) Connected to mtx1 (172.16.1.1 port 655) Sending ID to mtx1 (172.16.1.1 port 655): 0 mtx58 17 Sending 11 bytes of metadata to mtx1 (172.16.1.1 port 6 Got ID from mtx1 (172.16.1.1 port 655): 0 mtx1 17 Sending METAKEY to mtx1 (172.16.1.1 port 655): 1 94 64 0 0 57C9352011BC165C8DFCCB0E9FCBC795C0B1E21014694F4E37B9BFF8BBAC210CE6D4F9293A 02985F4AF49F7181F8E793E39CAE8406D8FDC09610A301FC8337C426DC56BDF0B16D803A1F3337 A3C02538301DB424310AE84C034389768DDC164FDBD3E8A2A9DBFC6E30872AE4512EAD01D30352 08EDC185F684BE0979ED0FA...

...ebug=5' the connection fails. The log shows messages like: Connection from 192.168.192.20 port 33105 Sending ID to (null) (192.168.192.20 port 33105): 0 crux 17 Sending 10 bytes of metadata to (null) (192.168.192.20 port 33105) Got ID from (null) (192.168.192.20 port 33105): 0 helix 17 Sending METAKEY to helix (192.168.192.20 port 33105): ........ Sending 269 bytes of metadata to helix (192.168.192.20 port 33105) Got METAKEY from helix (192.168.192.20 port 33105): ........ Sending CHALLENGE to helix (192.168.192.20 port 33105): ........ Sending 259 bytes of metadata to helix (192.168.192.20 po...

...mode) Executing script tinc-up Listening on 0.0.0.0 port 655 Ready Trying to connect to ebox (45.79.69.51 port 655) Using proxy /etc/tinc/rath/triv_proxy.sh Connected to ebox (45.79.69.51 port 655) proxy.sh: connecting to ebox via netcat... Got ID from ebox (45.79.69.51 port 655): 0 ebox 17 Sending METAKEY to ebox (45.79.69.51 port 655): 1 421 672 0 0 85F239FFC4CB544F04B4AC16150F90BF8EB648FD2C831A0435D45EC05ECC2594E0C4BEEC03135D0E4499377D8D71C05CF9392D90E8C5710F6E67DD99A2ED3F09FE0B6738D6F7EAF2B1FD62BCD1B330A50F4B6C58DB13168C883A7EB97518AAA7702E00D16132EC81FC8D6F4A839AD131B341F3ADB1AA0B64B7AC2C3F7D6C9...

...Guus. Well the debug helped a little bit. So did re-reading the manual again. I think I got further ahead, but unfortunately I still cannot quite get to complete the connection between the two nodes. It looks like the two nodes are communicating - they seem to be able to exchange RSA keys & MetaKeys, but for some reason, they start trying to exchange data on random ports (1361, 1362, 1436, etc.) before the connection has been completely established and I'm guessing that they might be getting blocked by Windows Firewall (I did add tinc.exe to the program exception list, along with port 655...

...BranchA (123.123.123.7 port 655) 1101125071 tinc.OFFICES[922]: Connected to BranchA (123.123.123.7 port 655) 1101125071 tinc.OFFICES[922]: Sending ID to BranchA (123.123.123.7 port 655) 1101125071 tinc.OFFICES[922]: Got ID from BranchA (123.123.123.7 port 655) 1101125071 tinc.OFFICES[922]: Sending METAKEY to BranchA (123.123.123.7 port 655) 1101125071 tinc.OFFICES[922]: Got METAKEY from BranchA (123.123.123.7 port 655) 1101125071 tinc.OFFICES[922]: Sending CHALLENGE to BranchA (123.123.123.7 port 655) 1101125071 tinc.OFFICES[922]: Got CHALLENGE from BranchA (123.123.123.7 port 655) 1101125071 tin...

Hello! I have recently installed tinc on a linux 2.4 machine which has 192.168.0.0/24 private network connected to eth0 and registered ip on eth1. I also installed tinc on Windows 2000 machine on a remote location. for this moment I can establish connection, on Linux machine tincd says: Sep 26 21:10:50 hostname tinc.gscvpn[483]: Node home (y.y.y.y port 655) became reachable But i

...hile reading from Linux ethertap device /dev/net/tun: Operation now in progress Error while reading from Linux ethertap device /dev/net/tun: Operation now in progress Connected to vpn_gw2 (x.x.x.x port 655) Sending ID to vpn_gw2 (x.x.x.x port 655) Got ID from vpn_gw2 (x.x.x.x port 655) Sending METAKEY to vpn_gw2 (x.x.x.x port 655) Error while reading from Linux ethertap device /dev/net/tun: Operation now in progress Error while reading from Linux ethertap device /dev/net/tun: Operation now in progress Error while reading from Linux ethertap device /dev/net/tun: Operation now in progress Got...

...5) Connected to office (111.111.111.111 port 655) Sending ID to office (111.111.111.111 port 655): 0 support 17 Sending 12 bytes of metadata to office (111.111.111.111 port 655) Flushing 12 bytes to office (111.111.111.111 port 655) Got ID from office (111.111.111.111 port 655): 0 office 17 Sending METAKEY to office (111.111.111.111 port 655): 1 94 64 0 0 BBB2E88F0815689A58FC 52D39151C0F009D8FD6108665084A3EEBCC1E91D76564E69A0E1D567A8B26FF104A47B172045 B752D B8E3C238F17C3CA21FA8CAF9192486A2E2B2788E2D50F74ECDAEC51A4 Sending 269 bytes of metadata to office (111.111.111.111 port 655) Got METAKEY from off...

-----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

...9.0.1.2 port 52907) Dec 13 14:49:08 c tinc.nfp_c_vpn[18195]: Error while processing ADD_EDGE from nfp_uh (6.7.8.9 port 37372) Dec 13 14:49:25 c tinc.nfp_c_vpn[18195]: Error while processing ADD_SUBNET from nfp_c_rt (7.8.9.0 port 36773) Dec 13 14:49:26 c tinc.nfp_c_vpn[18195]: Error while processing METAKEY from nfp_hl_event (9.0.1.2 port 52954) Dec 13 14:50:57 c tinc.nfp_c_vpn[18195]: Error while processing ADD_EDGE from nfp_uh (6.7.8.9 port 37373) Dec 13 14:50:57 c tinc.nfp_c_vpn[18195]: Error while processing ADD_EDGE from nfp_c_luxur (3.4.5.6 port 59736) Dec 13 14:50:57 c tinc.nfp_c_vpn[18195]: Er...