<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: RE: options config...
From: Amith Varghese <amith,AT,xalan,DOT,com>
Date: Wed, 12 Feb 2003 22:30:56 +0100
In-reply-to: <7DB0958915FDD611961400A0C98F18460BCE70@WINTRIX.thermeon.com>

I spoke too soon.  I can ping Linux B from Linux A with no problems.  However 
if
I don't use the tunnel for a little while, I am unable to initiate a ping to
Linux A from Linux B.  If I go back to Linux A and then ping Linux B and then
try again from Linux B back to Linux A everything works.  Looks like Linux A 
is
unable to initiate the tunnel.

Any ideas about why this is happening?

Thanks
Amith

> Thanks everyone.... things are up and running smoothly.  I used the internal
> IP
> address for "me" and it now works.
> 
> Thanks
> Amith
> >
> > > I have the following setup as stated before in my last message
> > >
> > > Linux A--------NAT/Firewall---| Internet |-----------Linux B
> > >
> > >
> > > Linux A has an internal IP address of 192.168.1.1.  The NAT/Firewall is
> > > set up
> > > so that all packets going to a particular IP (lets say 4.5.6.7) gets
> NATed
> > > to
> > > Linux A.
> > >   So based on what everyone is telling me, I should set Linux
> > > B's "peer" setting as 4.5.6.7:999?
> > >
> >     Yes
> >
> > >   If that is the case what should be Linux
> > > A's "me" setting (192.168.1.1 or 4.5.6.7 or 0.0.0.0)?
> > >
> >     Either 192.168.1.1 or 0.0.0.0
> >
> > --
> > Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> > Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> > Other commands available with "help" in body to the same address.
> > CIPE info and list archive:
> > <URL:http://sites.inka.de/~bigred/devel/cipe.html>
> >





<< | Thread Index | >> ]    [ << | Date Index | >> ]