RFH -> Request for Help.

[Geoff Norton]

Ivo et All,

  Changing 192.168.1.0 to 192.168.1.10 fixed the ping problem between A
and B, they can now talk and telnet and everything nicely.  

  However, other than the 2 routers I can't talk.

  For instance.. 192.168.1.10 pings 192.168.0.3.
 
  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.

  Ideas?? (Thanks for everyones help to date)

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.

On Mon, 27 Mar 2000, Ivo Timmermans wrote:

> On Mon Mar 27 2000, Geoff Norton <geoff at iRover.com> wrote:
> > Ivo,
> > 
> >   I've sent this directly to you simply because I'm going to paste all
> > output and obviously for security reasons I don't want internal ips going
> > out on a mailing list:
> 
> Understandable.  I send the reply to the mailinglist though.
> 
> 
> > HOST A SETTINGS:
> > 
> > TapDevice = /dev/tap0
> > MyVirtualIP = 192.168.1.0/24
> 
> This is wrong.  Should be 192.168.1.10.
> 
> 
> > 
> > HOST B SETTINGS:
> > 
> > TapDevice = /dev/tap0
> > MyVirtualIP = 192.168.0.237/24
> 
> So you did it right here...
> 
> 
> > 
> > PING FROM A.HOST1 (A host on the subnet in A) -> B.HOST1 (A host on the
> > subnet in B)
> > See ping get to A, See ping get to B, no response generated.
> 
> Does the packet travel past B onto the network 192.168.0 ?
> 
> 
> -- 
> Ivo Timmermans
> 
> You are just jealous because the little voices are talking to me.
> 


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