Re: JXTA cannot discover peers behind NATs?
Alan Zhang <[email protected]> Wed, 20 Dec 2006 18:56:27 -0800 (PST)
| Newsgroups | gmane.comp.java.jxta.user |
|---|---|
| Message-ID | <[email protected]> |
--0-457311818-1166669787=:75539
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
My test is quite simple. After starting jxta shell, I use "peers -r" and "peers -p peerid" to find my peers, like below:
JXTA>relaystatus
Active Relay Servers for 'relay' :
jxta-38
JXTA>rdvstatus
Rendezvous Status:
__________________
Current configuration : EDGE
"asd2" A p t [314/291]
Peer View :
"jxta-38" A P t [283/219]
Rendezvous Connections :
jxta-38 C : 1028093 / 728093
Rendezvous Disconnections :
[None]
JXTA>peers -r
# peers - peer discovery message sent
JXTA>peers
peer0: name = asd2
peer1: name = jxta-38
JXTA>
JXTA>peers -p urn:jxta:uuid-59616261646162614A787461503250332431C5F2F49143D7BE5B862429E5AC9D03
# peers - peer discovery message sent
JXTA>peers
peer0: name = asd2
peer1: name = jxta-38
JXTA>
For advertisement, I use "search -r" and "search -p peerid" commands, then "cat" each member in the advertisement list returned by the "search" command.
Alan
"Mike [bondolo] Duigou" <[email protected]> wrote: Alan Zhang wrote:
> 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).
How do you determine whether they can "see each other"? JXTA Discovery
is not a suitable way to enumerate the peers connected to the network as
it is not intended to provide exhaustive results. Did you try searching
for the specific peer and/or attempt to connect to the peer?
I also created a pipe adv in one peer and tried to find the
> adv in the
> other peer but failed.
This may be the same problem as the peer search. Were you searching for
the specific pipe advertisement or searching for all pipe advertisements
and assuming that the pipe advertisement one of your peers created would
be in the result returned?
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--0-457311818-1166669787=:75539
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
My test is quite simple. After starting jxta shell, I use "peers -r" and "peers -p peerid" to find my peers, like below: <br><br>JXTA>relaystatus<br>Active Relay Servers for 'relay' : <br> jxta-38<br>JXTA>rdvstatus<br> <br>Rendezvous Status: <br>__________________<br> <br>Current configuration : EDGE<br> "asd2" A p t [314/291]<br> <br>Peer View : <br> "jxta-38" A P t [283/219]<br> <br>Rendezvous Connections :<br> jxta-38 C : 1028093 / 728093<br> <br>Rendezvous Disconnections :<br> [None]<br><br>JXTA>peers -r<br># peers - peer discovery message sent<br>JXTA>peers<br>peer0: name = asd2<br>peer1: name = jxta-38<br>JXTA><br>JXTA>peers -p urn:jxta:uuid-59616261646162614A787461503250332431C5F2F49143D7BE5B862429E5AC9D03<br># pee
rs - peer discovery message sent<br>JXTA>peers<br>peer0: name = asd2<br>peer1: name =
jxta-38<br>JXTA><br><br>For advertisement, I use "search -r" and "search -p peerid" commands, then "cat" each member in the advertisement list returned by the "search" command. <br><br>Alan<br><br><br><b><i>"Mike [bondolo] Duigou" <[email protected]></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Alan Zhang wrote:<br>> 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 <br>> jxta shell<br>> in one machine with different PIDs and different tcp ports. I diabled <br>> local <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 rendezv
ous, but they couldn't see<br>> each other even when they were connected to a same
rendezvous peer(i.e<br>> jxta-38). <br><br>How do you determine whether they can "see each other"? JXTA Discovery <br>is not a suitable way to enumerate the peers connected to the network as <br>it is not intended to provide exhaustive results. Did you try searching <br>for the specific peer and/or attempt to connect to the peer?<br><br>I also created a pipe adv in one peer and tried to find the<br>> adv in the<br>> other peer but failed. <br><br>This may be the same problem as the peer search. Were you searching for <br>the specific pipe advertisement or searching for all pipe advertisements <br>and assuming that the pipe advertisement one of your peers created would <br>be in the result returned?<br><br>Mike<br><br>---------------------------------------------------------------------<br>To unsubscribe, e-mail: [email protected]<br>For additional commands, e-mail:
[email protected]<br><br></blockquote><br><p> __________________________________________________<br>Do You Yahoo!?<br>Tired of spam? Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com
--0-457311818-1166669787=:75539--