From: Andreas Unterkircher <unki@netshadow.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IPSec tunnel and routing
Date: Mon, 05 Dec 2005 05:08:30 +0000 [thread overview]
Message-ID: <4393CB4E.8050707@netshadow.at> (raw)
In-Reply-To: <877jakjpt0.fsf@vinci.loc>
Alexander Kotelnikov schrieb:
> Ok, I would not ask all this if I have no problem with
> tunnelling. With configuration like described above, where multihomed
> maches have ip-addresses (192.168.1.1, 10.1.0.1) and (192.168.2.1,
> 10.2.0.1) tunneling works for all machines, but these two
> routers. This happenes becase if we send a packet from 10.1.0.1 into
> 192.168.2/24 this packet does not come to ipsec, but is pushed to
> default gateway, if it exists. In other words, local generated packets
> do not come through prerouting or something.
>
You have to add a route on 10.1.0.1 to make sure packets which belong to
192.168.2.0/24 have
a src address of 192.168.1.1. Then the packet should go through the
ipsec tunnel. Similar route in
the other direction has to be used on 10.2.0.1.
Cheers,
Andreas
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-12-05 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 1:27 [LARTC] IPSec tunnel and routing Alexander Kotelnikov
2005-12-05 5:08 ` Andreas Unterkircher [this message]
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=4393CB4E.8050707@netshadow.at \
--to=unki@netshadow.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox