From: Sertys <sertys@supportivo.org>
To: Netfilter list <netfilter@lists.netfilter.org>
Subject: Re: Iptables and vserver
Date: Sun, 20 Mar 2005 19:52:34 +0200 [thread overview]
Message-ID: <opsnx6lwh276nf2y@xonix> (raw)
In-Reply-To: <Pine.LNX.4.62.0503201728510.4948@l01.thnet>
On Sun, 20 Mar 2005 17:34:27 +0100 (CET), Michael Tautschnig
<michael.tautschnig@zt-consulting.com> wrote:
> Hello,
>>
>> So set up PRE- and POSTROUTING rules and I was able to transparently
>> access
>> the 10.0.1.x network. However of course I am not able to access the SSH
>> and
>> HTTP servers on the host itself anymore because iptables can not
>> differentiate between the SSH and HTTP server provided by my host with
>> the
>> (one and only) public IP address and those servers provided by the
>> Vserver
>> the host also acts as a DNS server for. Can anybody point me to feasable
>> solutions to this problem because I don't want (or actually I simply
>> can't)
>> to use more than public IP address on the host. Anyone? Might that be
>> possible with advanced routing maybe?
>>
>
> I don't think this would ever be possible with advanced routing or the
> like - how would the server know, whether you are trying to access the
> vserver or the router? But it could be easily one, if you just changed
> the ports of the ssh/http-daemons to, let's say, 23 and 81 ...
>
> It could probably be done for http, though, if you are using different
> names for the instances provided by the vservers and the ones on the
> router using layer7-filter.
>
> Regards,
> Michael
Indeed michael is right. It's stupid to have several IP's sharing a domain
name and vice versa unless for service backup. Since you are vhosting you
can split the traffic on http proto queries and redirect it. You may do
that with squid for example, cause it talks http. NameVhosting is another
solution, but then you just have to issue a redirect page from your
main(the public one) server and cross your fingers the clients use HTTP1.1
:) It's a bit harder, not to say impossible to redirect trafic different
from HTTP. SSH packets would come with destination a.b.c.d and not
containt some headers like "I wanna reach vmachine2.a.b.c.d". Thus, get
your services across different ports. 222,2222,22222 is easy to remember :)
--
www.supportivo.org
I can't stop myself checking for pigs in the outlets. Everybody thinks i'm
a punk, cause of the hairstyle(220V).
end
prev parent reply other threads:[~2005-03-20 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 16:10 Iptables and vserver Werner Schalk
2005-03-20 16:34 ` Michael Tautschnig
2005-03-20 17:52 ` Sertys [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=opsnx6lwh276nf2y@xonix \
--to=sertys@supportivo.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.