From: Eliezer Croitoru <eliezer@ngtech.co.il>
To: netfilter@vger.kernel.org
Subject: What is the "algorightm" that decides on the routing path?
Date: Fri, 07 Mar 2014 02:13:17 +0200 [thread overview]
Message-ID: <53190F1D.2050309@ngtech.co.il> (raw)
What is the "algorightm" that decides on the routing path?
I am asking to understand how to explain the decision of multi dual
weight nexthop routes.
For example I do have a client with one router which load balance
towards two other routers with NAT on them using two different IP
addresses as outgoing IP.
so client 192.168.120.1 goes to 192.168.120.254 with the other leg at
192.168.130.254 and two next hops with 130.1 and 130.2 with another leg
at the 192.168.10.X leg.
Now I want to make sure I understand how exactly it is decided with what
nexthop will the packet be delivered towards?
There must be a "Static" way to calculate it.(ip? port? etc?)
Thanks,
Eliezer
reply other threads:[~2014-03-07 0:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53190F1D.2050309@ngtech.co.il \
--to=eliezer@ngtech.co.il \
--cc=netfilter@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.