JXTA cannot discover peers behind NATs?

Alan Zhang <[email protected]> Tue, 19 Dec 2006 17:58:29 -0800 (PST)
Newsgroups gmane.comp.java.jxta.user
Message-ID <[email protected]>
--0-11189167-1166579909=:36191
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

It seems JXTA cannot discover peers behind NATs and two peers both behind
NATs cannot connect to each other. I did a simple test by starting two jxta shell
in one machine with different PIDs and different tcp ports. I  diabled local 
multicasting to force the two peers to talk to each other via relay and
rendezvous. Using "rdvstatus" command and "relaystatus" command, I found
both peers could connect to a relay and a rendezvous, but they couldn't see
each other even when they were connected to a same rendezvous peer(i.e
 jxta-38). I also created a pipe adv in one peer and tried to find the adv in the
other peer but failed. I guess the relay peer might be a problem, because a 
edge peer behind NAT has to poll its relay peer for messages, if the edge peer
failed to get other peers' query messages from the relay peer,  it cannot answer
the query to uncover itself to other peers. Any insight? 

Thanks!

Alan
2006/12/20




 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
--0-11189167-1166579909=:36191
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

It seems JXTA cannot discover peers behind NATs and two peers both behind<br>NATs cannot connect to each other. I did a simple test by starting two jxta shell<br>in one machine with different PIDs and different tcp ports. I&nbsp; diabled local&nbsp;<br>multicasting to force the two peers to talk to each other via relay and<br>rendezvous. Using "rdvstatus" command and "relaystatus" command, I found<br>both peers could connect to a relay and a rendezvous, but they couldn't see<br>each other even when they were connected to a same rendezvous peer(i.e<br>&nbsp;jxta-38). I also created a pipe adv in one peer and tried to find the adv in the<br>other peer but failed. I guess the relay peer might be a problem, because a <br>edge peer behind NAT has to poll its relay peer for messages, if the edge peer<br>failed to get other peers' query messages from the relay peer,&nbsp; it cannot answer<br>th
 e query to uncover itself to other peers. Any insight?
 <br><br>Thanks!<br><br>Alan<br>2006/12/20<br><br><br><br><p>&#32;__________________________________________________<br>Do You Yahoo!?<br>Tired of spam?  Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com 
--0-11189167-1166579909=:36191--