All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nyamul Hassaan" <mnhassan@usa.net>
To: lartc@vger.kernel.org
Subject: [LARTC] VPN Solution
Date: Sun, 04 Feb 2007 02:49:28 +0000	[thread overview]
Message-ID: <00be01c74807$1d7b9dc0$58c170cb@isprossrv02> (raw)
In-Reply-To: <45629969.9050208@riverviewtech.net>


[-- Attachment #1.1: Type: text/plain, Size: 938 bytes --]

Greeting List Members,

I'm not sure if what I want to do is possible at all.  I have an office network (ONet) with 3 uplinks.  Each of these ISPs give me a block of /26 to /29 IP addresses, as my needs / demands are.

Now, I have a remote server (RS) hosted in a data center, which communicates between several hosts in my office.  What we want to do is encrypt the data being transferred between RS and ONet.

We already established a IPSEC tunnel between RS and ONet through 1 of the uplinks.  Is it possible to have 3 different IPSEC tunnels through the 3 uplinks, and then have a load balancing between the 3?

We have also taken a /26 block from the data center provider, and have routed the /26 through the IPSEC to our ONet.  Can we have the same /26 use the 3 uplinks configured as IPSEC tunnels and load balance between them?

If you need any more explanation, I would be happy to provide that.

Regards
HASSAAN


[-- Attachment #1.2: Type: text/html, Size: 1949 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2007-02-04  2:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21  6:15 [LARTC] VPN Solution Grant Taylor
2006-11-21  6:20 ` Rangi Biddle
2007-02-04  2:49 ` Nyamul Hassaan [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='00be01c74807$1d7b9dc0$58c170cb@isprossrv02' \
    --to=mnhassan@usa.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.