From: "Laurens van Alphen" <laurens.van.alphen@keenondots.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Advance Routing Guidance
Date: Thu, 15 Aug 2002 15:34:23 +0000 [thread overview]
Message-ID: <marc-lartc-102942575132399@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102939645206458@msgid-missing>
> so my Question is-->possible without **MASQUERADE** ??.. will the
> setup(as shown in docs) loadbalance for our real ip's ??
Short answer: No.
Long answer:
You should first answer the question: what kind of LB do you want? Incoming, outgoing or both? If you want incoming only, you don't need Julian's patches, nor NAT per sé. You can use DNS to balance your incoming connections and assing every backend server two IP addresses: one from both IP ranges.
If you want outgoing LB, or both:
Julian's patches work when you have more than one IP range, but each IP range is going only through one provider, that is: you do not have PI address space and do not use BGP4 to announce your routes through multiple providers. If you do have PI address space and speak BGP4, you don't need Julian's patches nor do you need NAT.
This is probably not your case, and the IP ranges you received from your providers are PA, that is they are part of the larger address space of your provider. This means that IP range 1 will only come through provider 1 and IP range 2 will only flow through provider 2.
Because of this: if you don't use NAT and assign an IP from IP range 1 to some machine, the server will never be able to use the link through provider 2, because his address is from IP range 1 and will only flow through provider 1 (read above). For this to work, you THUS need NAT.
Why don't you want to use NAT? NAT is not dirty. NAT is stable, fast, secure and saves you from renumbering your network when you switch providers.
Hope this is clear and helps, if not, ask.
Cheers,
Laurens van Alphen
Keen on dots
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-08-15 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 7:45 [LARTC] Advance Routing Guidance Arindam Haldar
2002-08-15 8:42 ` William L. Thomson Jr.
2002-08-15 15:34 ` Laurens van Alphen [this message]
2002-08-15 19:35 ` Arthur van Leeuwen
2002-08-15 21:06 ` Julian Anastasov
2002-08-16 14:52 ` Arindam Haldar
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-102942575132399@msgid-missing \
--to=laurens.van.alphen@keenondots.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.