I spent some time thinking about your points, and here's the conclusion
I came to:
(i) what you are proposing is essentially weak ES (with longest prefix match),
with a variant to the cost used for ECMP: within a set of equal
prefix length routes, the ones that have a src addr match
On Fri, Apr 16, 2010 at 12:08:28PM -0400, James Carlson wrote:
On 04/16/10 11:35, sowmini.varad...@oracle.com wrote:
should deal with forwarded packets. Since the hostmodel feature (and
esp the strong version and its variants) by its very name is not
intended for use for routing/forwarding,
sowmini.varad...@oracle.com wrote:
On (04/12/10 16:47), James Carlson wrote:
Sebastien Roy wrote:
This case proposes a new hostmodel property for the IP module that
can have 3 settings: strong, weak and src-priority. Some sample
incantations for setting the tunable are provided in the
On (04/13/10 08:06), James Carlson wrote:
Yes, I believe that was flagged in the man page updates (no?). In case
it was missed in the fast-track, here's what was intended:
That's all that was missed. In the quoted text above, it says 3
settings, but there are actually 4. It's just a
On (04/13/10 10:00), James Carlson wrote:
So when host1 go to respond, we'd look up a route in the strong-es mode
first, and assuming that there are no bugs in the src-address selection
(there were none when I tested this!) code, host1 would pick x.x.y.host1
as the src address, B as the
Sebastien Roy wrote:
This case proposes a new hostmodel property for the IP module that
can have 3 settings: strong, weak and src-priority. Some sample
incantations for setting the tunable are provided in the Examples
section.
It looks like there's a fourth (reportable, not settable) value
