Read only archive ; use https://github.com/JacORB/JacORB/issues for new issues
Bug 1030 - Two IP-address, one internal and one external registers internal IP to naming service, making the service inaccessible from out side
Summary: Two IP-address, one internal and one external registers internal IP to naming...
Status: RESOLVED FIXED
Alias: None
Product: JacORB
Classification: Unclassified
Component: Naming Service (show other bugs)
Version: 3.6
Hardware: Sun Solaris
: P5 critical
Assignee: Mailinglist to track bugs
URL:
Depends on:
Blocks:
 
Reported: 2016-04-25 07:42 UTC by alka singh
Modified: 2016-05-19 04:38 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description alka singh 2016-04-25 07:42:39 UTC 
I have system with two ip-ddresses one for external interface and another for internal interface. While binding to naming service it is some how using internal IP to bind. 

The same code base was working with, java6 and jacorb 3.5, it was binding to external IP. after upgrading to java8 and jacorb 3.6 code is using internal ip to bind. Is there any known bug related to this?
Comment 1 Nick Cross 2016-04-25 09:34:44 UTC 
There has been modifications to the ordering of network interfaces returned in the codebase. Would it be possible to test with the latest GIT codebase (https://github.com/JacORB/JacORB/) ?
Comment 2 alka singh 2016-04-29 06:39:55 UTC 
I will try to test with GIT codebase. How would this help me though?
Is there any way i can change the order of network interfaces?
Comment 3 Nick Cross 2016-05-19 04:38:04 UTC 
Discussed with Alka and problem has been solved in >= 3.7 codebase (i.e. current git head).