RE: port forwarding through localhost

["Andy B." <globi@hot.lu>]

Yes, I know that I should have used some FQDN instead of localhost, but the
cirumstances that once were have changed a lot - I will do better next time
:-)

-j REDIRECT is imho just for redirecting towards the same host (localhost to
localhost), so of no use.

As a quick fix, I am now using rinetd which does the trick, but the overhead
is driving the server load up :-/

Andy

-----Original Message-----
From: Michael P. Brininstool [mailto:mikepb@hoplite.org] 
Sent: Tuesday, January 30, 2007 20:54
To: 'Andy B.'; netfilter@lists.netfilter.org
Subject: RE: port forwarding through localhost

I know this is a little late, but when doing services like this, it has
proved helpful in the past to have the customers use a FQDN
(full-qualified-domain-name) instead of an IP.  For example, I setup the
following: imap.domain.com, smtp.domain.com, www.domain.com,
mail.domain.com, mysql.domain.com, proxy.domain.com, ftp.domain.com, etc,
even if they are all on the same machine.  That way, as services need to be
split off onto their own machine, a simple DNS change moves the load.

In the manner of helping in your current situation, isn't there a -j
REDIRECT table?

--
Michael P. Brininstool