Please help debug Windows setup

[Adam Macielinski]

Hi - Thanks to Sven-Haegar and Donald, but still having issues setting up with Windows.  Machine1 can't ping the VPN address of machine2.



Regular IPv4 address for both machines in 192.168.1.xxx range.



Router:

Forwarding port 655 to 101.102.103.1, UDP and TCP

Forwarding port 656 to 101.102.103.2, UDP and TCP



Tinc.conf on machine user1 just three lines:



Name = vpnuser1

ConnectTo = vpnuser2

Interface = TincVPN



TAP adapter (TAP-Windows Adapter V9) named TincVPN, and configured to 101.102.103.1 / 255.255.0.0



Tinc.conf on machine user2 just three lines:



Name = vpnuser2

ConnectTo = vpnuser1

Interface = TincVPN



TAP adapter (TAP-Windows Adapter V9) named TincVPN, and configured to 101.102.103.2 / 255.255.0.0



Hosts folder on both machines contains two files:



vpnuser1

Address = xyz.ddns.net

Port = 655

Subnet = 101.102.103.1/32

--RSA KEY--



vpnuser2

Address = xyz.ddns.net

Port = 656

Subnet = 101.102.103.2/32

--RSA KEY--



I've confirmed that xyz.ddns.net has the correct IP address (matches the WAN address of the router), and is set up as "DNS Host (A)".  Tinc service on both machines is running.  RSA keys generated on each of machines user1 and user2.  Local Windows firewalls allow incoming UDP and TCP traffic on all ports and IP addresses.



Any idea on how can I debug this thing?  Seems so close, but so far away.  Appreciate all thoughts.



Cheers,

Adam



From: Sven-Haegar Koch
Sent: Tuesday, July 14, 2015 5:14 AM
To: tinc at tinc-vpn.org
Subject: Re: Please help debug Windows setup


BindToAddress = 192.168.1.45 655
Subnet = 192.168.1.45

You should use different IP ranges for inside the VPN and outside of it
- otherwise your OS does not now how to reach the destination IP
correctly.

So for example change the Subnet statements to 192.168.2.x

Greetings
Haegar


On Mon, 13 Jul 2015, Donald Pearson wrote:

> Make sure your router supports nat reflection and has it enabled.
>
> On Mon, Jul 13, 2015 at 5:44 PM, Adam Macielinski <adam at macielinski.net> wrote:
> > Hi,
> >
> >
> >
> > Thanks to John Wice for helping me with an earlier question.  My two PCs
> > behind the same router are still having problems connecting.  Would
> > appreciate thoughts on what I’m doing wrong…
> >
> >
> >
> > Router:
> >
> > Port 655 forwarded to 192.168.1.45, both TCP and UDP
> >
> > Port 656 forwarded to 192.168.1.51, both TCP and UDP
> >
> >
> >
> > Machine #1.
> >
> > ==========
> >
> > Local IP address on LAN = 192.168.1.45
> >
> > Windows Firewall allows all incoming TCP and UDP traffic for the
> > Tinc.TincVPN service.
> >
> >
> >
> > Tinc.conf:
> >
> > Name = Adam
> >
> > ConnectTo = Erika
> >
> > Interface = TincVPN
> >
> > BindToAddress = 192.168.1.45 655
> >
> >
> >
> > Hosts/Adam:
> >
> > Address = XYZ.ddns.org  [WAN IP address, of router]
> >
> > Port = 655
> >
> > Subnet = 192.168.1.45
> >
> >
> >
> > Hosts/Erika:
> >
> > As below
> >
> >
> >
> > Machine #2.
> >
> > ==========
> >
> > Local IP address on LAN = 192.168.1.51
> >
> > Windows Firewall allows all incoming TCP and UDP traffic for the
> > Tinc.TincVPN service.
> >
> >
> >
> > Tinc.conf:
> >
> > Name = Erika
> >
> > ConnectTo = Adam
> >
> > Interface = TincVPN
> >
> > BindToAddress = 192.168.1.51 656
> >
> >
> >
> > Hosts/Erika:
> >
> > Address = XYZ.ddns.org  [WAN IP address, of router, same as above]
> >
> > Port = 656
> >
> > Subnet = 192.168.1.51
> >
> >
> >
> > Hosts/Adam:
> >
> > As above
> >
> >
> >
> >
> >
> > Cheers,
> >
> > Adam
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > tinc mailing list
> > tinc at tinc-vpn.org
> > http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
> >
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>

c'ya
sven-haegar

--
Three may keep a secret, if two of them are dead.
- Ben F.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20150721/13fffa41/attachment.html>