Skip to main content

JXSE Rdv/Rly

1 reply [Last post]
galato
Offline
Joined: 2007-07-06
Points: 0

Hi all,

I know this is very basic but I haven't looked at this in a few years (since they always worked) and now with the NAT issue reappearing when I upgraded some of my peers to 2.5 I need to revisit. I have a public RDV running on the IP shown below and peers behind NAT trying to connect to it - they find it but once they try to establish jxtabidi pipes between them they stall. I show the problem right after the code - this is a very small chunk of code that uses seeded methods to connect to the RDVRLY. Does this seem correct or is there something missing?? Thanks very much

if (args[0].equals("netrdv")) {
config.setPeerID((PeerID) IDFactory.fromURI(new URI(
"urn:jxta:uuid-59616261646162614E50472050325033DE6DFC0D22794E22B072C7A99881537703")
));
onfig.setMode(NetworkConfigurator.RDV_NODE | NetworkConfigurator.RELAY_NODE);

// config.setHttpPort(9700);
// config.setTcpPort(9701);
}
else if (args[0].equals("edge")) {
config.setDescription("Created by ConsumerPeer");
config.setMode(NetworkConfigurator.EDGE_NODE);

try {
config.addSeedRendezvous(new URI("http://129.12.58.111:9700"));
config.addSeedRelay(new URI("http://129.12.58.111:9700"));
} catch ...etc etc.

Do I need to set the seeding for the Relay to use tcp and 9701 or is the problem that i need to uncomment again the fact that I use those ports. Either way, both peers do find the RDv but once they try to setup the pipes to communicate they give the following - and they stall without connecting properly. Also where did the IP addr 71.111.181.175:50488 shown below come from?? Don't have such an address in my network here. Thanks for any feedback on this

[java] Jun 21, 2009 2:07:32 AM net.jxta.impl.endpoint.tcp.TcpMessenger
[java] INFO: Creating new TCP Connection to : tcp://192.168.1.43:9701 / 192.168.1.43:9701
[java] Jun 21, 2009 2:07:35 AM net.jxta.impl.endpoint.tcp.TcpMessenger
[java] INFO: Connection from 71.174.111.175:50486
[java] Jun 21, 2009 2:07:44 AM net.jxta.impl.endpoint.tcp.TcpMessenger closeImpl
[java] INFO: Normal close (open 1020032ms) of socket to : tcp://192.168.1.43:9701 / 71.111.181.175:50199
[java] Jun 21, 2009 2:07:44 AM net.jxta.impl.endpoint.tcp.TcpMessenger closeImpl
[java] INFO: Normal close (open 960031ms) of socket to : tcp://192.168.1.43:9701 / 71.111.181.175:50209
[java] Failed to connect the server pipe - trying again ...
[java] Jun 21, 2009 2:07:47 AM net.jxta.impl.pipe.InputPipeImpl
[java] INFO: Creating InputPipe for urn:jxta:uuid-59616261646162614E504720503250331FE30EC6E88747C18B61B4F6AC04728D04 of type JxtaUnicast with listener
[java] Jun 21, 2009 2:07:47 AM net.jxta.impl.pipe.NonBlockingOutputPipe startServiceThread
[java] INFO: Thread start : Worker Thread for NonBlockingOutputPipe : urn:jxta:uuid-1924FEA9399844D29BF18E6B65ECBB603B06C747B3984784B4D3A60CD2C1BC7404
[java] worker state : SENDMESSAGES queue closed : false number in queue : 1 number queued : 3 number dequeued : 2
[java] Jun 21, 2009 2:07:48 AM net.jxta.impl.pipe.NonBlockingOutputPipe
[java] INFO: Constructing for urn:jxta:uuid-1924FEA9399844D29BF18E6B65ECBB603B06C747B3984784B4D3A60CD2C1BC7404
[java] Jun 21, 2009 2:07:48 AM net.jxta.impl.pipe.NonBlockingOutputPipe startServiceThread
[java] INFO: Thread start : Worker Thread for NonBlockingOutputPipe : urn:jxta:uuid-1924FEA9399844D29BF18E6B65ECBB603B06C747B3984784B4D3A60CD2C1BC7404
[java] worker state : ACQUIREMESSENGER queue closed : false number in queue : 0 number queued : 0 number dequeued : 0
[java] Jun 21, 2009 2:07:48 AM net.jxta.impl.pipe.NonBlockingOutputPipe close
[java] INFO: Closing for urn:jxta:uuid-1924FEA9399844D29BF18E6B65ECBB603B06C747B3984784B4D3A60CD2C1BC7404
[java] Jun 21, 2009 2:07:48 AM net.jxta.impl.pipe.NonBlockingOutputPipe run
[java] INFO: Thread exit : Worker Thread for NonBlockingOutputPipe : urn:jxta:uuid-1924FEA9399844D29BF18E6B65ECBB603B06C747B3984784B4D3A60CD2C1BC7404
[java] worker state : CLOSED queue closed : true number in queue : 0 number queued : 0 number dequeued : 0
[java] Jun 21, 2009 2:07:48 AM net.jxta.impl.endpoint.tcp.TcpMessenger
[java] INFO: Connection from 71.111.181.175:50488
[java] Jun 21, 2009 2:07:48 AM net.jxta.impl.endpoint.tcp.TcpMessenger
[java] INFO: Creating new TCP Connection to : tcp://192.168.1.43:9701 / 192.168.1.43:9701
[java] Jun 21, 2009 2:07:52 AM net.jxta.impl.endpoint.tcp.TcpMessenger closeImpl
[java] INFO: Normal close (open 960032ms) of socket to : tcp://192.168.1.43:9701 / 71.174.181.175:50210
^Xmaple.ece.neu.edu [P2PA] %

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
galato
Offline
Joined: 2007-07-06
Points: 0

An update on this - I tested the code I showed in the original posting of this thread on two Linux boxes not behind NAT/Firewalls and everything works fine. SO it seems to me that either I am not setting up the relay correctly (what I show in the code) or JXSE is still having issues with NAT confingurations. Any ideas?

Mike - I will post this also on the other thread, the code I showed that worked in 2.4.1 for getting the server Pipe ID I just verified does not work in 2.5 - that's why Mohamed gave me the other code that now also shows it does not work. Any ideas?

Thanks very much