The element to use is host, not interface here (if I understand correctly what you want to do).
Regards JB On Aug 16, 2016, 07:31, at 07:31, Chandan <[email protected]> wrote: >Hello, > >My another machine is not able to identify even in the same network >below is my configuration. Correct me if i am wrong > ><network> > <port auto-increment="true" port-count="100">5701</port> > <outbound-ports> > > <ports>0</ports> > </outbound-ports> > <join> > <multicast enabled="false"> > <multicast-group>224.2.2.3</multicast-group> > <multicast-port>54327</multicast-port> > </multicast> > <tcp-ip enabled="true"> > <interface>127.0.0.1</interface> > <interface>10.165.20.45</interface> > </tcp-ip> > <aws enabled="false"> > <access-key>my-access-key</access-key> > <secret-key>my-secret-key</secret-key> > > <region>us-west-1</region> > > <host-header>ec2.amazonaws.com</host-header> > > <security-group-name>hazelcast-sg</security-group-name> > <tag-key>type</tag-key> > <tag-value>hz-nodes</tag-value> > </aws> > </join> > <interfaces enabled="true"> > <interface>10.165.20.*</interface> > </interfaces> > <ssl enabled="false"/> > <socket-interceptor enabled="false"/> > <symmetric-encryption enabled="false"> > > <algorithm>PBEWithMD5AndDES</algorithm> > > <salt>thesalt</salt> > > <password>thepass</password> > > <iteration-count>19</iteration-count> > </symmetric-encryption> > </network> > > > >-- >View this message in context: >http://karaf.922171.n3.nabble.com/Cellar-Clustering-in-karaf-tp4047542p4047544.html >Sent from the Karaf - Dev mailing list archive at Nabble.com.
