From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: UDP stream load balancing across multiple uplinks
Date: Fri, 25 Jul 2008 10:09:45 -0500 [thread overview]
Message-ID: <4889ECB9.3090206@riverviewtech.net> (raw)
In-Reply-To: <000001c8ee61$67e4b7a0$37ae26e0$@com>
On 07/25/08 09:19, Barry A Rich wrote:
> Bonding is not required in this case. The system that receives the
> UDP stream does not care if the UDP packets have different source IP
> addresses. NAT would not be required in this case, but the ISP might
> drop packets if the source address does not match the uplink address.
>
> Given those assumptions, what's the best way to load balance across
> the uplinks? If netfilter cannot be configured to do this, can I
> change ip_conntrack to ignore UDP packets?
Given that the source IP of your packets can change mid stream, you
could use the "nth" match extension. Using "nth" you would match
packets to decide how to mark them and then use the mark to determine
what routing table to use which would ultimately decide which outbound
path to use.
Grant. . . .
next prev parent reply other threads:[~2008-07-25 15:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 1:23 UDP stream load balancing across multiple uplinks Barry A Rich
[not found] ` <a43edf1b0807241837n7e6dceb4id5a16dd56c6344a9@mail.gmail.com>
2008-07-25 14:19 ` Barry A Rich
2008-07-25 15:09 ` Grant Taylor [this message]
2008-07-26 21:36 ` Barry A Rich
2008-07-28 13:33 ` Barry A Rich
2008-08-04 7:26 ` Покотиленко Костик
2008-08-04 13:57 ` Barry A Rich
2008-08-04 14:41 ` Покотиленко Костик
2008-08-04 15:48 ` Barry A Rich
2008-08-04 17:46 ` Покотиленко Костик
[not found] ` <000001c8ee59$6e86fee0$4b94fca0$@com>
[not found] ` <a43edf1b0807250755s32268b93mcd3227a7f364203b@mail.gmail.com>
2008-07-25 15:10 ` Barry A Rich
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=4889ECB9.3090206@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox