All of lore.kernel.org
 help / color / mirror / Atom feed
From: Per Jessen <per@computer.org>
To: netfilter@lists.netfilter.org
Subject: simple load-distribution setup - but weird behaviour
Date: Fri, 12 Mar 2004 11:49:35 +0100	[thread overview]
Message-ID: <c2s4k0$35s$1@sea.gmane.org> (raw)

Hi,

we're using iptables in a fairly primitive load-distribution setup - 

iptables -t nat -A OUTPUT -d 192.168.3.200 -j DNAT --to
192.168.3.101-192.168.3.108

All traffic originates on the local machine. It's been working fine for
quite a while, but today I noticed that only 7 of the 8 machines in the
cluster are being distributed to - 101,102,104,105,106,107,108 but not 103. 

There isn't an awful lot of traffic, perhaps 2-3 msgs/min. Kernel is 2.4.24. 
I tried telnet'ing to 103 (port 10025) which worked fine - and following
that 103 was suddenly also being distributed to automagically.

Is there a way of determining why 103 was not being distributed to? Or when
if this happens again, what can/should I look at? 


cheers
/Per Jessen, Zurich



             reply	other threads:[~2004-03-12 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 10:49 Per Jessen [this message]
2004-03-14 17:14 ` simple load-distribution setup - but weird behaviour Per Jessen

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='c2s4k0$35s$1@sea.gmane.org' \
    --to=per@computer.org \
    --cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.