From: "Barry A Rich" <barich@trisectrix.com>
To: 'Mail List - Netfilter' <netfilter@vger.kernel.org>
Cc: casper@meteor.dp.ua
Subject: RE: UDP stream load balancing across multiple uplinks
Date: Mon, 4 Aug 2008 09:57:14 -0400 [thread overview]
Message-ID: <000301c8f63a$00215660$00640320$@com> (raw)
In-Reply-To: <1217834772.4178.7.camel@casper.meteor.dp.ua>
> -----Original Message-----
> From: netfilter-owner@vger.kernel.org
[mailto:netfilter-owner@vger.kernel.org]
> On Behalf Of ??????????? ??????
> Sent: Monday, August 04, 2008 3:26 AM
> To: barich@trisectrix.com
> Cc: 'Mail List - Netfilter'
> Subject: RE: UDP stream load balancing across multiple uplinks
>
> В Пнд, 28/07/2008 в 09:33 -0400, Barry A Rich пишет:
> > > -----Original Message-----
> > > From: netfilter-owner@vger.kernel.org
> > > [mailto:netfilter-owner@vger.kernel.org]
> > > On Behalf Of Grant Taylor
> > > Sent: Friday, July 25, 2008 11:10 AM
> > >
> > > 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.
> >
> > The following setup does load balancing across the uplinks. However, the
> > source address in the outgoing packets is not being SNAT'ed. Any
> > suggestions?
>
> Only first packet of udp "connection" is reaching the rule in the nat
> table and does the job, since nat occurs for all packets in this
> connection rest of rules would not match.
I understand better. I removed the following rule:
#iptables -t raw -A PREROUTING -i eth0 -p udp --sport $SPORT -j NOTRACK
The connection is tracked and the outgoing UDP packets are SNAT-ed. However,
the source address for all UDP packets is the IP address of the uplink
assigned to the connection (regardless of the uplink they actually are
sent).
Is there a way to SNAT without connection tracking?
next prev parent reply other threads:[~2008-08-04 13:57 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
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 [this message]
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='000301c8f63a$00215660$00640320$@com' \
--to=barich@trisectrix.com \
--cc=casper@meteor.dp.ua \
--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