Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3478

subnet-match is completely broken

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.2.0.Final, 9.0.0.Alpha1
    • 8.1.0.Final
    • None
    • None

    Description

      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) -------------------------------------------------------------------
      

      Attachments

        Activity

          People

            istudens@redhat.com Ivo Studensky
            rdicroce Richard DiCroce (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: