* intended behavior of REDIRECT
@ 2008-04-15 18:10 Luke Elliott
2008-04-25 15:25 ` Jan Engelhardt
0 siblings, 1 reply; 2+ messages in thread
From: Luke Elliott @ 2008-04-15 18:10 UTC (permalink / raw)
To: netfilter
Hi
I'm trying to figure out the intended behavior of a REDIRECT rule such as:
iptables -t nat -A PREROUTING -p tcp --dport 9002 -j REDIRECT --to-ports
9003-9004
I'd like to balance connections to port 9002 across the two servers on
ports 9003 and 9004. Using the --random (or --random 1 with iptables
1.3.8...) option works, but what should the non-random rule actually do?
Digging around in the 2.6.24 kernel it seems to boil down to
tcp_unique_tuple() in nf_nat_proto_tcp.c. The interesting bit:
static u_int16_t port;
...
for (i = 0; i < range_size; i++, port++) {
*portptr = htons(min + port % range_size);
if (!nf_nat_used_tuple(tuple, ct))
return 1;
}
So if I'm reading this correctly, _port_ will only get incremented once
an in use tuple is hit. And assuming there are no other rules in place,
that means only after 64K-ish connections from a single host to port
9002? This seems to be what I see in practice - "everything" gets
forwarded to port 9003 (though TBH I've only tried a few hundred
connections).
So presumably the intention is not to round-robin connections, something
like:
for (i = 0; i < range_size; i++) {
*portptr = htons(min + port % range_size);
++port;
if (!nf_nat_used_tuple(tuple, ct))
return 1;
}
(Though no doubt that breaks lots of other usages of the function...)
An insight gratefully received!
Regards
Luke Elliott.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: intended behavior of REDIRECT
2008-04-15 18:10 intended behavior of REDIRECT Luke Elliott
@ 2008-04-25 15:25 ` Jan Engelhardt
0 siblings, 0 replies; 2+ messages in thread
From: Jan Engelhardt @ 2008-04-25 15:25 UTC (permalink / raw)
To: Luke Elliott; +Cc: netfilter
On Tuesday 2008-04-15 20:10, Luke Elliott wrote:
>
> iptables -t nat -A PREROUTING -p tcp --dport 9002 -j REDIRECT --to-ports
> 9003-9004
>
> I'd like to balance connections to port 9002 across the two servers on ports
> 9003 and 9004. Using the --random (or --random 1 with iptables 1.3.8...) option
> works, but what should the non-random rule actually do?
I'd rather use the two rules:
1. -m statistic --mode nth --every 2 -j REDIRECT --to-port 9003 +
2. (unconditional) -j REDIRECT --to-port 9004
Which will reliably RR over the ports.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-04-25 15:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-15 18:10 intended behavior of REDIRECT Luke Elliott
2008-04-25 15:25 ` Jan Engelhardt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox