Windows to Linux - ping-bug?

[Florian Lagg]

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: the supporter get's ping timeouts
 
possible Workaround:
If i start an ping from Linux (office) to the Windows-host (support) the
ping in the other direction (ad 3.) starts working. If there is more then
one node the Windows-host connects to there must be an initial ping from
every node!
 
My example-setup:
----------------------------------------------------------------------------
-----------
office:
NETWORK: 192.168.0.0/24 
GATEWAY: 192.168.0.10
The gateway is a Linksys-Router running OpenWRT. Port 655 TCP+UDP are open
in iptables
On this gateway tincd is running
 
tinc.conf:
name = office
 
/etc/tinc/office/tinc-up:
ifconfig $INTERFACE 192.168.0.11 netmask 255.255.0.0
iptables -A forwarding_rule -i office -j ACCEPT
iptables -A forwarding_rule -o office -j ACCEPT
----------------------------------------------------------------------------
-----------
support:
NETWORK: 192.168.123.0/24
GATEWAY: 192.168.123.1 (655 TCP+UDP nat'ed to 192.168.123.20
tinc runs on a windows xp host with the IP 192.168.123.20
 
tinc.conf:
name = support
ConnectTo = office
Interface = office
 
The Interface office is configured to 
IP 192.168.123.250 SUBNET 255.255.0.0
----------------------------------------------------------------------------
-----------
on both:
/etc/tinc/office/hosts/office:
Address=111.111.111.111
Subnet=192.168.0.0/24
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----
/etc/tinc/office/hosts/support:
Address = 222.222.222.222
Subnet = 192.168.123.0/24
-----BEGIN RSA PUBLIC KEY-----
...
-----END RSA PUBLIC KEY-----
----------------------------------------------------------------------------
-----------
Log on Windows (support). First ping fails, then (after pinged one time from
office to support) it starts working:
tincd -n office -d5 -D
tincd 1.0.7 (Jan  5 2007 15:26:38) starting, debug level 5
Tap reader running
{091E295E-E35A-4C52-A9D1-1CCD3C7176DE} (office) is a Windows tap device
Listening on 0.0.0.0 port 655
Ready
Trying to connect to office (111.111.111.111 port 655)
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 office (111.111.111.111 port 655): 1 94 64 0 0
7A60D0F5B1B176CD3D66E4
6F989E29F52806FAE6D2BD5F6F9D174C1FB8B958E596B830314E3F99808CA3C7F9935B6D4A0A
BE38D
61EA5743482D7DF65CC1F893BF561481AB464A564CFDBBF1ACE74A8
Sending CHALLENGE to office (111.111.111.111 port 655): 2
0989A5613BC948F7F55FB266043A
8AE2A6017AACE9CF66DADAAE392E20E8B94AD0387746F2121CD72BF71E41C89EBC88ACA515F8
06F50
CFEE8F6A82904DA01E76EA1C4C6482E8BB6D0BBA2FC603C2C
Sending 259 bytes of metadata to office (111.111.111.111 port 655)
Flushing 528 bytes to office (111.111.111.111 port 655)
Got CHALLENGE from office (111.111.111.111 port 655): 2
5222B98744B0EA9AA6E59F20CC11D4
F44BBDB4113D1731F68D54DCDD0836F4EF574F5BEFD30363B96AF5FEAA8E1EB15D78D98B11E7
AFDEF
E6C54F1E4CEE06BEF10D1F5DD10A4837D3C2552780A4E4A
Sending CHAL_REPLY to office (111.111.111.111 port 655): 3
DC515085A8DA4F11DC5B41D2E91
Sending 43 bytes of metadata to office (111.111.111.111 port 655)
Got CHAL_REPLY from office (111.111.111.111 port 655): 3
4EA38074EC93044EC8C3C54D4EFE3
Sending ACK to office (111.111.111.111 port 655): 4 655 1000 0
Sending 13 bytes of metadata to office (111.111.111.111 port 655)
Flushing 56 bytes to office (111.111.111.111 port 655)
Got ACK from office (111.111.111.111 port 655): 4 655 289 0
Connection with office (111.111.111.111 port 655) activated
Sending ADD_SUBNET to office (111.111.111.111 port 655): 10 faa6cf72 support
192.168.12
Sending 36 bytes of metadata to office (111.111.111.111 port 655)
Sending ADD_EDGE to everyone (BROADCAST): 12 9d85b6ad support office
111.111.111.111 65
Sending 47 bytes of metadata to office (111.111.111.111 port 655)
Got ADD_SUBNET from office (111.111.111.111 port 655): 10 3f530950 office
192.168.0.0/24
Forwarding ADD_SUBNET from office (111.111.111.111 port 655): 10 3f530950
office 192.168
Got ADD_EDGE from office (111.111.111.111 port 655): 12 34d88414 office
support 193.154.2
Forwarding ADD_EDGE from office (111.111.111.111 port 655): 12 34d88414
office support 19
Node office (111.111.111.111 port 655) became reachable
Flushing 83 bytes to office (111.111.111.111 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 54 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
224.0.
Writing packet of 82 bytes to Windows tap device
Read packet of 175 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
239.25
Writing packet of 203 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 54 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
224.0.
Writing packet of 82 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 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 42 bytes from Windows tap device
Cannot route packet: ARP request for unknown address 192.168.2.200
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
No valid key known yet for office (111.111.111.111 port 655), queueing
packet
Sending REQ_KEY to office (111.111.111.111 port 655): 15 support office
Sending 15 bytes of metadata to office (111.111.111.111 port 655)
Flushing 15 bytes to office (111.111.111.111 port 655)
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Got ANS_KEY from office (111.111.111.111 port 655): 16 office support
4994BC3CC7459028949
Flushing queue for office (111.111.111.111 port 655)
Receiving packet failed: No such file or directory
Read packet of 175 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
239.25
Writing packet of 203 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 175 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
239.25
Writing packet of 203 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 42 bytes from Windows tap device
Cannot route packet: ARP request for unknown address 192.168.2.200
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Receiving packet failed: No such file or directory
Receiving packet failed: No such file or directory
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 110 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 138 bytes to Windows tap device
Read packet of 221 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 249 bytes to Windows tap device
Read packet of 243 bytes from Windows tap device
Cannot route packet from support (MYSELF): unknown IPv4 destination address
192.16
Writing packet of 271 bytes to Windows tap device
Read packet of 243 bytes from Windows tap device
Packet looping back to support (MYSELF)!
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 42 bytes from Windows tap device
Cannot route packet: ARP request for unknown address 192.168.2.200
Receiving packet failed: No such file or directory
Receiving packet failed: No such file or directory
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 42 bytes from Windows tap device
Cannot route packet: ARP request for unknown address 192.168.2.200
Receiving packet failed: No such file or directory
Receiving packet failed: No such file or directory
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 42 bytes from Windows tap device
Cannot route packet: ARP request for unknown address 192.168.2.200
Receiving packet failed: No such file or directory
Receiving packet failed: No such file or directory
Got REQ_KEY from office (111.111.111.111 port 655): 15 office support
Sending ANS_KEY to office (111.111.111.111 port 655): 16 support office
238C94A480F68EB6A
Sending 74 bytes of metadata to office (111.111.111.111 port 655)
Flushing 74 bytes to office (111.111.111.111 port 655)
Received packet of 98 bytes from office (111.111.111.111 port 655)
Writing packet of 98 bytes to Windows tap device
Received packet of 98 bytes from office (111.111.111.111 port 655)
Writing packet of 98 bytes to Windows tap device
Received packet of 98 bytes from office (111.111.111.111 port 655)
Writing packet of 98 bytes to Windows tap device
Received packet of 98 bytes from office (111.111.111.111 port 655)
Writing packet of 98 bytes to Windows tap device
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 42 bytes from Windows tap device
Cannot route packet: ARP request for unknown address 192.168.2.200
Received packet of 74 bytes from office (111.111.111.111 port 655)
Writing packet of 74 bytes to Windows tap device
Received packet of 74 bytes from office (111.111.111.111 port 655)
Writing packet of 74 bytes to Windows tap device
Received packet of 98 bytes from office (111.111.111.111 port 655)
Writing packet of 98 bytes to Windows tap device
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Received packet of 74 bytes from office (111.111.111.111 port 655)
Writing packet of 74 bytes to Windows tap device
Received packet of 74 bytes from office (111.111.111.111 port 655)
Writing packet of 74 bytes to Windows tap device
Received packet of 98 bytes from office (111.111.111.111 port 655)
Writing packet of 98 bytes to Windows tap device
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Received packet of 74 bytes from office (111.111.111.111 port 655)
Writing packet of 74 bytes to Windows tap device
Received packet of 74 bytes from office (111.111.111.111 port 655)
Writing packet of 74 bytes to Windows tap device
Received packet of 98 bytes from office (111.111.111.111 port 655)
Writing packet of 98 bytes to Windows tap device
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Read packet of 74 bytes from Windows tap device
Sending packet of 74 bytes to office (111.111.111.111 port 655)
Received packet of 74 bytes from office (111.111.111.111 port 655)
Writing packet of 74 bytes to Windows tap device
Received packet of 74 bytes from office (111.111.111.111 port 655)
Writing packet of 74 bytes to Windows tap device
Received packet of 98 bytes from office (111.111.111.111 port 655)
Writing packet of 98 bytes to Windows tap device
^C
----------------------------------------------------------------------------
-----------
Corresponding log on unix (office):
tincd -n office -d5 -D
tincd 1.0.6 (Feb 13 2007 12:18:45) starting, debug level 5
/dev/net/tun is a Linux tun/tap device (tun mode)
Executing script tinc-up
Creating metasocket failed: Address family not supported by protocol
Listening on 0.0.0.0 port 655
Ready
Connection from 222.222.222.222 port 59379
Sending ID to (null) (222.222.222.222 port 59379): 0 office 17
Sending 10 bytes of metadata to (null) (222.222.222.222 port 59379)
Got ID from (null) (222.222.222.222 port 59379): 0 support 17
Sending METAKEY to support (222.222.222.222 port 59379): 1 94 64 0 0
7A60D0F5B1B176CD3D66E420DE6A666D3AE22265952ED1E0B0C22D775E88C5EE8EC670F6F989
E29F52806FAE6D2BD5F6F9D174C1FB8B958E596B830314E3F99808CA3C7F9935B6D4A0ABE38D
128AA11FDD0BC8B4FB46A03C6088C9606FE427FE0E326615161EA5743482D7DF65CC1F893BF5
61481AB464A564CFDBBF1ACE74A8
Sending 269 bytes of metadata to support (222.222.222.222 port 59379)
Flushing 279 bytes to support (222.222.222.222 port 59379)
Got METAKEY from support (222.222.222.222 port 59379): 1 94 64 0 0
BBB2E88F0815689A58FC74D9B0796346B91EF1E9EE02DE87D2975B752CAFDCC286A8D52D3915
1C0F009D8FD6108665084A3EEBCC1E91D76564E69A0E1D567A8B26FF104A47B172045B752D0D
027C653301090487FD07705152A6F7B58247E77BD220784B8E3C238F17C3CA21FA8CAF919248
6A2E2B2788E2D50F74ECDAEC51A4
Sending CHALLENGE to support (222.222.222.222 port 59379): 2
5222B98744B0EA9AA6E59F20CC11D4541B383EF0F2EEC5C3560518A8A17AE664C9468A1B2156
E6EF44BBDB4113D1731F68D54DCDD0836F4EF574F5BEFD30363B96AF5FEAA8E1EB15D78D98B1
1E7AFDEF5431A7BE6875B3EFCF67F8791E9148CCFCC6F01D65E515DB3E6C54F1E4CEE06BEF10
D1F5DD10A4837D3C2552780A4E4A
Sending 259 bytes of metadata to support (222.222.222.222 port 59379)
Got CHALLENGE from support (222.222.222.222 port 59379): 2
0989A5613BC948F7F55FB266043A658A4F432A81BB6498094099F3F841EE0E827A1AC8FB81DE
F8AE2A6017AACE9CF66DADAAE392E20E8B94AD0387746F2121CD72BF71E41C89EBC88ACA515F
806F502BDACEE2C04548F72755AE2DBCCB44707AFAE39B3F0844428CFEE8F6A82904DA01E76E
A1C4C6482E8BB6D0BBA2FC603C2C
Sending CHAL_REPLY to support (222.222.222.222 port 59379): 3
4EA38074EC93044EC8C3C54D4EFE360096098B93
Sending 43 bytes of metadata to support (222.222.222.222 port 59379)
Flushing 302 bytes to support (222.222.222.222 port 59379)
Got CHAL_REPLY from support (222.222.222.222 port 59379): 3
DC515085A8DA4F11DC5B41D2E911CEFB70D6D3F5
Sending ACK to support (222.222.222.222 port 59379): 4 655 289 0
Sending 12 bytes of metadata to support (222.222.222.222 port 59379)
Got ACK from support (222.222.222.222 port 59379): 4 655 1000 0
Connection with support (222.222.222.222 port 59379) activated
Sending ADD_SUBNET to support (222.222.222.222 port 59379): 10 3f530950
office 192.168.0.0/24
Sending 32 bytes of metadata to support (222.222.222.222 port 59379)
Sending ADD_EDGE to everyone (BROADCAST): 12 34d88414 office support
222.222.222.222 655 0 644
Sending 48 bytes of metadata to support (222.222.222.222 port 59379)
Flushing 92 bytes to support (222.222.222.222 port 59379)
Got ADD_SUBNET from support (222.222.222.222 port 59379): 10 faa6cf72
support 192.168.123.0/24
Forwarding ADD_SUBNET from support (222.222.222.222 port 59379): 10 faa6cf72
support 192.168.123.0/24
Got ADD_EDGE from support (222.222.222.222 port 59379): 12 9d85b6ad support
office 111.111.111.111 655 0 644
Forwarding ADD_EDGE from support (222.222.222.222 port 59379): 12 9d85b6ad
support office 111.111.111.111 655 0 644
Node support (222.222.222.222 port 655) became reachable
Got REQ_KEY from support (222.222.222.222 port 59379): 15 support office
Sending ANS_KEY to support (222.222.222.222 port 59379): 16 office support
4994BC3CC745902894916AFB310EF1513FFECB9B5804E787 91 64 4 0
Sending 74 bytes of metadata to support (222.222.222.222 port 59379)
Flushing 74 bytes to support (222.222.222.222 port 59379)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Sending packet of 98 bytes to support (222.222.222.222 port 655)
No valid key known yet for support (222.222.222.222 port 655), queueing
packet
Sending REQ_KEY to support (222.222.222.222 port 59379): 15 office support
Sending 15 bytes of metadata to support (222.222.222.222 port 59379)
Flushing 15 bytes to support (222.222.222.222 port 59379)
Got ANS_KEY from support (222.222.222.222 port 59379): 16 support office
238C94A480F68EB6A6E86D51730F1F5B54A9CC588C83A756 91 64 4 0
Flushing queue for support (222.222.222.222 port 655)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Sending packet of 98 bytes to support (222.222.222.222 port 655)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Sending packet of 98 bytes to support (222.222.222.222 port 655)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Sending packet of 98 bytes to support (222.222.222.222 port 655)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Sending packet of 98 bytes to support (222.222.222.222 port 655)
Received packet of 74 bytes from support (222.222.222.222 port 655)
Writing packet of 74 bytes to Linux tun/tap device (tun mode)
Received packet of 74 bytes from support (222.222.222.222 port 655)
Writing packet of 74 bytes to Linux tun/tap device (tun mode)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Sending packet of 74 bytes to support (222.222.222.222 port 655)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Sending packet of 74 bytes to support (222.222.222.222 port 655)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Sending packet of 98 bytes to support (222.222.222.222 port 655)
Received packet of 74 bytes from support (222.222.222.222 port 655)
Writing packet of 74 bytes to Linux tun/tap device (tun mode)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Sending packet of 74 bytes to support (222.222.222.222 port 655)
Received packet of 74 bytes from support (222.222.222.222 port 655)
Writing packet of 74 bytes to Linux tun/tap device (tun mode)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Sending packet of 74 bytes to support (222.222.222.222 port 655)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Sending packet of 98 bytes to support (222.222.222.222 port 655)
Received packet of 74 bytes from support (222.222.222.222 port 655)
Writing packet of 74 bytes to Linux tun/tap device (tun mode)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Sending packet of 74 bytes to support (222.222.222.222 port 655)
Received packet of 74 bytes from support (222.222.222.222 port 655)
Writing packet of 74 bytes to Linux tun/tap device (tun mode)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Sending packet of 74 bytes to support (222.222.222.222 port 655)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Sending packet of 98 bytes to support (222.222.222.222 port 655)
Received packet of 74 bytes from support (222.222.222.222 port 655)
Writing packet of 74 bytes to Linux tun/tap device (tun mode)
Received packet of 74 bytes from support (222.222.222.222 port 655)
Writing packet of 74 bytes to Linux tun/tap device (tun mode)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Sending packet of 74 bytes to support (222.222.222.222 port 655)
Read packet of 74 bytes from Linux tun/tap device (tun mode)
Sending packet of 74 bytes to support (222.222.222.222 port 655)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Sending packet of 98 bytes to support (222.222.222.222 port 655)
Metadata socket read error for support (222.222.222.222 port 59379):
Connection reset by peer
Closing connection with support (222.222.222.222 port 59379)
Sending DEL_EDGE to everyone (BROADCAST): 13 77ef75c0 office support
Node support (222.222.222.222 port 655) became unreachable
Sending DEL_EDGE to everyone (BROADCAST): 13 6bb47b8d support office
Purging unreachable nodes
Sending DEL_SUBNET to everyone (BROADCAST): 11 2181e8fb support
192.168.123.0/24
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Cannot route packet from office (MYSELF): unknown IPv4 destination address
192.168.123.1
Writing packet of 126 bytes to Linux tun/tap device (tun mode)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Cannot route packet from office (MYSELF): unknown IPv4 destination address
192.168.123.1
Writing packet of 126 bytes to Linux tun/tap device (tun mode)
Read packet of 98 bytes from Linux tun/tap device (tun mode)
Cannot route packet from office (MYSELF): unknown IPv4 destination address
192.168.123.1
Writing packet of 126 bytes to Linux tun/tap device (tun mode)
Got TERM signal
Closing connection with office (MYSELF)
Executing script tinc-down
Statistics for Linux tun/tap device (tun mode) /dev/net/tun:
 total bytes in:        1768
 total bytes out:        970
Terminating
 
Could someone check this and fix it?
I can help with tests if you like.
 
Thanks in advance
Florian Lagg (www.lagg.at <http://www.lagg.at/> )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://brouwer.uvt.nl/pipermail/tinc-devel/attachments/20070429/79412f58/attachment.html