Andrei Popescu on 21/01/10 17:54, wrote:
On Wed,20.Jan.10, 23:58:35, Adam Hardy wrote:
Not allowed to do that - apparently it would foobar the local
network where the host server of my vserver sits. I've got to use
the public IP address if I configure this, but I'd feel happier if I
didn't have to listen on port 25 at all. I don't want any incoming
mail - I just want to send.
Unless I'm terribly mistaken (please point me to respective
documentation, because I would want to close that gap) there is no way a
server listening only to 127.0.0.1 is accessible or even seen from
"outside" the same computer. That is the whole point of it!
Maybe your hosting provider only wants to make sure you are not
listening to other *external* IPs?
This is a virtual server on a hosting system with many others - and that's what
the sysop said:
>>>>> No - please do not touch those at all, your vserver will stop working if
you do.
>>>>>
>>>>> They are the internal IP address of the vserver. The data centre LAN is
NAT'd.
>>>>>
>>>>> 10.153.118.230 internally equates directly to 205.153.118.230 externally.
>>>>>
>>>>> All services in your vserver *must* be bound to the 10.153.118.230 IP
address.
>>>>>
>>>>> *Very important:*
>>>>> *Never allow anything to bind to localhost or 127.0.0.1.*
>>>>>
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org