Need of complete network address isolation.

[BHa77 <br...@gmail.com>]

Hi,

>From karaf 2.3.1 - that bundles with smx 5.0.0 - there is a very useful
property named "rmiRegistryHost" that binds socket to
${rmiRegistryHost}:${rmiRegistryPort}, but it's only half the way to fit one
of my production requirements : "no tcp port wildcarding".

This listener is OK :
*tcp        0      0 ::ffff:192.168.200.1:1099       :::*                       
LISTEN*

However I found no way to do the same with rmiServer,
so this one is not correct for my use :
*tcp        0      0 :::44444                    :::*                       
LISTEN* 

My goal is to have :
*tcp        0      0 ::ffff:192.168.200.1:44444                    :::*                       
LISTEN* 

It has to be done in some SocketFactory but I don't know karaf sources for
now...
If someone has solved this,... Ideas welcome!!
Thanks




--
View this message in context: http://karaf.922171.n3.nabble.com/Need-of-complete-network-address-isolation-tp4028980.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Need of complete network address isolation.

[Freeman Fang <fr...@gmail.com>]

Hi,

Yes, this is a known issue and already get resolved, KARAF-2291[1] tracked it, next Karaf 2.3.2 would pick up this fix.

And you can find the commit change from [1] also, where you can build a jar with the fix yourself

[1]https://issues.apache.org/jira/browse/KARAF-2291
－－－－－－－－－－－－－
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋

www.camelone.org : The open source integration conference: 

On 2013-6-8, at 下午7:03, BHa77 wrote:

> Hi,
> 
> From karaf 2.3.1 - that bundles with smx 5.0.0 - there is a very useful
> property named "rmiRegistryHost" that binds socket to
> ${rmiRegistryHost}:${rmiRegistryPort}, but it's only half the way to fit one
> of my production requirements : "no tcp port wildcarding".
> 
> This listener is OK :
> *tcp        0      0 ::ffff:192.168.200.1:1099       :::*                       
> LISTEN*
> 
> However I found no way to do the same with rmiServer,
> so this one is not correct for my use :
> *tcp        0      0 :::44444                    :::*                       
> LISTEN* 
> 
> My goal is to have :
> *tcp        0      0 ::ffff:192.168.200.1:44444                    :::*                       
> LISTEN* 
> 
> It has to be done in some SocketFactory but I don't know karaf sources for
> now...
> If someone has solved this,... Ideas welcome!!
> Thanks
> 
> 
> 
> 
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Need-of-complete-network-address-isolation-tp4028980.html
> Sent from the Karaf - User mailing list archive at Nabble.com.