Jxta and Loopback Interface

Hi all,

as far as I know, Jxta embeds a mechanism for throwing away
loopback addresses (127.0.0.1) if some network card is
detected to be active in the system.

Maybe this feature causes a lot of connectivity issues,
while trying to run simple client/server examples on
a single development machine. I guess there could be
some management of loopback addrs that is not completely
consistent across the overall Jxta components.

Is there any simple way to bypass such mechanisms, by
proper configuration of the machine ? I'm trying Jxta
on a Linux FC2 laptop, if this is useful at all, and
I found that no issues arise if trying with 2 distinct computers,
but everytime I try on a single machine, I run into a
real connectivity nightmare.... which doesn't seem to be
very compatible with the Jxta philosophy.

Many thanks in advance,

  tom.