Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1111575 - (6.x) subnet-match is does not respect 'value' attribute
(6.x) subnet-match is does not respect 'value' attribute
Status: VERIFIED
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management (Show other bugs)
6.3.0
Unspecified Unspecified
unspecified Severity unspecified
: DR1
: EAP 6.4.0
Assigned To: Ivo Studensky
Petr Kremensky
:
Depends On:
Blocks: 1111578
  Show dependency treegraph
 
Reported: 2014-06-20 08:10 EDT by Ivo Studensky
Modified: 2018-03-06 15:38 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previous releases of JBoss EAP 6 carried a bug that prevented subnet-match from respecting the `value` attribute. In this release of the product, the issue has been resolved and the `value` attribute works as expected.
Story Points: ---
Clone Of:
: 1111578 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker WFLY-3478 Major Resolved subnet-match is completely broken 2016-08-30 02:51 EDT

  None (edit)
Description Ivo Studensky 2014-06-20 08:10:18 EDT
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) -------------------------------------------------------------------
Comment 2 JBoss JIRA Server 2014-06-26 04:30:55 EDT
Ivo Studensky <istudens@redhat.com> updated the status of jira WFLY-3478 to Reopened
Comment 3 Ivo Studensky 2014-06-26 04:34:33 EDT
PR sent:
https://github.com/jbossas/jboss-eap/pull/1484
Comment 4 JBoss JIRA Server 2014-06-27 00:58:18 EDT
Ivo Studensky <istudens@redhat.com> updated the status of jira WFLY-3478 to Resolved

Note You need to log in before you can comment on or make changes to this bug.