Testing 1.0pre2 from CVS

Axel Müller axel.mueller at i2c-systems.com
Sun Jun 25 00:08:03 CEST 2000


>> I run the very new tinc on both sides this time.
>> Both sides had "IndirectData = yes" in their tinc.conf.
>> Procedure was to start tinc on server side, then start tinc on client
>> side. So far everthing looked okay. Then (12 seconds later - 22:39:37) I
>> tried to  ping the server side (=VPN peer) at 192.168.9.1 but without
>> success.
>
> Sorry, all clients must use indirectdata = yes, but NOT the server. And
> ALL computers must run the latest tincd. Could you try that?
You made it very clear this time ;-)
This time I put "indirectdata = yes" only on the client (I'm the only one).
Again both sides were running the latest tinc.

Here is the client side log file:

Jun 24 23:56:41 tomcat tinc[32011]: tincd 1.0pre2 (Jun 24 2000 22:18:47) 
starting, debug level 3.
Jun 24 23:56:41 tomcat tinc[32011]: Generating 128 bits keys.
Jun 24 23:56:41 tomcat tinc[32011]: Ready: listening on port 655.
Jun 24 23:56:41 tomcat tinc[32011]: Connected to 212.79.9.74:655
Jun 24 23:56:41 tomcat tinc[32011]: got 
BASIC_INFO(655,192.168.9.1,255.255.255.0)
Jun 24 23:56:41 tomcat tinc[32011]: Peer uses protocol version 7
Jun 24 23:56:41 tomcat tinc[32011]: Opening UDP socket to 212.79.9.74
Jun 24 23:56:41 tomcat tinc[32011]: Send BASIC_INFO to 212.79.9.74
Jun 24 23:56:54 tomcat tinc[32011]: trying to look up 192.168.9.1 in 
connection list failed.
Jun 24 23:57:25 tomcat last message repeated 31 times


Here is the server side log file:

Jun 24 23:55:42 lemon tinc.9[10908]: tincd 1.0pre2 (Jun 24 2000 22:18:47) 
starting, debug level 3.
Jun 24 23:55:42 lemon tinc.9[10908]: Generating 128 bits keys.
Jun 24 23:55:42 lemon tinc.9[10908]: Ready: listening on port 655.
Jun 24 23:56:23 lemon tinc.9[10908]: Connection from 213.54.41.186:1061
Jun 24 23:56:23 lemon tinc.9[10908]: Send BASIC_INFO to 213.54.41.186
Jun 24 23:56:23 lemon tinc.9[10908]: got 
BASIC_INFO(655,192.168.9.100,255.255.255.0)
Jun 24 23:56:23 lemon tinc.9[10908]: Peer uses protocol version 7
Jun 24 23:56:23 lemon tinc.9[10908]: Opening UDP socket to 213.54.41.186
Jun 24 23:56:23 lemon tinc.9[10908]: Send PASSPHRASE 
0e8dbfe690ae1c95a5a75c088d8a49c545845c4c9c30232ddd6f9fe84d2d6a47ffdd1cbf124
ca1939fc9350267ba
9d87a3def04d6ce6e626d5f2155d7aa38f6b1b07d38c0c3cca86fa559d389ab65eb779d7aa6
db8af7a98b161f3b5702cb5bba6136272d6a7dd920dcb7524d927ce9dcd93a32feff1a
6e011c51775593ba62cee0bf1d4d18bf3674d15d4885158b759bf6ab989c31793feb956625a
2765b6afe74869fba8258a195ed81d530ca61ea66becb0ef7e5ce42c946d9a43996ca4
a401ab83196e2088334913d5798a555482978ad692a0c7bf086d645d2bff53bcb6722de18e5
09c02d3fb89b33c8a21c31f93ee75b51503243f9dee9f7218191578 to 192.168.9.1
00
Jun 24 23:56:24 lemon tinc.9[10908]: 192.168.9.100 wants to quit
Jun 24 23:56:24 lemon tinc.9[10908]: Closing connection with 213.54.41.186.
Jun 24 23:56:39 lemon tinc.9[10908]: Connection from 213.54.41.186:1062
Jun 24 23:56:39 lemon tinc.9[10908]: Send BASIC_INFO to 213.54.41.186
Jun 24 23:56:39 lemon tinc.9[10908]: got 
BASIC_INFO(655,192.168.9.100,255.255.255.0)
Jun 24 23:56:39 lemon tinc.9[10908]: Peer uses protocol version 7
Jun 24 23:56:39 lemon tinc.9[10908]: Opening UDP socket to 213.54.41.186
Jun 24 23:56:39 lemon tinc.9[10908]: Send PASSPHRASE 
0e8dbfe690ae1c95a5a75c088d8a49c545845c4c9c30232ddd6f9fe84d2d6a47ffdd1cbf124
ca1939fc9350267ba
9d87a3def04d6ce6e626d5f2155d7aa38f6b1b07d38c0c3cca86fa559d389ab65eb779d7aa6
db8af7a98b161f3b5702cb5bba6136272d6a7dd920dcb7524d927ce9dcd93a32feff1a
6e011c51775593ba62cee0bf1d4d18bf3674d15d4885158b759bf6ab989c31793feb956625a
2765b6afe74869fba8258a195ed81d530ca61ea66becb0ef7e5ce42c946d9a43996ca4
a401ab83196e2088334913d5798a555482978ad692a0c7bf086d645d2bff53bcb6722de18e5
09c02d3fb89b33c8a21c31f93ee75b51503243f9dee9f7218191578 to 192.168.9.1

I tried to ping the remote peer from each side without success (always the 
lookup fails).

---
TINC development list, tinc-devel at nl.linux.org
Archive: http://mail.nl.linux.org/tinc-devel/



More information about the Tinc-devel mailing list