|
That's not really helpful, as I need
the (database) services on this machine, to be used by other
machines (so loopback isn't an option), when the cable is plugged
in.
I can understand this being the default behaviour on a desktop,
but this is really not acceptable behaviour on a server (the act
of accidentally unpluging a cable kills services that don't need
to use the cable). If there really is no way to turn this off,
then NetworkManager isn't really suitable for servers, and that
seems an unlikely intention.
Simon
On 07/12/13 11:11, Ritesh Khadgaray wrote:
Hi
On 6 Dec 2013 00:47, "Simon Bazley" <simon bazley themartingale com>
wrote:
>
> Hi,
>
> I've got a server which is running several databases and
web services, which is connected to both public and private
networks, via different physical network ports.
>
> All of the services communicate with each other using the
private IP 10.0.0.18 which is bound to the static ip address of
the private connection (on eth1). This server is self
contained, so the private connection is purely so that other
private computers can also access the databases contained on the
machine.
>
> However, when I physically unplug the cable from the
private network eth1 goes down, and looses it's IP address,
hence all the services on that machine stop being able to
communicate with each other.
>
> How do I tell NetworkManager, not to shut down that
interface on physical disconnect? It should be up, all the
time. All physical interfaces on that machine should be up all
the time.
>
> Simon
> _______________________________________________
Afaik, this is the expected behaviour. I would
suggest your apps to use 127.0.0.1 to talk to each other.
Cheers
T
|
