All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksander Kamenik <aleksander@krediidiinfo.ee>
To: lartc@vger.kernel.org
Subject: [LARTC] custom route for forwarded traffic
Date: Tue, 30 Oct 2007 14:38:12 +0000	[thread overview]
Message-ID: <472741D4.4050409@krediidiinfo.ee> (raw)

Hi,


I have two networks, users and servers connected via vpn (ipsec). Both 
internal networks. The routing is fine and connections work both ways.

Accordingly both networks have a firewall each which faces the internet 
and they create the vpn link between each other. Both firewalls have 
only one external IP (if they had more, I wouldn't be asking).

The servers network's firewall however does DNAT too. This is for 
external clients who connect to the external IP of the firewall and so 
can connect to the internal mail and webserver.

I want the computers in the users network to connect to the external IP 
of the servers firewall AND have the connection go through the VPN.

If I add a rule to the main routing table in the users network's 
firewall for servers network's external IP to go through the VPN, I will 
break the VPN connection (kind of like the chicken and egg problem).

So I need to create a route, which will apply only for forwarded 
connections. How do I do that?


Thanks,

-- 
Aleksander Kamenik
system administrator
+372 6659 649
aleksander@krediidiinfo.ee

Krediidiinfo AS
http://www.krediidiinfo.ee/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-10-30 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 14:38 Aleksander Kamenik [this message]
2007-10-30 16:14 ` [LARTC] custom route for forwarded traffic Grant Taylor

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=472741D4.4050409@krediidiinfo.ee \
    --to=aleksander@krediidiinfo.ee \
    --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.