All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arindam Haldar <arindamhaldar@inbox.lv>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Advance Routing Guidance
Date: Fri, 16 Aug 2002 14:52:02 +0000	[thread overview]
Message-ID: <marc-lartc-102950952108480@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102939645206458@msgid-missing>

hi julian
hi all
thanx to you all.. many doubts are now cleared.. the **NATing** 
soulution is ofcource a very steady one but am not able to convince my 
management for it !.. hopefully they will...
ys julian you r right :).. there were white spaces--it's patched 
perfectly now .. :) ..
to you all---> have a :) sunday..
:)
A.H

Julian Anastasov wrote:
> 	Hello,
> 
> On Thu, 15 Aug 2002, Arindam Haldar wrote:
> 
> 
>>after going thru the docs i find that with julians patch one needs to
>>**MASQUERADE** to the links... we dont want that !.. we want our real ip
>>to flow in these 2 links(real ip already being broadcasted on provider's
>>network)..
>>so my Question is-->possible without **MASQUERADE** ??.. will the
>>setup(as shown in docs) loadbalance for our real ip's ?? ..
> 
> 
> 	Of course, it is possible ... and depends on how restrictive
> are your providers. But if one link fails you can have the problem
> of using sources for the failed link, then the replies from world
> will hit the failed provider and will not reach you. As result,
> your internal servers should know which source addresses to use
> according to the link state. The masquerade simply guarantees that
> one link is used only from addresses that are reachable from this
> link.
> 
> 
>>what other things i have to consider ?..
> 
> 
> 	As for applying the patches you need to download them
> correctly. More likely you have white space problem (try with
> patch -l).
> 
> 
>>Awaiting a reply very very anxiously..
>>A.H
> 
> 
> Regards
> 
> --
> Julian Anastasov <ja@ssi.bg>
> 
> 
> 


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-08-16 14:52 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
2002-08-15 19:35 ` Arthur van Leeuwen
2002-08-15 21:06 ` Julian Anastasov
2002-08-16 14:52 ` Arindam Haldar [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=marc-lartc-102950952108480@msgid-missing \
    --to=arindamhaldar@inbox.lv \
    --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.