From: David Ahern <dsahern@gmail.com>
To: Markus Moeller <huaraz@moeller.plus.com>, netdev@vger.kernel.org
Subject: Re: More complex PBR rules
Date: Sun, 7 Jul 2019 07:24:40 -0600 [thread overview]
Message-ID: <3fe925c0-e26f-492d-2552-b13a14451e3e@gmail.com> (raw)
In-Reply-To: <AFAC77AC6F8347289E6900614A523B32@Ultrabook1>
On 7/6/19 5:06 PM, Markus Moeller wrote:
> Hi Network developers
>
> I am new to this group and wonder if you can advise how I could
> implement more complex PBR rules to achieve for example load balancing.
> The requirement I have is to route based on e.g. a hash like:
>
> hash(src-ip+dst-ip) mod N routes via gwX 0<X<=N ( load balance
> over N gateways )
Have you tried multipath routing? Does that not work for you?
>
> This would help in situations where I can not use a MAC for identifying
> a gateway ( e.g. in cloud environments) .
>
> Could someone point me to the kernel source code where PBR is performed ?
>
net/core/fib_rules.c
next prev parent reply other threads:[~2019-07-07 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 23:06 More complex PBR rules Markus Moeller
2019-07-07 13:24 ` David Ahern [this message]
2019-07-07 23:20 ` Markus Moeller
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=3fe925c0-e26f-492d-2552-b13a14451e3e@gmail.com \
--to=dsahern@gmail.com \
--cc=huaraz@moeller.plus.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox