What's wrong in these configurations?
EleGoS
elegos at fastwebnet.it
Mon Nov 27 12:44:43 CET 2006
Guus Sliepen ha scritto:
> On Sat, Nov 25, 2006 at 10:45:43PM +0100, EleGoS wrote:
>
>
>>> tincd -n vpn -d5 -D
>>>
>>> If the information it logs does not help you fix the problem, send me a
>>> copy of it, so I can have look.
>>>
>>>
>> It was a IPv6 problem :D
>> I've installed it on my windows for experimental purposes... I've used
>> the debugged mode and I've found errors about IPv6, so I've just added
>> this line to my conf: AddressFamily = ipv4 and deleted Address to both
>> hosts/elegos :D
>>
>
> Aha! Can you tell me which errors you saw exactly?
>
this is my log. Note: I've tried pinging, then shut down the service,
enabled it in debug mode and tried another time to ping
With FamilyAddress = ipv4 there are anyway IPv4 errors (like those in
the report), but I can establish a connection
NOTE:
me = 11.11.11.22
server = 11.11.11.11
Note also: 0 IPs (like 1.0.0.1, or 50.10.10.11) make some errors (cannot
connect... I'll send you another report with 'zeros' IPs)
C:\Documents and Settings\Giacomo>ping 11.11.11.22
Esecuzione di Ping 11.11.11.22 con 32 byte di dati:
Risposta da 11.11.11.22: byte=32 durata<1ms TTL=128
Risposta da 11.11.11.22: byte=32 durata<1ms TTL=128
Risposta da 11.11.11.22: byte=32 durata<1ms TTL=128
Risposta da 11.11.11.22: byte=32 durata<1ms TTL=128
Statistiche Ping per 11.11.11.22:
Pacchetti: Trasmessi = 4, Ricevuti = 4, Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 0ms, Massimo = 0ms, Medio = 0ms
C:\Documents and Settings\Giacomo>ping 11.11.11.11
Esecuzione di Ping 11.11.11.11 con 32 byte di dati:
Risposta da 11.11.11.11: byte=32 durata=114ms TTL=128
Risposta da 11.11.11.11: byte=32 durata=80ms TTL=128
Risposta da 11.11.11.11: byte=32 durata=105ms TTL=128
Risposta da 11.11.11.11: byte=32 durata=151ms TTL=128
Statistiche Ping per 11.11.11.11:
Pacchetti: Trasmessi = 4, Ricevuti = 4, Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 80ms, Massimo = 151ms, Medio = 112ms
C:\Documents and Settings\Giacomo>cd\
C:\>cd Programmi\tinc
C:\Programmi\tinc>tincd -n elenet -d5 -D
tincd 1.0.5 (Nov 14 2006 14:10:48) starting, debug level 5
Tap reader running
{52BDEF92-AD72-49A4-8A05-EDAF024A4DFA} (elenet) is a Windows tap device
Listening on 0.0.0.0 port 655
Ready
Trying to connect to shado (82.57.126.12 port 655)
Connected to shado (82.57.126.12 port 655)
Sending ID to shado (82.57.126.12 port 655): 0 elegos 17
Sending 12 bytes of metadata to shado (82.57.126.12 port 655)
Flushing 12 bytes to shado (82.57.126.12 port 655)
Got ID from shado (82.57.126.12 port 655): 0 shado 17
Sending METAKEY to shado (82.57.126.12 port 655): 1 94 64 0 0
7FB78B2C8FEB355C0C
E6A413099092C0B869A23746698D8174658A3B225B9BB4678D4D35908AD989A30229A495FF665628
3F575668EB23A6E988DFC3357641823752E3A1B3F178F0CF17367B0817E6992A0D8F23CDD12CB71B
90DC4554D037044E7EF96C7596EA19E9F6FF90BFBB40CABBA7A3519EA7381B14BC57470250C844
Sending 269 bytes of metadata to shado (82.57.126.12 port 655)
Got METAKEY from shado (82.57.126.12 port 655): 1 94 64 0 0
BBEEF835BA3E7D6D2465
6EC07D8BC476FF72E02E9C8754B7965388CEE641101D22C9B713DC8F70CABAE99023CC8EB1491152
A2594F2E773E8B4066AB2A348E91248BDBF558635ABEE5D4098C1D3F73A19E93139440C212703E20
7FF25E882662B74C686498687AE8DEBA92D27DA708E6CBD727E7DA65E5C9E5D6EDCACA280C64
Sending CHALLENGE to shado (82.57.126.12 port 655): 2
926CD1EE0C7BF57B04C96D7460
CE3C1AEFE67EC5B4D5E3E46AE4E793E95D0A544BA03055AEC99BEEE450F18E8EC67F5C0CD722C049
BE24A5FA05701EF321A1DCA86C2C71856AF7A05701EF7CE66EACCEDA4A924C05BD950FDEEE76158A
FA218443791484F3DDFFF4119917B9B4690385D58AE4A0C4F5039E95D7835ECB7690DA
Sending 259 bytes of metadata to shado (82.57.126.12 port 655)
Flushing 528 bytes to shado (82.57.126.12 port 655)
Got CHALLENGE from shado (82.57.126.12 port 655): 2
B68E32F8570810219FCD4E5BFBEA
3C47B5946F90B6CD87946336237D9FF47324429C07D47F9A2C6A18462AFCC440B43DAEAF32CFCDBB
472455EF8DCD0508208F56300A9947FE12638EC1A950E923FFF1EB47AD812A11BDC051FA1048C02E
82E6E0218C1A2E89303A6FB097923B7648EEB12112D1CCC6F7D2AFB2DC516F7F4F09
Sending CHAL_REPLY to shado (82.57.126.12 port 655): 3
9B2D5422F802566A6A7C5D1AE
22E041B9861D13F
Sending 43 bytes of metadata to shado (82.57.126.12 port 655)
Got CHAL_REPLY from shado (82.57.126.12 port 655): 3
C1F47BDD9EADDEB40A27A352D8E
331D95F1790F3
Sending ACK to shado (82.57.126.12 port 655): 4 655 0 0
Sending 10 bytes of metadata to shado (82.57.126.12 port 655)
Flushing 53 bytes to shado (82.57.126.12 port 655)
Read packet of 156 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv6 destination
address ff02:
0:0:0:0:1:ffbd:ef92
Writing packet of 204 bytes to Windows tap device
Read packet of 78 bytes from Windows tap device
Got too short packet from elegos (MYSELF)
Got ACK from shado (82.57.126.12 port 655): 4 655 0 0
Connection with shado (82.57.126.12 port 655) activated
Sending ADD_SUBNET to shado (82.57.126.12 port 655): 10 7a8a8e0 elegos
11.11.11.
22/32
Sending 33 bytes of metadata to shado (82.57.126.12 port 655)
Sending ADD_EDGE to everyone (BROADCAST): 12 4c3e5ad9 elegos shado
82.57.126.12
655 0 0
Sending 46 bytes of metadata to shado (82.57.126.12 port 655)
Got ADD_SUBNET from shado (82.57.126.12 port 655): 10 c397f13a shado
11.11.11.11
/32
Forwarding ADD_SUBNET from shado (82.57.126.12 port 655): 10 c397f13a
shado 11.1
1.11.11/32
Got ADD_EDGE from shado (82.57.126.12 port 655): 12 9bd3b75d shado
elegos 213.15
6.52.112 655 0 0
Forwarding ADD_EDGE from shado (82.57.126.12 port 655): 12 9bd3b75d
shado elegos
213.156.52.112 655 0 0
Node shado (82.57.126.12 port 655) became reachable
Flushing 79 bytes to shado (82.57.126.12 port 655)
Read packet of 42 bytes from Windows tap device
Read packet of 42 bytes from Windows tap device
Read packet of 42 bytes from Windows tap device
Read packet of 70 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv6 destination
address ff02:
0:0:0:0:0:0:2
Writing packet of 118 bytes to Windows tap device
Read packet of 54 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 224.0
.0.22
Writing packet of 82 bytes to Windows tap device
Read packet of 175 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 239.2
55.255.250
Writing packet of 203 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 54 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 224.0
.0.22
Writing packet of 82 bytes to Windows tap device
Read packet of 92 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 120 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 92 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 120 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 92 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 120 bytes to Windows tap device
Read packet of 175 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 239.2
55.255.250
Writing packet of 203 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 70 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv6 destination
address ff02:
0:0:0:0:0:0:2
Writing packet of 118 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 86 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv6 destination
address ff02:
0:0:0:0:1:ffbd:ef92
Writing packet of 134 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 175 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 239.2
55.255.250
Writing packet of 203 bytes to Windows tap device
Read packet of 220 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 248 bytes to Windows tap device
Read packet of 220 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 248 bytes to Windows tap device
Read packet of 220 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 248 bytes to Windows tap device
Read packet of 220 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 248 bytes to Windows tap device
Read packet of 471 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 499 bytes to Windows tap device
Read packet of 228 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 256 bytes to Windows tap device
Read packet of 228 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 256 bytes to Windows tap device
Read packet of 228 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 256 bytes to Windows tap device
Read packet of 240 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 268 bytes to Windows tap device
Read packet of 240 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 268 bytes to Windows tap device
Read packet of 240 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 268 bytes to Windows tap device
Read packet of 240 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 268 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 138 bytes to Windows tap device
Read packet of 456 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 484 bytes to Windows tap device
Read packet of 243 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 271 bytes to Windows tap device
Read packet of 258 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 286 bytes to Windows tap device
Read packet of 42 bytes from Windows tap device
Writing packet of 42 bytes to Windows tap device
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to shado (82.57.126.12 port 655)
No valid key known yet for shado (82.57.126.12 port 655), queueing packet
Sending REQ_KEY to shado (82.57.126.12 port 655): 15 elegos shado
Sending 16 bytes of metadata to shado (82.57.126.12 port 655)
Flushing 16 bytes to shado (82.57.126.12 port 655)
Got ANS_KEY from shado (82.57.126.12 port 655): 16 shado elegos
065C291D081E5B49
93D6489E59AFF58D19F23063E579846A 91 64 4 0
Flushing queue for shado (82.57.126.12 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to shado (82.57.126.12 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to shado (82.57.126.12 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to shado (82.57.126.12 port 655)
Read packet of 216 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 244 bytes to Windows tap device
Read packet of 92 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 120 bytes to Windows tap device
Read packet of 92 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 120 bytes to Windows tap device
Read packet of 92 bytes from Windows tap device
Cannot route packet from elegos (MYSELF): unknown IPv4 destination
address 11.11
.255.255
Writing packet of 120 bytes to Windows tap device
>
>> P.S.
>> If I do as server, and I'm under the NAT, if I connect to various PCs
>> (say: 4 or 5), those PCs are linked to one another daemon (on another
>> machine), and all the others connect to this last server, the in/out
>> traffic to me (NATted) is divided into those 5 PCs or only on one?
>>
>> i.e.
>> elegos -> ConnectTo = PC1..PC2..PC3
>> PC4 -> ConnectTo = PC1..PC2..PC3
>> All the others -> ConnectTo = PC4
>>
>> Bandwidth to elegos = PC4, or PC1/2/3 or PC4-PC*?
>>
>
> If you are behind a NAT and use TCPOnly = yes, then elegos will not
> communicate directly with PC4. It will go via one of PC1, PC2, PC3.
> Which one I cannot tell. But tinc does not do load balancing.
>
>
Thanks for the info ^^
(copy to the mailing list)
More information about the tinc
mailing list