Linux to Windows Tinc Issue

[Andrew Barlow]

Hello,

I am having troubles with the following configuration in that it produces
the following errors:

*Masterserver:*

On the server (yea, I know) side is a Linux machine called "*masterserver*".
It should have a VPN IP of 192.168.2.1 and it sits behind a pretty generic
ADSL Router (with port 655 forwarded) which can be found via a dynamic host
address. A small snippet of errors this machine produces are:

*No response to MTU probes from client1 (87.82.30.179 port 655)
Cannot route packet from masterserver (MYSELF): unknown IPv4 destination
address 192.168.2.2
Writing packet of 126 bytes to Linux tun/tap device (tun mode)
Got PACKET from client1 (87.82.30.179 port 655): 17 120
Received packet of 120 bytes from client1 (87.82.30.179 port 655)
Broadcasting packet of 120 bytes from client1 (87.82.30.179 port 655)
Writing packet of 120 bytes to Linux tun/tap device (tun mode)
Got PING from client1 (87.82.30.179 port 655): 8
Sending PONG to client1 (87.82.30.179 port 655): 9
Sending 2 bytes of metadata to client1 (87.82.30.179 port 655)
Flushing 2 bytes to client1 (87.82.30.179 port 655)
Sending PING to client1 (87.82.30.179 port 655): 8
Sending 2 bytes of metadata to client1 (87.82.30.179 port 655)
Flushing 2 bytes to client1 (87.82.30.179 port 655)
Got PONG from client1 (87.82.30.179 port 655): 9
Got PING from client1 (87.82.30.179 port 655): 8*


Although, it does seem to send the keys happily and find each other in some
way, I cannot ping 192.168.2.2 from "masterserver (192.168.2.1)" at all. The
configuration files for this machine are:

*/vpn/tinc.conf*

Name = masterserver
ConnectTo = client1

*/vpn/hosts/masterserver*

Address = ******tech.homeip.net
Subnet = 255.255.255.0
-- key data --

*/vpn/hosts/client1*

Address = ******monster.homeip.net
Subnet = 255.255.255.0
-- key data --

*/vpn/tinc-up*

#!/bin/sh
ifconfig $INTERFACE 192.168.2.1 netmask 255.255.255.0

*ifconfig results
*
vpn       Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:192.168.2.1  P-t-P:192.168.2.1  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:2205 (2.2 KB)  TX bytes:336 (336.0 B)


*Client1*

The client (yes, I know) machine for this vpn is called "*client1*" and
should have a VPN address of 192.168.2.2. This is running on *Windows XP*. I
have given it a static IP in accordance with the how-to on the website.
However, when I run tinc from the command line I get the following straight
away.

*{98FDEAFD-09AA-4437-88E2-D502F88E9D9A} (VPN) is a Windows tap deviceTap
reader running
Listening on 0.0.0.0 port 655
Ready
Cannot route packet: ARP request for unknown address 192.168.2.2
Cannot route packet: ARP request for unknown address 192.168.2.2
Cannot route packet: ARP request for unknown address 192.168.2.2
Cannot route packet from client1 <MYSELF>: unknown IPv4 destination address
192.168.255.255*

And that just continues forever. However, sometimes it does exchange keys
but then just seems to repeat this kind of thing:

*Cannot route packet from client1 (MYSELF): unknown IPv4 destination address
192.168.255.255
Writing packet of 247 bytes to Windows tap device
Cannot route packet from client1 (MYSELF): unknown IPv4 destination address
192.168.255.255
Writing packet of 302 bytes to Windows tap device
Cannot route packet from client1 (MYSELF): unknown IPv4 destination address
192.168.255.255
Writing packet of 277 bytes to Windows tap device
Broadcasting packet of 120 bytes from client1 (MYSELF)
Sending packet of 120 bytes to masterserver (78.32.128.149 port 655)
Packet for masterserver (78.32.128.149 port 655) larger than minimum MTU,
forwarding via TCP
Sending PACKET to masterserver (78.32.128.149 port 37922): 17 120
Sending 7 bytes of metadata to masterserver (78.32.128.149 port 37922)
Sending 120 bytes of metadata to masterserver (78.32.128.149 port 37922)
Flushing 127 bytes to masterserver (78.32.128.149 port 37922)
Broadcasting packet of 120 bytes from client1 (MYSELF)
Sending packet of 120 bytes to masterserver (78.32.128.149 port 655)
Packet for masterserver (78.32.128.149 port 655) larger than minimum MTU,
forwarding via TCP
Sending PACKET to masterserver (78.32.128.149 port 37922): 17 120
Sending 7 bytes of metadata to masterserver (78.32.128.149 port 37922)
Sending 120 bytes of metadata to masterserver (78.32.128.149 port 37922)
Flushing 127 bytes to masterserver (78.32.128.149 port 37922)
Sending PING to masterserver (78.32.128.149 port 37922): 8
Sending 2 bytes of metadata to masterserver (78.32.128.149 port 37922)
Flushing 2 bytes to masterserver (78.32.128.149 port 37922)
Got PONG from masterserver (78.32.128.149 port 37922): 9
Got PING from masterserver (78.32.128.149 port 37922): 8
Sending PONG to masterserver (78.32.128.149 port 37922): 9
Sending 2 bytes of metadata to masterserver (78.32.128.149 port 37922)
Flushing 2 bytes to masterserver (78.32.128.149 port 37922)*

Again, no pinging to 192.168.2.1 (should be masterserver) and I certainly
can't use it for anything.

The configuration files for the Windows XP side are:

*\vpn\tinc.conf*

Name = client1
ConnectTo = masterserver

*\vpn\hosts\masterserver*

Address = ******tech.homeip.net
Subnet = 255.255.255.0
-- key data --

*\vpn\hosts\client1*

Address = ******monster.homeip.net
Subnet = 255.255.255.0
-- key data --

*ipconfig results*

Ethernet adapter VPN:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 192.168.2.2
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . . . . :

I'm sure you probably get this an aweful lot and its probably something
irratatingly simply, but if anyone could help, that would be hugely
appreciated.

Thank-you kindly.

Andy Barlow
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20100707/e2bd4b35/attachment.htm>