+++ This bug was initially created as a clone of Bug #1111575 +++ A clone for 6.3.1. Description of problem: subnet-match does not respect the value attribute. Instead, it seems to just pick the first interface it finds. No matter what I specify as a value, even if it's a value that's complete nonsense and doesn't match any IP address on my system, e.g. <interface name="public"> <subnet-match value="1.2.3.0/24"/> </interface> the ports end up bound to the only interface that is currently connected 14:45:16,740 INFO [stdout] (ServerService Thread Pool -- 40) ------------------------------------------------------------------- 14:45:16,740 INFO [stdout] (ServerService Thread Pool -- 40) GMS: address=normandy/GamingPortal, cluster=GamingPortal, physical address=192.168.1.105:3100 14:45:16,741 INFO [stdout] (ServerService Thread Pool -- 40) -------------------------------------------------------------------
Ivo Studensky <istudens> updated the status of jira WFLY-3478 to Reopened
Ivo Studensky <istudens> updated the status of jira WFLY-3478 to Resolved