<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Andy,<div><br></div><div>The subnet variable in your configuration files should be:</div><div><br></div><div>Subnet=192.168.2.1/32</div><div><br></div><div>for masterserver and </div><div><br></div><div>Subnet=192.168.2.2/32</div><div><br></div><div>for client1.</div><div><br></div><div>Give that a try and let us know how you go.</div><div><br></div><div>Kind Regards,</div><div>Mike</div><div><br></div><div><br></div><div><br><div><div>On 07/07/2010, at 6:56 PM, Andrew Barlow wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hello,<br><br>I am having troubles with the following configuration in that it produces the following errors:<br><br><font size="4"><u><b>Masterserver:</b></u></font><br><br>On the server (yea, I know) side is a Linux machine called "<b>masterserver</b>". 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:<br>
<br><i>No response to MTU probes from client1 (87.82.30.179 port 655)<br>Cannot route packet from masterserver (MYSELF): unknown IPv4 destination address 192.168.2.2<br>Writing packet of 126 bytes to Linux tun/tap device (tun mode)<br>
Got PACKET from client1 (87.82.30.179 port 655): 17 120<br>Received packet of 120 bytes from client1 (87.82.30.179 port 655)<br>Broadcasting packet of 120 bytes from client1 (87.82.30.179 port 655)<br>Writing packet of 120 bytes to Linux tun/tap device (tun mode)<br>
Got PING from client1 (87.82.30.179 port 655): 8<br>Sending PONG to client1 (87.82.30.179 port 655): 9<br>Sending 2 bytes of metadata to client1 (87.82.30.179 port 655)<br>Flushing 2 bytes to client1 (87.82.30.179 port 655)<br>
Sending PING to client1 (87.82.30.179 port 655): 8<br>Sending 2 bytes of metadata to client1 (87.82.30.179 port 655)<br>Flushing 2 bytes to client1 (87.82.30.179 port 655)<br>Got PONG from client1 (87.82.30.179 port 655): 9<br>
Got PING from client1 (87.82.30.179 port 655): 8</i><br><br><br>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:<br>
<br><u><b>/vpn/tinc.conf</b></u><br><br>Name = masterserver<br>ConnectTo = client1<br><br><u><b>/vpn/hosts/masterserver</b></u><br><br>Address = ******<a href="http://tech.homeip.net/" target="_blank">tech.homeip.net</a><br>
Subnet = 255.255.255.0<br>
-- key data --<br><br><u><b>/vpn/hosts/client1</b></u><br><br>Address = ******<a href="http://monster.homeip.net/" target="_blank">monster.homeip.net</a><br>Subnet = 255.255.255.0<br>-- key data --<br><br><u><b>/vpn/tinc-up</b></u><br>
<br>
#!/bin/sh<br>ifconfig $INTERFACE 192.168.2.1 netmask 255.255.255.0<br><br><u><b>ifconfig results<br></b></u><br>vpn Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 <br> inet addr:192.168.2.1 P-t-P:192.168.2.1 Mask:255.255.255.0<br>
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1<br> RX packets:19 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:500 <br>
RX bytes:2205 (2.2 KB) TX bytes:336 (336.0 B)<br><br><font size="4"><br><u><b>Client1</b></u></font><br><br>The client (yes, I know) machine for this vpn is called "<b>client1</b>" and should have a VPN address of 192.168.2.2. This is running on <b>Windows XP</b>. 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.<br>
<br><i>{98FDEAFD-09AA-4437-88E2-D502F88E9D9A} (VPN) is a Windows tap deviceTap reader running<br>Listening on 0.0.0.0 port 655<br>Ready<br>Cannot route packet: ARP request for unknown address 192.168.2.2<br>Cannot route packet: ARP request for unknown address 192.168.2.2<br>
Cannot route packet: ARP request for unknown address 192.168.2.2<br>Cannot route packet from client1 <MYSELF>: unknown IPv4 destination address 192.168.255.255</i><br><br>And that just continues forever. However, sometimes it does exchange keys but then just seems to repeat this kind of thing:<br>
<br><i>Cannot route packet from client1 (MYSELF): unknown IPv4 destination address 192.168.255.255<br>Writing packet of 247 bytes to Windows tap device<br>Cannot route packet from client1 (MYSELF): unknown IPv4 destination address 192.168.255.255<br>
Writing packet of 302 bytes to Windows tap device<br>Cannot route packet from client1 (MYSELF): unknown IPv4 destination address 192.168.255.255<br>Writing packet of 277 bytes to Windows tap device<br>Broadcasting packet of 120 bytes from client1 (MYSELF)<br>
Sending packet of 120 bytes to masterserver (78.32.128.149 port 655)<br>Packet for masterserver (78.32.128.149 port 655) larger than minimum MTU, forwarding via TCP<br>Sending PACKET to masterserver (78.32.128.149 port 37922): 17 120<br>
Sending 7 bytes of metadata to masterserver (78.32.128.149 port 37922)<br>Sending 120 bytes of metadata to masterserver (78.32.128.149 port 37922)<br>Flushing 127 bytes to masterserver (78.32.128.149 port 37922)<br>Broadcasting packet of 120 bytes from client1 (MYSELF)<br>
Sending packet of 120 bytes to masterserver (78.32.128.149 port 655)<br>Packet for masterserver (78.32.128.149 port 655) larger than minimum MTU, forwarding via TCP<br>Sending PACKET to masterserver (78.32.128.149 port 37922): 17 120<br>
Sending 7 bytes of metadata to masterserver (78.32.128.149 port 37922)<br>Sending 120 bytes of metadata to masterserver (78.32.128.149 port 37922)<br>Flushing 127 bytes to masterserver (78.32.128.149 port 37922)<br>Sending PING to masterserver (78.32.128.149 port 37922): 8<br>
Sending 2 bytes of metadata to masterserver (78.32.128.149 port 37922)<br>Flushing 2 bytes to masterserver (78.32.128.149 port 37922)<br>Got PONG from masterserver (78.32.128.149 port 37922): 9<br>Got PING from masterserver (78.32.128.149 port 37922): 8<br>
Sending PONG to masterserver (78.32.128.149 port 37922): 9<br>Sending 2 bytes of metadata to masterserver (78.32.128.149 port 37922)<br>Flushing 2 bytes to masterserver (78.32.128.149 port 37922)</i><br><br>Again, no pinging to 192.168.2.1 (should be masterserver) and I certainly can't use it for anything.<br>
<br>The configuration files for the Windows XP side are:<br><br><u><b>\vpn\tinc.conf</b></u><br><br>Name = client1<br>ConnectTo = masterserver<br><br><u><b>\vpn\hosts\masterserver</b></u><br><br>Address = ******<a href="http://tech.homeip.net/">tech.homeip.net</a><br>
Subnet = 255.255.255.0<br>-- key data --<br><br><u><b>\vpn\hosts\client1</b></u><br><br>Address = ******<a href="http://monster.homeip.net/">monster.homeip.net</a><br>Subnet = 255.255.255.0<br>-- key data --<br><br><u><b>ipconfig results</b></u><br>
<br>Ethernet adapter VPN:<br><br> Connection-specific DNS Suffix . :<br> IP Address. . . . . . . . . . . . : 192.168.2.2<br> Subnet Mask . . . . . . . . . . . : 255.255.0.0<br> Default Gateway . . . . . . . . . :<br>
<br>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.<br><br>Thank-you kindly.<br><br>Andy Barlow<br>
_______________________________________________<br>tinc mailing list<br><a href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a><br>http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc<br></blockquote></div><br></div></body></html>