From: Mike Nielsen <mike@getbent.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Complicated Route Statement
Date: Thu, 06 Feb 2003 05:03:21 +0000 [thread overview]
Message-ID: <marc-lartc-104450787219007@msgid-missing> (raw)
Hi there.
I am having trouble coming up with a routing statement for the following
Lan A is connected to LAn B via a Freeswan site to site VPN
On lab B there is a cisco router which is handles traffic for an IP address.
I need to find a way to have traffic to this Other machine routed through the
IPsec tunnel, to the Cisco.
Here's a crppy ascii art diagram to help explain
Lan A
192.168.24.128/26
192.168.24.130 iproute2 Firewall and VPN machine
|
| IPsec Tunnel
|
Lan B
192.168.24.1 Iproute2 Firewall and VPN machine
192.168.24.0/26 --- 192.168.24.2 Cisco Router <--> 198.185.204.0/24
So basically I need a route statement that says
route any traffic to 198.185.204.0/24 to 192.168.24.2 Via 192.168.24.2
??
Any help you all could give would be greatly appreciate
--
-----------------------------
|\/|ike@GetBent.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-02-06 5:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 5:03 Mike Nielsen [this message]
2003-02-06 12:41 ` [LARTC] Complicated Route Statement Matthew S. Crocker
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=marc-lartc-104450787219007@msgid-missing \
--to=mike@getbent.net \
--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.