y - Net Developer

CHAPTER 12 ■ DEVELOPING PEER-TO-PEER APPLICATIONS WITH WCF 397ramrameshreddy.blog.comExtended payload (binary):Comment: aD????????Addresses: 169.254.2.2:28365192.168.1.73:28365[2001:0000:4136:e37a:2847:1735:a83d:dc55]%0:28365Extended payload (binary):We have two instances of QuickReturnTraderChat running, which you can see in the previousexample. We also have two network cards, one of which is connected to the Internet andthe other of which is on an internal network. The first network adapter (which is connected tothe Internet connection) has the IP address of 192.168.1.73 (this is NATed of course), and thelocal only is 169.254.2.2. Both are listening on port 28365.The other command of interest is traceroute, which resolved a peer with path tracing. Ifthe name is registered, then the result is quite similar to the resolve command used earlier, asshown in Listing 12-17.Listing 12-17. Known Peer Traceroutenetsh p2p pnrp peer>traceroute 0.quickreturntraderchat Global_Resolve started...Found:Addresses: 169.254.2.2:28365 tcp192.168.1.73:28365 tcp[2001:0000:4136:e37a:2847:1735:a83d:dc55]%0:28365tcpExtended payload (string):Extended payload (binary):Resolve Path:[2001:0000:4136:e37a:2847:1735:a83d:dc55]:3540, (0), (0)Accepted[2001:0000:4136:e37a:2847:1735:a83d:dc55]:3540, (0), (0)Accepted Final InquireHowever, on the other hand, if the peer is not registered, then you see more interestingbehavior, as shown in Listing 12-18. Note an invalid name (0.quickreturntraderchatwedontkow)was provided to mimic this behavior. Also, the listing has been abbreviated for clarity. The exactnumber of hops would vary on the size of your cloud.Listing 12-18. Unknown Peer Traceroutenetsh p2p pnrp peer>traceroute 0.quickreturntraderchatwedontkow Global_Resolve started...Not Found.Resolve Path:[2001:0000:4136:e37a:2847:1735:a83d:dc55]:3540, (0), (0)Accepted[2001:0000:4136:e37e:140b:26c5:affa:3034]:3540, (8), (31)Rejected (Dead end)ramrameshreddyramrameshreddy