Tinc tunnel between two subnets

[Zia Syed]

On Machine B (notice new IP :( )

root at raspberrypi:/etc/tinc/erix# tincd -n erix -d 3

root at raspberrypi:/etc/tinc/erix# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
0.0.0.0         10.16.0.1       0.0.0.0         UG    0      0        0 eth0
10.16.0.0       0.0.0.0         255.255.0.0     U     0      0        0 eth0

root at raspberrypi:/etc/tinc/erix# INTERFACE=erix /etc/tinc/erix/tinc-up
RTNETLINK answers: File exists


On Machine A
root at homer1:/etc/tinc/erix# tincd -n erix -d 3

root at homer1:/etc/tinc/erix# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 em1
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0
docker0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 em1

root at homer1:/etc/tinc/erix# INTERFACE=erix /etc/tinc/erix/tinc-up
RTNETLINK answers: File exists



On Tue, Jul 8, 2014 at 1:27 PM, Guus Sliepen <guus at tinc-vpn.org> wrote:

> On Tue, Jul 08, 2014 at 12:33:10PM -0700, Zia Syed wrote:
>
> > Thanks guys. First off, i removed the 15.0.0.0 and now I can am not able
> to
> > ping even A and B. Here is the updated network diagram.
> > http://cl.ly/image/0E1n0s1v043u
> >
> > On Machine A:
> > ---------------------------
> > ubuntu at homer:/etc/tinc/erix$ more hosts/esprit1
> > Subnet = 192.168.1.0/32
> > Address = <Public IP>
>
> The Subnet should be 192.168.1.0/24, not /32.
>
> > On Machine B:
> > ---------------------------
> > pi at raspberrypi /etc/tinc/erix $ more hosts/pi
> > Subnet = 10.16.50.0/32
>
> Here it's the same, it should be 10.16.50.0/24.
>
> > ubuntu at homer1:/etc/tinc/erix$ route -n
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref    Use
> > Iface
> > 0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0
> em1
> > 172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0
> > docker0
> > 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0
> em1
> [...]
> > Even though I have 'ip route add .." in both tinc-up, i dont see the
> route
> > in 'route -n'.
>
> Hm. When tinc is started, what happens if you run the tinc-up script by
> hand like this?
>
> INTERFACE=erix /etc/tinc/erix/tinc-up
>
> > pi at raspberrypi /etc/tinc/erix $ ping 192.168.1.150
> > PING 192.168.1.150 (192.168.1.150) 56(84) bytes of data.
> > From 192.168.1.150 icmp_seq=1 Destination Net Unknown
>
> That's tinc telling you it doesn't know about the IP address
> 192.168.1.150, because you added /32 instead of /24 Subnets in the host
> config files.
>
> > Could this be I am not setting the gateway for this route correctly on B?
>
> You should not have to set a gateway. The rest of your configuration
> looks fine to me, so the only problems are the Subnets and the fact that
> the routes are not added by the tinc-up script.
>
> --
> Met vriendelijke groet / with kind regards,
>      Guus Sliepen <guus at tinc-vpn.org>
>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20140708/020b2941/attachment.html>