RFH -> Request for Help.

[Geoff Norton]

On Mon, 27 Mar 2000, Guus Sliepen wrote:

> On Mon, 27 Mar 2000, Geoff Norton wrote:
> 
> >   I see packet go across vpn and get to 192.168.0.237, however
> > 192.168.0.237 doesn't pass it over to the eth0 device to get to
> > 192.168.0.3.
> 
> Make sure:
> 
> - ARP is off on the tap devices (ifconfig -arp tap0)

  ARP is off.

> - routes are set correctly on all computers:
>   192.168.0.3: route add 192.168.0.0 netmask 255.255.0.0 gw 192.168.0.237
>   192.168.0.237: route add 192.168.0.0 netmask 255.255.255.0 eth0

  The routing is fine, because 192.168.0.237 is the default gateway for
192.168.0.3, hence he forwars the packets with him as the gateway for
192.168.1.* automatically.

> - echo 1 >/proc/sys/net/ipv4/ip_forward

  This is already done.

> - firewall rules allow passage of such packets

  Firewalling allows the passage of the packet.

> - packets should NOT be masqueraded
> 

  No masquerading going on.

  It looks to me that the packet goes over the vpn and gets picked up by
the tap device on the other side, but never gets forwarded off the tap
device to the kernel routing table.

Geoff Norton
------------
iRover.com Director of Technology
Pager: (416)381-1665
geoff at iRover.com
geoff at timecity.org
Lead Network Developer of the Time City project.



-
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/