tinc - Sep 1999 - No subject

Hi,

I am using tin-0.3 and trying to route over a tinc tunnel.  Here is my
details:

   192.168.10.0/24
         / \
          |
          | ethernet network
          |
         \ /
-------------------------
| 192.168.10.254 (eth0) |
| Linux Router          |
| 192.168.0.1 (tap0)    |
-------------------------
         / \
          |
          |
          | tinc tunnel
          |
          |
         \ /
-------------------------
| 192.168.0.2 (tap0)    |
| Linux Router          |
| 192.168.20.50 (eth0)  |
-------------------------
         / \
          |
          | ethernet network
          | 
         \ /
   192.168.20.0/24


The tinc tunnel is up and 192.168.0.1 & 2 are talking ok, but when I try to
send a packet from 192.168.10.0/24 to 192.168.20.0/24 I get a message
similar to:

Sep 11 17:07:40 pegasus tincd.exosea02[17935]: An IP packet (0800) for
192.168.20.53 from 192.168.10.14
Sep 11 17:07:40 pegasus tincd.exosea02[17935]: trying to look up
192.168.20.53 in connection list failed.

So I looked it up, and I see it is trying to match 192.168.20.53 in its
connection list, which it is not there.

The routing is setup ok, it just seems tincd won't let my packets thru.
Can anyone shed some light on this?

Thankx

Chris


-- 
// Chris MacLean  Senior Systems Engineer  Global Media Corp. * //
// cmaclean@globalmedia.com  ICQ#25731309  http://globalmedia.com/
-
Tinc:         Discussion list about the tinc VPN daemon
Archive:      http://mail.nl.linux.org/lists/
Tinc site:    http://ftp.nl.linux.org/pub/linux/tinc/

Hi Chris,
> I am using tin-0.3 and trying to route over a tinc tunnel.  Here is my
> details:
> 
>    192.168.10.0/24
> | Linux Router          |
> | 192.168.0.1 (tap0)    |
>           | tinc tunnel
> | 192.168.0.2 (tap0)    |
> | Linux Router          |
>    192.168.20.0/24

Either:

a) Setup the routers to masquerade their respective ethernet LANs.
b) Tell tinc on both routers that its VPN address is 192.168.*
c) Change the IP address of the routers to be 192.168.10.xx on router
   1 and 192.168.20.xx on router 2

Option b might be the best, but it does mean that you can't connect
any other LANs to the VPN.


-- 
Ivo Timmermans

You are just jealous because the little voices are talking to me.
-------------- 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/19990920/d5dd6c47/attachment.pgp