HI Alejandro,
But I can't put the mail server to work because the Postfix can't
establish a connection to the amavisd. Because of the variety of
components I suspect that amavisd-new, spamassassin or clamav are
hardcoded to 127.0.0.1, so I can't use a private non-routable IP as
localhost.
I use
Hi Alejandro!
> Today I write to Herbert because I lost my mail account password, but
> now I retrieve itso I have a question to ask you. I have Debian Etch
> with a vserver, having a base host and two vservers. One of these
> vservers has a LDAP server with localhost mapped to a private
> non
Dear all,
Today I write to Herbert because I lost my mail account password, but
now I retrieve itso I have a question to ask you. I have Debian Etch
with a vserver, having a base host and two vservers. One of these
vservers has a LDAP server with localhost mapped to a private
non-routable IP a
On Thu, Oct 19, 2006 at 10:28:23AM +0200, Tomas Fasth wrote:
> Alexander Kabanov wrote:
> > let me rephrase you question - do you want an isolated localhost IP
> > address for each guest? Why would you need this?
>
> To Minimize exposure by binding local services to a local interface?
you can do
Alexander Kabanov wrote:
> let me rephrase you question - do you want an isolated localhost IP
> address for each guest? Why would you need this?
To Minimize exposure by binding local services to a local interface?
Local interface is a simple and automatic security feature. Yes, you can block
pub
People, I just want to know if there are any scenarios where it's
necessary the use of a like-localhost interface with IP 127.0.0.X/8 in
the vservers...or just mapping localhost to a non-routable IP it's
enough in order to run vservers without problems always ???
Thanks again.
Alejandro
Herbert
On Fri, Oct 13, 2006 at 03:18:30PM -0300, Alejandro Cabrera Obed wrote:
> (Sorry I write again becaause an error message)
>
> Dear all, I'm new at vservers so I was looking for some information
> about the localhost interface problem. I mean that if I want to run a
> service on localhost I have to
(Sorry I write again becaause an error message)
Dear all, I'm new at vservers so I was looking for some information
about the localhost interface problem. I mean that if I want to run a
service on localhost I have to bind localhost to the guest IP or to a
non-routable IP in the case I need a close
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it seems like many people have the same question over and over again.
yes, you can have localhost
vi /etc/hosts
xx.xx.xx.xx localhost
where xx.xx.xx.xx your guest IP
you can give 127.0.0.1 to a guest, but then your server shares it with
t
Dear all, I'm new at vservers so I was looking for some information
about the localhost interface problem. I mean that if I want to run a
service on localhost I have to bind localhost to the guest IP or to a
non-routable IP in the case I need a closed-service.
Otherwhise I have localhost mapped to
On Mon, Jul 03, 2006 at 10:35:44AM -0400, Paul S. Gumerman wrote:
> Herbert,
>
> This problem is on the *host*, not a guest.
>
> I've verified that none of the guests on vhost3 (the box with the
> problem) has anything to do with 127.0.0.1.
>
> Also, on vhost3, sshd with explicit "ListenAddress
Herbert,
This problem is on the *host*, not a guest.
I've verified that none of the guests on vhost3 (the box with the
problem) has anything to do with 127.0.0.1.
Also, on vhost3, sshd with explicit "ListenAddress" settings for the
host's ip as well as 127.0.0.1 will start and run without co
Herbert Poetzl wrote:
> basically I do not see a good reason for assigning
> 127.x.x.x to a guest, but if you have to, then try
> to choose different ones, e.g. 127.0.0.2, 127.0.0.3 ...
>
Does that work with ssh port forwarding?
I ran into this problem when I tried that:
http://sources.redhat
On Fri, Jun 30, 2006 at 08:51:58PM -0400, Paul S. Gumerman wrote:
> In it's own thread now -- sorry for the unintentional hijack.
>
> I have two practically identical vserver hosts, named vhost1 and vhost3.
>
> They are both running kernel CentOS (2.6.14.3-vs2.0.1-rc5) x86_64.
>
> /etc/hosts on
In it's own thread now -- sorry for the unintentional hijack.
I have two practically identical vserver hosts, named vhost1 and
vhost3.
They are both running kernel CentOS (2.6.14.3-vs2.0.1-rc5) x86_64.
/etc/hosts on each one is essentially the same, and the routes look
good and essentially
On Fri, Jun 30, 2006 at 09:51:38AM -0400, Paul S. Gumerman wrote:
> I have two practically identical vserver hosts, named vhost1 and vhost3.
>
> They are both running kernel CentOS (2.6.14.3-vs2.0.1-rc5) x86_64.
>
> /etc/hosts on each one is essentially the same, and the routes look good
> and e
I have two practically identical vserver hosts, named vhost1 and vhost3.
They are both running kernel CentOS (2.6.14.3-vs2.0.1-rc5) x86_64.
/etc/hosts on each one is essentially the same, and the routes look good
and essentially the same.
The ifconfig output for both looks the same, and both
Hello,
I'm at my last try to port an OpenExchange server, setup
with SLES9 and the commercial Version of OX, to a VServer.
I've gotten so far that everything seems to work, apart from
the admin interface, which is written in java. Which makes
debugging hard.
I've narrowed the problem down to th
On Fri, 2006-06-09 at 12:57 +0200, Herbert Poetzl wrote:
> not _instead_, but yes, you _can_ assign 127.0.0.1 to one (or more) guests,
> as every other IP
Okay, then this means that first-come-first-serve with regard to ports
to listen on?
Thanks Herbert.
___
On Thu, Jun 08, 2006 at 09:41:43PM -0700, Paul C. Bryan wrote:
> Just curious, is there a way I can designate lo's 127.0.0.1 to a VPS
> instead of root?
not _instead_, but yes, you _can_ assign 127.0.0.1
to one (or more) guests, as every other IP
HTH,
Herbert
> __
Just curious, is there a way I can designate lo's 127.0.0.1 to a VPS
instead of root?
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
hi all,
the only reason why I would like to have some kind of local/internal
interface inside a guest - let people bind services to something that
is not accessible from outside and from other guests on the host
server.
but this is not a big deal, imo - "good to have". I'm going to play
with NGN
On Wed, Jun 07, 2006 at 11:53:10PM +0200, Albert Shih wrote:
> Le 07/06/2006 à 22:39:35+0200, Andreas John a écrit
> > Hello,
> >
> > usually you set in you /etc/hosts file the host 'localhost' to the
> > public IP of the guest. There is no real need to have a 127.0.0.1
> > accessible. If you e.g
On Wed, Jun 07, 2006 at 03:43:38PM -0700, Alexander Kabanov wrote:
> hi,
>
> what about this (need to verify, going to this evening)
>
> ifconfig dummy0 10.10.10.10 up
>
> and then give two IPs to each guest, i.e. (vserver/interfaces)
>
> eth0 x.x.x.x - external IP
> dummy0 10.10.10.11 - intern
On Wed June 7 2006 17:43, Alexander Kabanov wrote:
> hi,
>
> what about this (need to verify, going to this evening)
>
> ifconfig dummy0 10.10.10.10 up
>
> and then give two IPs to each guest, i.e. (vserver/interfaces)
>
> eth0 x.x.x.x - external IP
> dummy0 10.10.10.11 - internal IP
>
> guest
hi,
what about this (need to verify, going to this evening)
ifconfig dummy0 10.10.10.10 up
and then give two IPs to each guest, i.e. (vserver/interfaces)
eth0 x.x.x.x - external IP
dummy0 10.10.10.11 - internal IP
guest's /etc/hosts
x.x.x.x guest01
10.10.10.11 localhost
unfortunatelly, most
Le 07/06/2006 à 22:39:35+0200, Andreas John a écrit
> Hello,
>
> usually you set in you /etc/hosts file the host 'localhost' to the
> public IP of the guest. There is no real need to have a 127.0.0.1
> accessible. If you e.g. ping 127.0.0.1 from within a guest, it get
> automatically mapped to th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
Alexander Kabanov wrote:
> I have 5 guests on the server, each guest has own localhost IP, like
> 127.0.0.5, 127.0.0.6 etc. (guests /etc/hosts has record like
> "127.0.0.5 localhost") it seemed the only option available. can
> someone tell me is i
hi,
I have 5 guests on the server, each guest has own localhost IP, like
127.0.0.5, 127.0.0.6 etc. (guests /etc/hosts has record like
"127.0.0.5 localhost") it seemed the only option available. can
someone tell me is it good approach? is there anything else beside
this? The reason why I want to h
Hello,
usually you set in you /etc/hosts file the host 'localhost' to the
public IP of the guest. There is no real need to have a 127.0.0.1
accessible. If you e.g. ping 127.0.0.1 from within a guest, it get
automatically mapped to the public IP of the guest.
If you need a 127-x address within you
Hi all
I've a vserver running two guests.
On one guest everything work fine. But on second I cannot have the name
resolution for localhost. Hi don't know localhost is 127.0.0.1, for example
I cannot make ping localhost.
And I don't have /etc/hosts file on booth guest.
How can I fix this.
Rega
Herbert Poetzl schrieb:
On Wed, Mar 08, 2006 at 09:52:22AM +0100, gerardi wrote:
Hello,
I am trying to connet to a mail server on the real server but within
the vserver the Ip 127.0.0.1 seems to be mapped to the First Virtual
Interface.
yes, that is not unexpected ...
I am usi
On Wed, Mar 08, 2006 at 09:52:22AM +0100, gerardi wrote:
> Hello,
>
> I am trying to connet to a mail server on the real server but within
> the vserver the Ip 127.0.0.1 seems to be mapped to the First Virtual
> Interface.
yes, that is not unexpected ...
> I am using the dummy device for a priva
Xavier Montagutelli schrieb:
Quoting gerardi <[EMAIL PROTECTED]>:
Hello,
I am trying to connet to a mail server on the real server but within
the vserver the Ip 127.0.0.1 seems to
be mapped to the First Virtual Interface.
I am using the dummy device for a private network between the
vse
Quoting gerardi <[EMAIL PROTECTED]>:
Hello,
I am trying to connet to a mail server on the real server but within
the vserver the Ip 127.0.0.1 seems to
be mapped to the First Virtual Interface.
I am using the dummy device for a private network between the
vservers and nat for access to the
inte
Hello,
I am trying to connet to a mail server on the real server but within the
vserver the Ip 127.0.0.1 seems to
be mapped to the First Virtual Interface.
I am using the dummy device for a private network between the vservers
and nat for access to the
internet but who kann i access the lo i
hi,
it seems possible to have localhost inside a guest. here is what I did
interface/0
dev - lo
ip - 127.0.0.1
prefix - 32
but when a daemon binds to a localhost port and the guest has external
interface, I'm able to access that service using guest external IP. I
just want to verify is this the
37 matches
Mail list logo
