Tinc doesn't connect

Guus Sliepen guus at sliepen.warande.net
Mon Mar 19 15:34:24 CET 2001


On Mon, Mar 19, 2001 at 01:23:02PM +0100, Marcel Loesberg wrote:

> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> cable204.196.en cable001.192.en 255.255.255.255 UGH   0      0        0 eth1
> gw.rdam.motosot *               255.255.255.255 UH    0      0        0 eth0
> mail.motosoto.c *               255.255.255.255 UH    0      0        0 eth1

Are the above routing entries really necessary?

> 192.168.200.0   *               255.255.255.0   U     0      0        0 tap0
> 192.168.200.0   *               255.255.255.0   U     0      0        0 tap0

Duplicate routing entries...

> default         cable001.192.en 0.0.0.0         UG    0      0        0 eth1
> default         cable001.192.en 0.0.0.0         UG    1      0        0 eth1

Duplicate routing entries...

This probably is't the problem, but it's a good idea to clean your routing
table anyway.

> Chain forward (policy ACCEPT):
> target     prot opt     source                destination           ports
> MASQ       all  ------  192.168.0.0/24       anywhere              n/a

Did you specify the -i option for this rule to restrict masquerading two a
specific outgoing interface?

Furthermore, could you run tincd with the -ddddd option and show us the
resulting syslog messages from the start of tinc up till the error?

-------------------------------------------
Met vriendelijke groet / with kind regards,
  Guus Sliepen <guus at sliepen.warande.net>
-------------------------------------------
See also: http://tinc.nl.linux.org/
          http://www.kernelbench.org/
-------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20010319/5b92e6eb/attachment.pgp


More information about the Tinc mailing list