From: Grant Monroe <grant@janrain.com>
To: lartc@vger.kernel.org
Subject: [LARTC] IPSec tunnel problem
Date: Fri, 23 Apr 2004 19:58:47 +0000 [thread overview]
Message-ID: <40897577.7050606@janrain.com> (raw)
I am attempting to setup a simple network-to-network IPSec tunnel. The
tunnel appears to be setup correctly because I can make connections
between the networks and tcpdump shows esp packets going between the two
gateways. My problem is that I cannot make connections from one gateway
to the other through the tunnel. I think that this is a routing issue.
Here is some more info about my network:
192.168.1.1 10.0.0.6 10.0.0.9
192.168.2.1
192.168.1.7 +-----------+
+-----------+ 192.168.2.14
+-----+ | Gateway | | Gateway
| +-----+
| Foo | -- 192.168.1.0/24 -- | A | -- 10.0.0.0/24 -- | B
| -- 192.168.2.0/24 -- | Bar |
+-----+ +-----------+
+-----------+ +-----+
So, for example, Foo can ping Bar, but Gateway A can't ping Gateway B's
private interface or Bar.
Thanks for any help.
Grant Monroe
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-04-23 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 19:58 Grant Monroe [this message]
2004-04-26 15:06 ` [LARTC] IPSec tunnel problem Jason A. Pattie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40897577.7050606@janrain.com \
--to=grant@janrain.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.