From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: iptables to redir subdomain to certain ports
Date: Sun, 14 Jan 2007 22:23:27 -0600 [thread overview]
Message-ID: <45AB01BF.1010600@riverviewtech.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0701131710290.19940@yvahk01.tjqt.qr>
On 01/13/07 10:11, Jan Engelhardt wrote:
> Only if www.domain.com has a distinct ip address from dl.domain.com. If
> that does not hold true, use Apache's mod_rewrite magic, because then
> you are actually working on l7 rather than l3.
I'm not sure that mod_rewrite by its self will provide that much help.
If you use mod_proxy, possibly in conjunction with mod_rewrite, you can
configure a virtual domain of Apache to be a reverse proxy. Thus when a
client connects to Apache on 80 asking for a virtual domain, Apache will
then go and as thttpd for the contents on behalf of the client. This
will mean that the clients will never have to choose a different port.
If you need help with such, email me directly as this is not really a
Netfilter issue.
Regarding L7 filter, it may work, but you would have to make sure that
the returning traffic was un-redirected. If you do not un-redirect the
traffic, there is a very good chance that clients will see returning
traffic directly from the thttpd server on port 81, thus the clients
firewall and / or client IP stack will stop the connection.
Grant. . . .
prev parent reply other threads:[~2007-01-15 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 15:34 iptables to redir subdomain to certain ports Andras Izsof
2007-01-13 16:11 ` Jan Engelhardt
2007-01-15 4:23 ` Grant Taylor [this message]
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=45AB01BF.1010600@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox