# Elasticsearch Cluster discovery **URL:** \ **Category:** Elasticsearch\ **Created:** [June 5, 2014, 6:17pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-discovery/17936 "2014-06-05T18:17:03Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![asrozar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asrozar/32/675_2.png) [@asrozar](https://discuss.elastic.co/u/asrozar)\ **Post date:** [June 5, 2014, 6:17pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-discovery/17936/1 "2014-06-05T18:17:03Z")
I have 3 Elasticsearch servers setup on a CentOS KVM host. I'd like to lock these servers down with iptables but when I do this It kills the cluster (even with the propper ports open). So I thought I'd have two servers behind the KVM nat interface, and the primary server with two nics. One nic on the KVM nat network, and the other on my standard network that will make it accessible. I though that since they all are on the same "layer 2" network that the clustering would work fine but not so much. Is there a way that I can force the clustering to happen on my nat network? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f9eb5a64-2fe2-4bf3-8d9a-a8a4c253abca%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f9eb5a64-2fe2-4bf3-8d9a-a8a4c253abca%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 5, 2014, 10:59pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-discovery/17936/2 "2014-06-05T22:59:52Z")
ES runs on an all or nothing principal when it comes to networking. You cannot split cluster and API interfaces. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com) web: [www.campaignmonitor.com](http://www.campaignmonitor.com) On 6 June 2014 04:17, [avery.rozar@insecure-it.com](mailto:avery.rozar@insecure-it.com) wrote: > I have 3 Elasticsearch servers setup on a CentOS KVM host. I'd like to > lock these servers down with iptables but when I do this It kills the > cluster (even with the propper ports open). So I thought I'd have two > servers behind the KVM nat interface, and the primary server with two nics. > One nic on the KVM nat network, and the other on my standard network that > will make it accessible. I though that since they all are on the same > "layer 2" network that the clustering would work fine but not so much. Is > there a way that I can force the clustering to happen on my nat network? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/f9eb5a64-2fe2-4bf3-8d9a-a8a4c253abca%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f9eb5a64-2fe2-4bf3-8d9a-a8a4c253abca%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/f9eb5a64-2fe2-4bf3-8d9a-a8a4c253abca%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/f9eb5a64-2fe2-4bf3-8d9a-a8a4c253abca%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624YfBDOwj\_TSzrUYjqHpCth%3D\_Abg1DM%3Dg2%2BkzyoC9%3DsnFQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624YfBDOwj_TSzrUYjqHpCth%3D_Abg1DM%3Dg2%2BkzyoC9%3DsnFQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:24am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-discovery/17936/3 "2017-07-06T01:24:20Z")