[ https://issues.jboss.org/browse/WFLY-11806?page=com.atlassian.jira.plugin... ] G. Richard Bellamy updated WFLY-11806: -------------------------------------- Description: socket-binding/jgroups-tcp client mappings do not map to the system property {{jgroups.external_addr}} correctly, and therefore jgroups ALWAYS advertises the address bound to the {{private}} interface. When setting the client mappings for the {{jgroups-tcp}} socket binding, wildfly should ensure that the pingdata for various discovery protocols announces the destination address set there, presumably by setting the {{jgroups.external_addr}} value. was: socket-binding/jgroups-tcp client mappings do not map to jgroups.external_addr properly, and therefore jgroups ALWAYS advertises the address bound to the {{private}} interface. When setting the client mappings for the {{jgroups-tcp}} socket binding, wildfly should ensure that the pingdata for various discovery protocols announces the destination address set there, presumably by setting the {{jgroups.external_addr}} value. -- This message was sent by Atlassian Jira (v7.12.1#712002)