From: Herman <Herman@AerospaceSoftware.com>
To: markee@bandwidthco.com, netfilter@lists.netfilter.org
Subject: Re: Invalid friggen argument
Date: Sun, 12 Oct 2003 19:22:01 -0600 [thread overview]
Message-ID: <200310121922.01492.Herman@AerospaceSoftware.com> (raw)
In-Reply-To: <LFEHKEBEBHAFGJBMNKAOIELHCCAA.markee@bandwidthco.com>
On Sunday 12 October 2003 7:01 pm, Herman@aerospacesoftware.com wrote:
I understand now. The machines that you are DNATTING to are dynamic, and
may or may not be on-line and listening. The service port is Java based
(sounds like Sun Microsystems Netlet protocol) but I gather it will always
be the same listening port, it is just the IP that changes. This is the
deal: you have an extra layer of complexity here that IPTables by nature
is not designed to handle. That's not to say it cannot be done. You are
going to need to build some dynamic variables into your script that run some
test for active IP's upon match of the port forwarding rule. Based on the
test results, you can tell IPTables what where to forward. For example,
when the rule is encountered, you could send a Ping to all the potential
hosts, then grab the IP of the host that responds, and then set iptables to
DNAT to that IP. That is just one way to accomplish this. So, it is
possible, but it is going to take some extra work.
Yikes - I think I'll settle for a fixed IP on one machine for starters. That
is proving to be enough of a headache.
As for your modules, masquerade works off it's own specific module so it
working is no indication of NAT working.
OK, that is beginning to make sense. So I have to try and figure out what
module is used for nat and see whether it is loaded.
Thanks!
--
Herman Oosthuysen
B.Eng(E), MIEEE
Aerospace Software Ltd.
Ph: 1.403.241-8773, Cell: 1.403.852-5545, Fx: 1.403.241-8841
Herman@AerospaceSoftware.com, http://www.AerospaceSoftware.com
next parent reply other threads:[~2003-10-13 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <LFEHKEBEBHAFGJBMNKAOIELHCCAA.markee@bandwidthco.com>
2003-10-13 1:22 ` Herman [this message]
2003-10-12 7:41 Invalid friggen argument Herman
2003-10-12 11:08 ` Willy TARREAU
2003-10-12 15:46 ` Herman
2003-10-12 17:44 ` Mark E. Donaldson
2003-10-12 18:18 ` Herman
2003-10-14 6:04 ` Joel Newkirk
2003-10-14 13:14 ` Herman
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=200310121922.01492.Herman@AerospaceSoftware.com \
--to=herman@aerospacesoftware.com \
--cc=markee@bandwidthco.com \
--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.