Lock couchbase to a particular IP
When installing couchbase, it appears to start all its daemon processes on all IP addresses / ethernet ports.
Is there a way to restrict couchbase and all related forked processes to only startup on a particular IP address?
I want to install on a VPS with 2 ethernet cards (one is public and one is private). I only want couchbase to expose itself on the private side of the network.
I know I can manipulate the firewall with Iptables, and will if it comes to that. I was hoping for something a bit easier however.
~~~~~~~
On a related note, when working at home with a computer that has neither a DNS entry or a static IP, I noticed that couchbase can't connect properly if the DHCP license expires and I get a new IP. Since this is a windows machine, I change the IPADDR.OUT file in couchbase/server/bin and then run "service_reregister.bat". But, when I do that I lose all the data in the bucket (it goes back to an uninitialized state). Is this the proper way to do this?
At the moment, it always listens on all interfaces. You can control which interface is used with routing and you know that you can restrict it with firewalls. There is no simple way to change which IP it listens on.
On the related question, I think you can actually move the data to a new directory when you change the IP (make sure the service is offline when you do) and you'll keep your data. It may be better to configure some persistent interface (not on DHCP) that may not be the primary one-- just another loopback, and run it on that? For instance, you could put 127.0.0.1 in where the service binds.