Hi, Thanks for the reply.
The firewall on the node is off, and he can't comunicate with himself. The problem is: vm-motisqaapp02 has the local address 172.16.3.81 with the NAT 10.10.1.135. But, with the current data center definitions, it can't solve the 10.10.1.135 doesn't recognizing itself. Can I configure different adresses for network.publish host ? One for comunicating with outside nodes and another with itself? -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Problem-setting-up-cluster-with-NAT-address-tp4057849p4057867.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1403014356232-4057867.post%40n3.nabble.com. For more options, visit https://groups.google.com/d/optout.
