API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Mar 29th, 2020
2,269
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 47.52 KB | None | 0 0
raw download clone embed print report
  1. [3/29/2020 3:36:57 PM] Launcher scene starting.
  2. [3/29/2020 3:37:15 PM] Resolving named connection to server. [Copernicus219]
  3. [3/29/2020 3:37:15 PM] Attempting resolved connection to server. [68.183.117.123:62119]
  4. [3/29/2020 3:37:15 PM] Noble Connect [18664]: Found host candidate: HOST (192.168.1.200:50101)
  5. [3/29/2020 3:37:15 PM] Noble Connect [18664]: Found host candidate: HOST (192.168.73.1:50102)
  6. [3/29/2020 3:37:15 PM] Noble Connect [18664]: Found host candidate: HOST (192.168.56.1:50103)
  7. [3/29/2020 3:37:15 PM] Noble Connect [18664]: Found host candidate: HOST (192.168.57.1:50104)
  8. [3/29/2020 3:37:15 PM] Noble Connect [18664]: Found host candidate: HOST (192.168.99.1:50105)
  9. [3/29/2020 3:37:15 PM] Noble Connect [18664]: Found host candidate: HOST (169.254.44.238:50106)
  10. [3/29/2020 3:37:15 PM] Noble Connect [18664]: Found host candidate: HOST (169.254.50.150:50107)
  11. [3/29/2020 3:37:15 PM] Noble Connect [18664]: Found host candidate: HOST (169.254.176.12:50108)
  12. [3/29/2020 3:37:15 PM] Noble Connect [18664]: Found host candidate: HOST (127.0.0.1:50109)
  13. [3/29/2020 3:37:15 PM] Noble Connect [18673]: Sending ALLOCATE REQUEST [d10a8101f719637eaa4489b3] from 192.168.1.200:50101 to 68.183.117.123:3478
  14. [3/29/2020 3:37:15 PM] Noble Connect [18700]: Sending ALLOCATE REQUEST [29d088d3da951151bf4ed02e] from 192.168.73.1:50102 to 68.183.117.123:3478
  15. [3/29/2020 3:37:15 PM] Noble Connect [18704]: Handle response from 68.183.117.123:3478 at 192.168.1.200:50101
  16. [3/29/2020 3:37:15 PM] Noble Connect [18705]: Received ALLOCATE ERROR RESPONSE [d10a8101f719637eaa4489b3] (401): Unauthorized
  17. [3/29/2020 3:37:15 PM] Noble Connect [18710]: Sending ALLOCATE REQUEST [63a7dccf8c6b6999e293ea93] from 192.168.1.200:50101 to 68.183.117.123:3478
  18. [3/29/2020 3:37:15 PM] Noble Connect [18720]: Sending ALLOCATE REQUEST [ee5a0e5e49d4a9a92b37bb19] from 192.168.56.1:50103 to 68.183.117.123:3478
  19. [3/29/2020 3:37:15 PM] Noble Connect [18727]: Handle response from 68.183.117.123:3478 at 192.168.1.200:50101
  20. [3/29/2020 3:37:15 PM] Noble Connect [18727]: Received ALLOCATE SUCCESS RESPONSE [63a7dccf8c6b6999e293ea93] from 68.183.117.123:3478 at 192.168.1.200:50101
  21. [3/29/2020 3:37:15 PM] Noble Connect [18740]: Sending ALLOCATE REQUEST [00f11f3c8df360c5ae258551] from 192.168.57.1:50104 to 68.183.117.123:3478
  22. [3/29/2020 3:37:15 PM] Noble Connect [18760]: Sending ALLOCATE REQUEST [be93747142c5503d40b220de] from 192.168.99.1:50105 to 68.183.117.123:3478
  23. [3/29/2020 3:37:15 PM] Noble Connect [18780]: Sending ALLOCATE REQUEST [f6f415acf590db68a7fa671d] from 169.254.44.238:50106 to 68.183.117.123:3478
  24. [3/29/2020 3:37:15 PM] Noble Connect [18802]: Sending ALLOCATE REQUEST [2c9bc7d4ebef70e47e77d868] from 169.254.50.150:50107 to 68.183.117.123:3478
  25. [3/29/2020 3:37:16 PM] Noble Connect [18822]: Sending ALLOCATE REQUEST [d0ef80cf58464de5511ceb37] from 169.254.176.12:50108 to 68.183.117.123:3478
  26. [3/29/2020 3:37:16 PM] Noble Connect [18842]: Sending ALLOCATE REQUEST [8c863675c8877c101e80c16f] from 127.0.0.1:50109 to 68.183.117.123:3478
  27. [3/29/2020 3:37:16 PM] Noble Connect [18901]: Sending ALLOCATE REQUEST [29d088d3da951151bf4ed02e] from 192.168.73.1:50102 to 68.183.117.123:3478
  28. [3/29/2020 3:37:16 PM] Noble Connect [18920]: Sending ALLOCATE REQUEST [ee5a0e5e49d4a9a92b37bb19] from 192.168.56.1:50103 to 68.183.117.123:3478
  29. [3/29/2020 3:37:16 PM] Noble Connect [18943]: Sending ALLOCATE REQUEST [00f11f3c8df360c5ae258551] from 192.168.57.1:50104 to 68.183.117.123:3478
  30. [3/29/2020 3:37:16 PM] Noble Connect [18960]: Sending ALLOCATE REQUEST [be93747142c5503d40b220de] from 192.168.99.1:50105 to 68.183.117.123:3478
  31. [3/29/2020 3:37:16 PM] Noble Connect [18980]: Sending ALLOCATE REQUEST [f6f415acf590db68a7fa671d] from 169.254.44.238:50106 to 68.183.117.123:3478
  32. [3/29/2020 3:37:16 PM] Noble Connect [19002]: Sending ALLOCATE REQUEST [2c9bc7d4ebef70e47e77d868] from 169.254.50.150:50107 to 68.183.117.123:3478
  33. [3/29/2020 3:37:16 PM] Noble Connect [19022]: Sending ALLOCATE REQUEST [d0ef80cf58464de5511ceb37] from 169.254.176.12:50108 to 68.183.117.123:3478
  34. [3/29/2020 3:37:16 PM] Noble Connect [19042]: Sending ALLOCATE REQUEST [8c863675c8877c101e80c16f] from 127.0.0.1:50109 to 68.183.117.123:3478
  35. [3/29/2020 3:37:16 PM] Noble Connect [19301]: Sending ALLOCATE REQUEST [29d088d3da951151bf4ed02e] from 192.168.73.1:50102 to 68.183.117.123:3478
  36. [3/29/2020 3:37:16 PM] Noble Connect [19320]: Sending ALLOCATE REQUEST [ee5a0e5e49d4a9a92b37bb19] from 192.168.56.1:50103 to 68.183.117.123:3478
  37. [3/29/2020 3:37:16 PM] Noble Connect [19343]: Sending ALLOCATE REQUEST [00f11f3c8df360c5ae258551] from 192.168.57.1:50104 to 68.183.117.123:3478
  38. [3/29/2020 3:37:16 PM] Noble Connect [19360]: Sending ALLOCATE REQUEST [be93747142c5503d40b220de] from 192.168.99.1:50105 to 68.183.117.123:3478
  39. [3/29/2020 3:37:16 PM] Noble Connect [19380]: Sending ALLOCATE REQUEST [f6f415acf590db68a7fa671d] from 169.254.44.238:50106 to 68.183.117.123:3478
  40. [3/29/2020 3:37:16 PM] Noble Connect [19402]: Sending ALLOCATE REQUEST [2c9bc7d4ebef70e47e77d868] from 169.254.50.150:50107 to 68.183.117.123:3478
  41. [3/29/2020 3:37:16 PM] Noble Connect [19424]: Sending ALLOCATE REQUEST [d0ef80cf58464de5511ceb37] from 169.254.176.12:50108 to 68.183.117.123:3478
  42. [3/29/2020 3:37:16 PM] Noble Connect [19442]: Sending ALLOCATE REQUEST [8c863675c8877c101e80c16f] from 127.0.0.1:50109 to 68.183.117.123:3478
  43. [3/29/2020 3:37:17 PM] Noble Connect [20101]: Sending ALLOCATE REQUEST [29d088d3da951151bf4ed02e] from 192.168.73.1:50102 to 68.183.117.123:3478
  44. [3/29/2020 3:37:17 PM] Noble Connect [20120]: Sending ALLOCATE REQUEST [ee5a0e5e49d4a9a92b37bb19] from 192.168.56.1:50103 to 68.183.117.123:3478
  45. [3/29/2020 3:37:17 PM] Noble Connect [20143]: Sending ALLOCATE REQUEST [00f11f3c8df360c5ae258551] from 192.168.57.1:50104 to 68.183.117.123:3478
  46. [3/29/2020 3:37:17 PM] Noble Connect [20160]: Sending ALLOCATE REQUEST [be93747142c5503d40b220de] from 192.168.99.1:50105 to 68.183.117.123:3478
  47. [3/29/2020 3:37:17 PM] Noble Connect [20180]: Sending ALLOCATE REQUEST [f6f415acf590db68a7fa671d] from 169.254.44.238:50106 to 68.183.117.123:3478
  48. [3/29/2020 3:37:17 PM] Noble Connect [20202]: Sending ALLOCATE REQUEST [2c9bc7d4ebef70e47e77d868] from 169.254.50.150:50107 to 68.183.117.123:3478
  49. [3/29/2020 3:37:17 PM] Noble Connect [20224]: Sending ALLOCATE REQUEST [d0ef80cf58464de5511ceb37] from 169.254.176.12:50108 to 68.183.117.123:3478
  50. [3/29/2020 3:37:17 PM] Noble Connect [20242]: Sending ALLOCATE REQUEST [8c863675c8877c101e80c16f] from 127.0.0.1:50109 to 68.183.117.123:3478
  51. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: HOST (192.168.1.200:50101)
  52. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: HOST (192.168.73.1:50102)
  53. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: HOST (192.168.56.1:50103)
  54. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: HOST (192.168.57.1:50104)
  55. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: HOST (192.168.99.1:50105)
  56. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: HOST (169.254.44.238:50106)
  57. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: HOST (169.254.50.150:50107)
  58. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: HOST (169.254.176.12:50108)
  59. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: HOST (127.0.0.1:50109)
  60. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: RELAYED (68.183.117.123:52504 => 192.168.1.200:50101)
  61. [3/29/2020 3:37:19 PM] Noble Connect [21847]: Found candidate: SERVER_REFLEXIVE (68.67.247.66:50101 => 192.168.1.200:50101)
  62. [3/29/2020 3:37:19 PM] Noble Connect [21860]: Sending CREATE_PERMISSION REQUEST [69a8d6ec7c1584fd934d8ccb] from 192.168.1.200:50101 to 68.183.117.123:3478
  63. [3/29/2020 3:37:19 PM] Noble Connect [21876]: Handle response from 68.183.117.123:3478 at 192.168.1.200:50101
  64. [3/29/2020 3:37:19 PM] Noble Connect [21876]: Received CREATE_PERMISSION SUCCESS RESPONSE [69a8d6ec7c1584fd934d8ccb] from 68.183.117.123:3478 at 192.168.1.200:50101
  65. [3/29/2020 3:37:19 PM] Noble Connect [21876]: Sending CREATE_PERMISSION REQUEST [2bf7d522097118ee62363d33] from 192.168.1.200:50101 to 68.183.117.123:3478
  66. [3/29/2020 3:37:19 PM] Noble Connect [21892]: Handle response from 68.183.117.123:3478 at 192.168.1.200:50101
  67. [3/29/2020 3:37:19 PM] Noble Connect [21892]: Received CREATE_PERMISSION SUCCESS RESPONSE [2bf7d522097118ee62363d33] from 68.183.117.123:3478 at 192.168.1.200:50101
  68. [3/29/2020 3:37:19 PM] Noble Connect [21897]: Sending SEND INDICATION [115bfa3c1bec33495a467e12] from 192.168.1.200:50101 to 68.183.117.123:3478
  69. [3/29/2020 3:37:19 PM] Noble Connect [21957]: Sending CHANNEL_BIND REQUEST [fa76813b6edff93702a6cc4d] from 192.168.1.200:50101 to 68.183.117.123:3478
  70. [3/29/2020 3:37:19 PM] Noble Connect [21957]: Sending CHANNEL_BIND REQUEST [a408fe158d63688d01922e13] from 192.168.1.200:50101 to 68.183.117.123:3478
  71. [3/29/2020 3:37:19 PM] Noble Connect [21957]: Sending CHANNEL_BIND REQUEST [759aee6e8de740c30289aa39] from 192.168.1.200:50101 to 68.183.117.123:3478
  72. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Sending CHANNEL_BIND REQUEST [6059b73333c755a4c31b5738] from 192.168.1.200:50101 to 68.183.117.123:3478
  73. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.1.200:50101) => HOST (192.168.1.69:59148)
  74. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (127.0.0.1:50109) => HOST (127.0.0.1:59149)
  75. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (127.0.0.1:50109) => HOST (192.168.1.69:59148)
  76. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.176.12:50108) => HOST (127.0.0.1:59149)
  77. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.176.12:50108) => HOST (192.168.1.69:59148)
  78. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.50.150:50107) => HOST (127.0.0.1:59149)
  79. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.50.150:50107) => HOST (192.168.1.69:59148)
  80. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.44.238:50106) => HOST (192.168.1.69:59148)
  81. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.99.1:50105) => HOST (127.0.0.1:59149)
  82. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.99.1:50105) => HOST (192.168.1.69:59148)
  83. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.57.1:50104) => HOST (127.0.0.1:59149)
  84. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.57.1:50104) => HOST (192.168.1.69:59148)
  85. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.44.238:50106) => HOST (127.0.0.1:59149)
  86. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.73.1:50102) => HOST (192.168.1.69:59148)
  87. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.56.1:50103) => HOST (127.0.0.1:59149)
  88. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.56.1:50103) => HOST (192.168.1.69:59148)
  89. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.1.200:50101) => HOST (127.0.0.1:59149)
  90. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.73.1:50102) => HOST (127.0.0.1:59149)
  91. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.57.1:50104) => SERVER_REFLEXIVE (67.38.19.212:59148)
  92. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.99.1:50105) => SERVER_REFLEXIVE (67.38.19.212:59148)
  93. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.73.1:50102) => SERVER_REFLEXIVE (67.38.19.212:59148)
  94. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (127.0.0.1:50109) => SERVER_REFLEXIVE (67.38.19.212:59148)
  95. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.44.238:50106) => SERVER_REFLEXIVE (67.38.19.212:59148)
  96. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.176.12:50108) => SERVER_REFLEXIVE (67.38.19.212:59148)
  97. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.1.200:50101) => SERVER_REFLEXIVE (67.38.19.212:59148)
  98. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.50.150:50107) => SERVER_REFLEXIVE (67.38.19.212:59148)
  99. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.56.1:50103) => SERVER_REFLEXIVE (67.38.19.212:59148)
  100. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (169.254.176.12:50108) => RELAYED (68.183.117.123:62119)
  101. [3/29/2020 3:37:19 PM] Noble Connect [21958]: Local Candidate: HOST (192.168.73.1:50102) => RELAYED (68.183.117.123:62119)
  102. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: HOST (192.168.1.200:50101) => RELAYED (68.183.117.123:62119)
  103. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: HOST (169.254.44.238:50106) => RELAYED (68.183.117.123:62119)
  104. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: HOST (127.0.0.1:50109) => RELAYED (68.183.117.123:62119)
  105. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: HOST (192.168.99.1:50105) => RELAYED (68.183.117.123:62119)
  106. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: HOST (192.168.57.1:50104) => RELAYED (68.183.117.123:62119)
  107. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: HOST (169.254.50.150:50107) => RELAYED (68.183.117.123:62119)
  108. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: HOST (192.168.56.1:50103) => RELAYED (68.183.117.123:62119)
  109. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: RELAYED (68.183.117.123:52504 => 192.168.1.200:50101) => HOST (192.168.1.69:59148)
  110. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: RELAYED (68.183.117.123:52504 => 192.168.1.200:50101) => HOST (127.0.0.1:59149)
  111. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: RELAYED (68.183.117.123:52504 => 192.168.1.200:50101) => SERVER_REFLEXIVE (67.38.19.212:59148)
  112. [3/29/2020 3:37:19 PM] Noble Connect [21959]: Local Candidate: RELAYED (68.183.117.123:52504 => 192.168.1.200:50101) => RELAYED (68.183.117.123:62119)
  113. [3/29/2020 3:37:19 PM] Noble Connect [21973]: Handle response from 68.183.117.123:3478 at 192.168.1.200:50101
  114. [3/29/2020 3:37:19 PM] Noble Connect [21973]: Received CHANNEL_BIND SUCCESS RESPONSE [fa76813b6edff93702a6cc4d] from 68.183.117.123:3478 at 192.168.1.200:50101
  115. [3/29/2020 3:37:19 PM] Noble Connect [21974]: Handle response from 68.183.117.123:3478 at 192.168.1.200:50101
  116. [3/29/2020 3:37:19 PM] Noble Connect [21974]: Received CHANNEL_BIND SUCCESS RESPONSE [a408fe158d63688d01922e13] from 68.183.117.123:3478 at 192.168.1.200:50101
  117. [3/29/2020 3:37:19 PM] Noble Connect [21974]: Handle response from 68.183.117.123:3478 at 192.168.1.200:50101
  118. [3/29/2020 3:37:19 PM] Noble Connect [21974]: Received CHANNEL_BIND SUCCESS RESPONSE [759aee6e8de740c30289aa39] from 68.183.117.123:3478 at 192.168.1.200:50101
  119. [3/29/2020 3:37:19 PM] Noble Connect [21974]: Handle response from 68.183.117.123:3478 at 192.168.1.200:50101
  120. [3/29/2020 3:37:19 PM] Noble Connect [21974]: Received CHANNEL_BIND SUCCESS RESPONSE [6059b73333c755a4c31b5738] from 68.183.117.123:3478 at 192.168.1.200:50101
  121. [3/29/2020 3:37:19 PM] Noble Connect [21981]: Sending BIND REQUEST [6694d631d2872cfc911967bc] from 192.168.1.200:50101 to 192.168.1.69:59148
  122. [3/29/2020 3:37:19 PM] Noble Connect [21999]: Sending BIND REQUEST [3fa6764ebc909e736c98153e] from 127.0.0.1:50109 to 127.0.0.1:59149
  123. [3/29/2020 3:37:19 PM] Noble Connect [22019]: Sending BIND REQUEST [714b128e6f93ccbc2d2c893d] from 127.0.0.1:50109 to 192.168.1.69:59148
  124. [3/29/2020 3:37:19 PM] Noble Connect [22039]: Sending BIND REQUEST [8fede27ef16608a779fbf725] from 169.254.176.12:50108 to 127.0.0.1:59149
  125. [3/29/2020 3:37:19 PM] Noble Connect [22059]: Sending BIND REQUEST [9e34da616da5b4675906c525] from 169.254.176.12:50108 to 192.168.1.69:59148
  126. [3/29/2020 3:37:19 PM] Noble Connect [22079]: Sending BIND REQUEST [2485a6d8d924fae7fa1e17bc] from 169.254.50.150:50107 to 127.0.0.1:59149
  127. [3/29/2020 3:37:19 PM] Noble Connect [22099]: Sending BIND REQUEST [4a421b04079bf42458186c90] from 169.254.50.150:50107 to 192.168.1.69:59148
  128. [3/29/2020 3:37:19 PM] Noble Connect [22119]: Sending BIND REQUEST [17b939a3022df9cda91c969b] from 169.254.44.238:50106 to 192.168.1.69:59148
  129. [3/29/2020 3:37:19 PM] Noble Connect [22139]: Sending BIND REQUEST [f1834255ed6747f02d34190d] from 192.168.99.1:50105 to 127.0.0.1:59149
  130. [3/29/2020 3:37:19 PM] Noble Connect [22159]: Sending BIND REQUEST [d4168ee93d021c05cbc9bd01] from 192.168.99.1:50105 to 192.168.1.69:59148
  131. [3/29/2020 3:37:19 PM] Noble Connect [22179]: Sending BIND REQUEST [19b1192729c5a3bdf267b033] from 192.168.57.1:50104 to 127.0.0.1:59149
  132. [3/29/2020 3:37:19 PM] Noble Connect [22181]: Sending BIND REQUEST [6694d631d2872cfc911967bc] from 192.168.1.200:50101 to 192.168.1.69:59148
  133. [3/29/2020 3:37:19 PM] Noble Connect [22199]: Sending BIND REQUEST [3fa6764ebc909e736c98153e] from 127.0.0.1:50109 to 127.0.0.1:59149
  134. [3/29/2020 3:37:19 PM] Noble Connect [22199]: Sending BIND REQUEST [18990690636edbe4e068e633] from 192.168.57.1:50104 to 192.168.1.69:59148
  135. [3/29/2020 3:37:19 PM] Noble Connect [22219]: Sending BIND REQUEST [714b128e6f93ccbc2d2c893d] from 127.0.0.1:50109 to 192.168.1.69:59148
  136. [3/29/2020 3:37:19 PM] Noble Connect [22219]: Sending BIND REQUEST [ee5eb37f9d651b21f387cc15] from 169.254.44.238:50106 to 127.0.0.1:59149
  137. [3/29/2020 3:37:19 PM] Noble Connect [22239]: Sending BIND REQUEST [8fede27ef16608a779fbf725] from 169.254.176.12:50108 to 127.0.0.1:59149
  138. [3/29/2020 3:37:19 PM] Noble Connect [22239]: Sending BIND REQUEST [c7b391c23962e16e633bffdb] from 192.168.73.1:50102 to 192.168.1.69:59148
  139. [3/29/2020 3:37:19 PM] Noble Connect [22259]: Sending BIND REQUEST [9e34da616da5b4675906c525] from 169.254.176.12:50108 to 192.168.1.69:59148
  140. [3/29/2020 3:37:19 PM] Noble Connect [22259]: Sending BIND REQUEST [3db7b035716f447d73eebbed] from 192.168.56.1:50103 to 127.0.0.1:59149
  141. [3/29/2020 3:37:19 PM] Noble Connect [22282]: Sending BIND REQUEST [2485a6d8d924fae7fa1e17bc] from 169.254.50.150:50107 to 127.0.0.1:59149
  142. [3/29/2020 3:37:19 PM] Noble Connect [22282]: Sending BIND REQUEST [d7d56d384e0d229fdf39a042] from 192.168.56.1:50103 to 192.168.1.69:59148
  143. [3/29/2020 3:37:19 PM] Noble Connect [22299]: Sending BIND REQUEST [4a421b04079bf42458186c90] from 169.254.50.150:50107 to 192.168.1.69:59148
  144. [3/29/2020 3:37:19 PM] Noble Connect [22302]: Sending BIND REQUEST [ac5ada5077c713ef1e30e967] from 192.168.1.200:50101 to 127.0.0.1:59149
  145. [3/29/2020 3:37:19 PM] Noble Connect [22319]: Sending BIND REQUEST [17b939a3022df9cda91c969b] from 169.254.44.238:50106 to 192.168.1.69:59148
  146. [3/29/2020 3:37:19 PM] Noble Connect [22322]: Sending BIND REQUEST [09fa58ee45ddf90f6ca8bff3] from 192.168.73.1:50102 to 127.0.0.1:59149
  147. [3/29/2020 3:37:19 PM] Noble Connect [22339]: Sending BIND REQUEST [f1834255ed6747f02d34190d] from 192.168.99.1:50105 to 127.0.0.1:59149
  148. [3/29/2020 3:37:19 PM] Noble Connect [22342]: Sending BIND REQUEST [9d3924af2afede1401b7ccc3] from 192.168.57.1:50104 to 67.38.19.212:59148
  149. [3/29/2020 3:37:19 PM] Noble Connect [22359]: Sending BIND REQUEST [d4168ee93d021c05cbc9bd01] from 192.168.99.1:50105 to 192.168.1.69:59148
  150. [3/29/2020 3:37:19 PM] Noble Connect [22362]: Sending BIND REQUEST [9a9e2b4727f9e7fb7b7d9ca7] from 192.168.99.1:50105 to 67.38.19.212:59148
  151. [3/29/2020 3:37:19 PM] Noble Connect [22379]: Sending BIND REQUEST [19b1192729c5a3bdf267b033] from 192.168.57.1:50104 to 127.0.0.1:59149
  152. [3/29/2020 3:37:19 PM] Noble Connect [22382]: Sending BIND REQUEST [63458437dc7049c607a55425] from 192.168.73.1:50102 to 67.38.19.212:59148
  153. [3/29/2020 3:37:19 PM] Noble Connect [22399]: Sending BIND REQUEST [18990690636edbe4e068e633] from 192.168.57.1:50104 to 192.168.1.69:59148
  154. [3/29/2020 3:37:19 PM] Noble Connect [22402]: Sending BIND REQUEST [898d5268202252d9a86cbbd9] from 127.0.0.1:50109 to 67.38.19.212:59148
  155. [3/29/2020 3:37:19 PM] Noble Connect [22419]: Sending BIND REQUEST [ee5eb37f9d651b21f387cc15] from 169.254.44.238:50106 to 127.0.0.1:59149
  156. [3/29/2020 3:37:19 PM] Noble Connect [22422]: Sending BIND REQUEST [307c38251a26b6cda6f8dfbd] from 169.254.44.238:50106 to 67.38.19.212:59148
  157. [3/29/2020 3:37:19 PM] Noble Connect [22439]: Sending BIND REQUEST [c7b391c23962e16e633bffdb] from 192.168.73.1:50102 to 192.168.1.69:59148
  158. [3/29/2020 3:37:19 PM] Noble Connect [22442]: Sending BIND REQUEST [667e51b381e929855d53ddb9] from 169.254.176.12:50108 to 67.38.19.212:59148
  159. [3/29/2020 3:37:19 PM] Noble Connect [22459]: Sending BIND REQUEST [3db7b035716f447d73eebbed] from 192.168.56.1:50103 to 127.0.0.1:59149
  160. [3/29/2020 3:37:19 PM] Noble Connect [22462]: Sending BIND REQUEST [c3d8c7bc8ed24a16d0c476cb] from 192.168.1.200:50101 to 67.38.19.212:59148
  161. [3/29/2020 3:37:19 PM] Noble Connect [22482]: Sending BIND REQUEST [d7d56d384e0d229fdf39a042] from 192.168.56.1:50103 to 192.168.1.69:59148
  162. [3/29/2020 3:37:19 PM] Noble Connect [22482]: Sending BIND REQUEST [1751698c922ab0e6d38e99ca] from 169.254.50.150:50107 to 67.38.19.212:59148
  163. [3/29/2020 3:37:19 PM] Noble Connect [22502]: Handle response from 67.38.19.212:59148 at 192.168.1.200:50101
  164. [3/29/2020 3:37:19 PM] Noble Connect [22502]: Received BIND SUCCESS RESPONSE [c3d8c7bc8ed24a16d0c476cb] from 67.38.19.212:59148 at 192.168.1.200:50101
  165. [3/29/2020 3:37:19 PM] Noble Connect [22502]: Sending BIND REQUEST [ac5ada5077c713ef1e30e967] from 192.168.1.200:50101 to 127.0.0.1:59149
  166. [3/29/2020 3:37:19 PM] Noble Connect [22502]: Sending BIND REQUEST [aac2ba7e4fb580ed54ab96a0] from 192.168.56.1:50103 to 67.38.19.212:59148
  167. [3/29/2020 3:37:19 PM] Noble Connect [22505]: Session Candidate: HOST (192.168.1.200:50101) => SERVER_REFLEXIVE (67.38.19.212:59148)
  168. [3/29/2020 3:37:19 PM] Noble Connect [22507]: Selected Pair: HOST (192.168.1.200:50101) => SERVER_REFLEXIVE (67.38.19.212:59148)
  169. [3/29/2020 3:37:19 PM] Noble Connect [22507]: Sending BIND REQUEST [2d1491443785ccddbbdc83ea] from 192.168.1.200:50101 to 67.38.19.212:59148
  170. [3/29/2020 3:37:19 PM] Noble Connect [22548]: Handle response from 67.38.19.212:59148 at 192.168.1.200:50101
  171. [3/29/2020 3:37:19 PM] Noble Connect [22548]: Received BIND SUCCESS RESPONSE [2d1491443785ccddbbdc83ea] from 67.38.19.212:59148 at 192.168.1.200:50101
  172. [3/29/2020 3:37:19 PM] Noble Connect [22549]: Connecting via route: HOST (192.168.1.200:50101) => SERVER_REFLEXIVE (67.38.19.212:59148)
  173. [3/29/2020 3:37:19 PM] Noble Connect [22555]: Received BIND REQUEST [d8d2a99eeceaaad7be0924ec] from 67.38.19.212:59148 at 192.168.1.200:50101
  174. [3/29/2020 3:37:19 PM] Noble Connect [22556]: Sending BIND SUCCESS_RESPONSE [d8d2a99eeceaaad7be0924ec] from 192.168.1.200:50101 to 67.38.19.212:59148
  175. [3/29/2020 3:37:19 PM] Noble Connect [22586]: Received BIND REQUEST [f87558308a09c8ad2e2cf9de] from 67.38.19.212:59148 at 68.183.117.123:3478
  176. [3/29/2020 3:37:19 PM] Noble Connect [22586]: Sending BIND SUCCESS_RESPONSE [f87558308a09c8ad2e2cf9de] from 192.168.1.200:50101 to 67.38.19.212:59148
  177. [3/29/2020 3:37:19 PM] Noble Connect [22632]: Received BIND REQUEST [466d45cc6ded9e340ca799f2] from 68.183.117.123:62119 at 68.183.117.123:3478
  178. [3/29/2020 3:37:19 PM] Noble Connect [22632]: Sending BIND SUCCESS_RESPONSE [466d45cc6ded9e340ca799f2] from 192.168.1.200:50101 to 68.183.117.123:62119
  179. [3/29/2020 3:37:28 PM] Noble Connect [31785]: Adding bridge for peer 67.38.19.212:59148 with client end point: 127.0.0.1:56767
  180. [3/29/2020 3:37:34 PM] Noble Connect [37801]: Sending REFRESH REQUEST [79a979c8b22f0dbe7c7c7fa8] from 192.168.1.200:50101 to 68.183.117.123:3478
  181. [3/29/2020 3:37:35 PM] Noble Connect [37817]: Handle response from 68.183.117.123:3478 at 192.168.1.200:50101
  182. [3/29/2020 3:37:35 PM] Noble Connect [37817]: Received REFRESH SUCCESS RESPONSE [79a979c8b22f0dbe7c7c7fa8] from 68.183.117.123:3478 at 192.168.1.200:50101
  183. [3/29/2020 3:38:54 PM] Network setup cancelled by user.
  184. [3/29/2020 3:38:56 PM] Resolving named connection to server. [Copernicus219]
  185. [3/29/2020 3:38:56 PM] Attempting resolved connection to server. [68.183.117.123:62119]
  186. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Found host candidate: HOST (192.168.1.200:54753)
  187. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Found host candidate: HOST (192.168.73.1:54754)
  188. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Found host candidate: HOST (192.168.56.1:54755)
  189. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Found host candidate: HOST (192.168.57.1:54756)
  190. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Found host candidate: HOST (192.168.99.1:54757)
  191. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Found host candidate: HOST (169.254.44.238:54758)
  192. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Found host candidate: HOST (169.254.50.150:54759)
  193. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Found host candidate: HOST (169.254.176.12:54760)
  194. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Found host candidate: HOST (127.0.0.1:54761)
  195. [3/29/2020 3:38:57 PM] Noble Connect [120084]: Sending ALLOCATE REQUEST [000ae0defa815d08e9cc784b] from 192.168.1.200:54753 to 68.183.117.123:3478
  196. [3/29/2020 3:38:57 PM] Noble Connect [120102]: Handle response from 68.183.117.123:3478 at 192.168.1.200:54753
  197. [3/29/2020 3:38:57 PM] Noble Connect [120102]: Received ALLOCATE ERROR RESPONSE [000ae0defa815d08e9cc784b] (401): Unauthorized
  198. [3/29/2020 3:38:57 PM] Noble Connect [120102]: Sending ALLOCATE REQUEST [1f510788c77554355728384e] from 192.168.1.200:54753 to 68.183.117.123:3478
  199. [3/29/2020 3:38:57 PM] Noble Connect [120104]: Sending ALLOCATE REQUEST [945c10b1849d525ca4affbab] from 192.168.73.1:54754 to 68.183.117.123:3478
  200. [3/29/2020 3:38:57 PM] Noble Connect [120119]: Handle response from 68.183.117.123:3478 at 192.168.1.200:54753
  201. [3/29/2020 3:38:57 PM] Noble Connect [120119]: Received ALLOCATE SUCCESS RESPONSE [1f510788c77554355728384e] from 68.183.117.123:3478 at 192.168.1.200:54753
  202. [3/29/2020 3:38:57 PM] Noble Connect [120124]: Sending ALLOCATE REQUEST [f4ff4fdfcde1e352ab1bd923] from 192.168.56.1:54755 to 68.183.117.123:3478
  203. [3/29/2020 3:38:57 PM] Noble Connect [120149]: Sending ALLOCATE REQUEST [e6060aab40a18936694bd45a] from 192.168.57.1:54756 to 68.183.117.123:3478
  204. [3/29/2020 3:38:57 PM] Noble Connect [120168]: Sending ALLOCATE REQUEST [8a84e29eba3dfc81e84240b4] from 192.168.99.1:54757 to 68.183.117.123:3478
  205. [3/29/2020 3:38:57 PM] Noble Connect [120189]: Sending ALLOCATE REQUEST [fb4a60eb60f5c6b6cd14a8b8] from 169.254.44.238:54758 to 68.183.117.123:3478
  206. [3/29/2020 3:38:57 PM] Noble Connect [120209]: Sending ALLOCATE REQUEST [33f4b1f8388f1d63f4ed18cd] from 169.254.50.150:54759 to 68.183.117.123:3478
  207. [3/29/2020 3:38:57 PM] Noble Connect [120229]: Sending ALLOCATE REQUEST [794144b2b36d24d96c5122df] from 169.254.176.12:54760 to 68.183.117.123:3478
  208. [3/29/2020 3:38:57 PM] Noble Connect [120249]: Sending ALLOCATE REQUEST [d5791e4ed78db7a38e122aba] from 127.0.0.1:54761 to 68.183.117.123:3478
  209. [3/29/2020 3:38:57 PM] Noble Connect [120304]: Sending ALLOCATE REQUEST [945c10b1849d525ca4affbab] from 192.168.73.1:54754 to 68.183.117.123:3478
  210. [3/29/2020 3:38:57 PM] Noble Connect [120324]: Sending ALLOCATE REQUEST [f4ff4fdfcde1e352ab1bd923] from 192.168.56.1:54755 to 68.183.117.123:3478
  211. [3/29/2020 3:38:57 PM] Noble Connect [120349]: Sending ALLOCATE REQUEST [e6060aab40a18936694bd45a] from 192.168.57.1:54756 to 68.183.117.123:3478
  212. [3/29/2020 3:38:57 PM] Noble Connect [120369]: Sending ALLOCATE REQUEST [8a84e29eba3dfc81e84240b4] from 192.168.99.1:54757 to 68.183.117.123:3478
  213. [3/29/2020 3:38:57 PM] Noble Connect [120394]: Sending ALLOCATE REQUEST [fb4a60eb60f5c6b6cd14a8b8] from 169.254.44.238:54758 to 68.183.117.123:3478
  214. [3/29/2020 3:38:57 PM] Noble Connect [120409]: Sending ALLOCATE REQUEST [33f4b1f8388f1d63f4ed18cd] from 169.254.50.150:54759 to 68.183.117.123:3478
  215. [3/29/2020 3:38:57 PM] Noble Connect [120429]: Sending ALLOCATE REQUEST [794144b2b36d24d96c5122df] from 169.254.176.12:54760 to 68.183.117.123:3478
  216. [3/29/2020 3:38:57 PM] Noble Connect [120449]: Sending ALLOCATE REQUEST [d5791e4ed78db7a38e122aba] from 127.0.0.1:54761 to 68.183.117.123:3478
  217. [3/29/2020 3:38:57 PM] Noble Connect [120704]: Sending ALLOCATE REQUEST [945c10b1849d525ca4affbab] from 192.168.73.1:54754 to 68.183.117.123:3478
  218. [3/29/2020 3:38:57 PM] Noble Connect [120724]: Sending ALLOCATE REQUEST [f4ff4fdfcde1e352ab1bd923] from 192.168.56.1:54755 to 68.183.117.123:3478
  219. [3/29/2020 3:38:57 PM] Noble Connect [120749]: Sending ALLOCATE REQUEST [e6060aab40a18936694bd45a] from 192.168.57.1:54756 to 68.183.117.123:3478
  220. [3/29/2020 3:38:57 PM] Noble Connect [120769]: Sending ALLOCATE REQUEST [8a84e29eba3dfc81e84240b4] from 192.168.99.1:54757 to 68.183.117.123:3478
  221. [3/29/2020 3:38:57 PM] Noble Connect [120794]: Sending ALLOCATE REQUEST [fb4a60eb60f5c6b6cd14a8b8] from 169.254.44.238:54758 to 68.183.117.123:3478
  222. [3/29/2020 3:38:58 PM] Noble Connect [120809]: Sending ALLOCATE REQUEST [33f4b1f8388f1d63f4ed18cd] from 169.254.50.150:54759 to 68.183.117.123:3478
  223. [3/29/2020 3:38:58 PM] Noble Connect [120829]: Sending ALLOCATE REQUEST [794144b2b36d24d96c5122df] from 169.254.176.12:54760 to 68.183.117.123:3478
  224. [3/29/2020 3:38:58 PM] Noble Connect [120849]: Sending ALLOCATE REQUEST [d5791e4ed78db7a38e122aba] from 127.0.0.1:54761 to 68.183.117.123:3478
  225. [3/29/2020 3:38:58 PM] Noble Connect [121504]: Sending ALLOCATE REQUEST [945c10b1849d525ca4affbab] from 192.168.73.1:54754 to 68.183.117.123:3478
  226. [3/29/2020 3:38:58 PM] Noble Connect [121524]: Sending ALLOCATE REQUEST [f4ff4fdfcde1e352ab1bd923] from 192.168.56.1:54755 to 68.183.117.123:3478
  227. [3/29/2020 3:38:58 PM] Noble Connect [121549]: Sending ALLOCATE REQUEST [e6060aab40a18936694bd45a] from 192.168.57.1:54756 to 68.183.117.123:3478
  228. [3/29/2020 3:38:58 PM] Noble Connect [121569]: Sending ALLOCATE REQUEST [8a84e29eba3dfc81e84240b4] from 192.168.99.1:54757 to 68.183.117.123:3478
  229. [3/29/2020 3:38:58 PM] Noble Connect [121594]: Sending ALLOCATE REQUEST [fb4a60eb60f5c6b6cd14a8b8] from 169.254.44.238:54758 to 68.183.117.123:3478
  230. [3/29/2020 3:38:58 PM] Noble Connect [121609]: Sending ALLOCATE REQUEST [33f4b1f8388f1d63f4ed18cd] from 169.254.50.150:54759 to 68.183.117.123:3478
  231. [3/29/2020 3:38:58 PM] Noble Connect [121629]: Sending ALLOCATE REQUEST [794144b2b36d24d96c5122df] from 169.254.176.12:54760 to 68.183.117.123:3478
  232. [3/29/2020 3:38:58 PM] Noble Connect [121649]: Sending ALLOCATE REQUEST [d5791e4ed78db7a38e122aba] from 127.0.0.1:54761 to 68.183.117.123:3478
  233. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: HOST (192.168.1.200:54753)
  234. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: HOST (192.168.73.1:54754)
  235. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: HOST (192.168.56.1:54755)
  236. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: HOST (192.168.57.1:54756)
  237. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: HOST (192.168.99.1:54757)
  238. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: HOST (169.254.44.238:54758)
  239. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: HOST (169.254.50.150:54759)
  240. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: HOST (169.254.176.12:54760)
  241. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: HOST (127.0.0.1:54761)
  242. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: RELAYED (68.183.117.123:54178 => 192.168.1.200:54753)
  243. [3/29/2020 3:39:00 PM] Noble Connect [123249]: Found candidate: SERVER_REFLEXIVE (68.67.247.66:54753 => 192.168.1.200:54753)
  244. [3/29/2020 3:39:00 PM] Noble Connect [123250]: Sending CREATE_PERMISSION REQUEST [67ee9b94057f72e141427577] from 192.168.1.200:54753 to 68.183.117.123:3478
  245. [3/29/2020 3:39:00 PM] Noble Connect [123269]: Handle response from 68.183.117.123:3478 at 192.168.1.200:54753
  246. [3/29/2020 3:39:00 PM] Noble Connect [123269]: Received CREATE_PERMISSION SUCCESS RESPONSE [67ee9b94057f72e141427577] from 68.183.117.123:3478 at 192.168.1.200:54753
  247. [3/29/2020 3:39:00 PM] Noble Connect [123269]: Sending CREATE_PERMISSION REQUEST [f48883febfa7fcd6e9793a9c] from 192.168.1.200:54753 to 68.183.117.123:3478
  248. [3/29/2020 3:39:00 PM] Noble Connect [123287]: Handle response from 68.183.117.123:3478 at 192.168.1.200:54753
  249. [3/29/2020 3:39:00 PM] Noble Connect [123287]: Received CREATE_PERMISSION SUCCESS RESPONSE [f48883febfa7fcd6e9793a9c] from 68.183.117.123:3478 at 192.168.1.200:54753
  250. [3/29/2020 3:39:00 PM] Noble Connect [123288]: Sending SEND INDICATION [b8b7e3a1c4e32662b168dd14] from 192.168.1.200:54753 to 68.183.117.123:3478
  251. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Sending CHANNEL_BIND REQUEST [ed35a5a02873d12fdf8e4702] from 192.168.1.200:54753 to 68.183.117.123:3478
  252. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Sending CHANNEL_BIND REQUEST [4778180655fde4ba8d5e441b] from 192.168.1.200:54753 to 68.183.117.123:3478
  253. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Sending CHANNEL_BIND REQUEST [dcf95283a9d1af859fe6b572] from 192.168.1.200:54753 to 68.183.117.123:3478
  254. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Sending CHANNEL_BIND REQUEST [e11ebd80f9114e691250146b] from 192.168.1.200:54753 to 68.183.117.123:3478
  255. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.1.200:54753) => HOST (192.168.1.69:59148)
  256. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (127.0.0.1:54761) => HOST (127.0.0.1:59149)
  257. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (127.0.0.1:54761) => HOST (192.168.1.69:59148)
  258. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.176.12:54760) => HOST (127.0.0.1:59149)
  259. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.176.12:54760) => HOST (192.168.1.69:59148)
  260. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.50.150:54759) => HOST (127.0.0.1:59149)
  261. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.50.150:54759) => HOST (192.168.1.69:59148)
  262. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.44.238:54758) => HOST (192.168.1.69:59148)
  263. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.99.1:54757) => HOST (127.0.0.1:59149)
  264. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.99.1:54757) => HOST (192.168.1.69:59148)
  265. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.57.1:54756) => HOST (127.0.0.1:59149)
  266. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.57.1:54756) => HOST (192.168.1.69:59148)
  267. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.44.238:54758) => HOST (127.0.0.1:59149)
  268. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.73.1:54754) => HOST (192.168.1.69:59148)
  269. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.56.1:54755) => HOST (127.0.0.1:59149)
  270. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.56.1:54755) => HOST (192.168.1.69:59148)
  271. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.1.200:54753) => HOST (127.0.0.1:59149)
  272. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.73.1:54754) => HOST (127.0.0.1:59149)
  273. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.57.1:54756) => SERVER_REFLEXIVE (67.38.19.212:59148)
  274. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.99.1:54757) => SERVER_REFLEXIVE (67.38.19.212:59148)
  275. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.73.1:54754) => SERVER_REFLEXIVE (67.38.19.212:59148)
  276. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (127.0.0.1:54761) => SERVER_REFLEXIVE (67.38.19.212:59148)
  277. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.44.238:54758) => SERVER_REFLEXIVE (67.38.19.212:59148)
  278. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.176.12:54760) => SERVER_REFLEXIVE (67.38.19.212:59148)
  279. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.1.200:54753) => SERVER_REFLEXIVE (67.38.19.212:59148)
  280. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.50.150:54759) => SERVER_REFLEXIVE (67.38.19.212:59148)
  281. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.56.1:54755) => SERVER_REFLEXIVE (67.38.19.212:59148)
  282. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.176.12:54760) => RELAYED (68.183.117.123:62119)
  283. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.73.1:54754) => RELAYED (68.183.117.123:62119)
  284. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (192.168.1.200:54753) => RELAYED (68.183.117.123:62119)
  285. [3/29/2020 3:39:00 PM] Noble Connect [123337]: Local Candidate: HOST (169.254.44.238:54758) => RELAYED (68.183.117.123:62119)
  286. [3/29/2020 3:39:00 PM] Noble Connect [123338]: Local Candidate: HOST (127.0.0.1:54761) => RELAYED (68.183.117.123:62119)
  287. [3/29/2020 3:39:00 PM] Noble Connect [123338]: Local Candidate: HOST (192.168.99.1:54757) => RELAYED (68.183.117.123:62119)
  288. [3/29/2020 3:39:00 PM] Noble Connect [123338]: Local Candidate: HOST (192.168.57.1:54756) => RELAYED (68.183.117.123:62119)
  289. [3/29/2020 3:39:00 PM] Noble Connect [123338]: Local Candidate: HOST (169.254.50.150:54759) => RELAYED (68.183.117.123:62119)
  290. [3/29/2020 3:39:00 PM] Noble Connect [123338]: Local Candidate: HOST (192.168.56.1:54755) => RELAYED (68.183.117.123:62119)
  291. [3/29/2020 3:39:00 PM] Noble Connect [123338]: Local Candidate: RELAYED (68.183.117.123:54178 => 192.168.1.200:54753) => HOST (192.168.1.69:59148)
  292. [3/29/2020 3:39:00 PM] Noble Connect [123338]: Local Candidate: RELAYED (68.183.117.123:54178 => 192.168.1.200:54753) => HOST (127.0.0.1:59149)
  293. [3/29/2020 3:39:00 PM] Noble Connect [123338]: Local Candidate: RELAYED (68.183.117.123:54178 => 192.168.1.200:54753) => SERVER_REFLEXIVE (67.38.19.212:59148)
  294. [3/29/2020 3:39:00 PM] Noble Connect [123338]: Local Candidate: RELAYED (68.183.117.123:54178 => 192.168.1.200:54753) => RELAYED (68.183.117.123:62119)
  295. [3/29/2020 3:39:00 PM] Noble Connect [123354]: Handle response from 68.183.117.123:3478 at 192.168.1.200:54753
  296. [3/29/2020 3:39:00 PM] Noble Connect [123354]: Received CHANNEL_BIND SUCCESS RESPONSE [ed35a5a02873d12fdf8e4702] from 68.183.117.123:3478 at 192.168.1.200:54753
  297. [3/29/2020 3:39:00 PM] Noble Connect [123354]: Handle response from 68.183.117.123:3478 at 192.168.1.200:54753
  298. [3/29/2020 3:39:00 PM] Noble Connect [123354]: Received CHANNEL_BIND SUCCESS RESPONSE [4778180655fde4ba8d5e441b] from 68.183.117.123:3478 at 192.168.1.200:54753
  299. [3/29/2020 3:39:00 PM] Noble Connect [123354]: Handle response from 68.183.117.123:3478 at 192.168.1.200:54753
  300. [3/29/2020 3:39:00 PM] Noble Connect [123354]: Received CHANNEL_BIND SUCCESS RESPONSE [dcf95283a9d1af859fe6b572] from 68.183.117.123:3478 at 192.168.1.200:54753
  301. [3/29/2020 3:39:00 PM] Noble Connect [123354]: Handle response from 68.183.117.123:3478 at 192.168.1.200:54753
  302. [3/29/2020 3:39:00 PM] Noble Connect [123354]: Received CHANNEL_BIND SUCCESS RESPONSE [e11ebd80f9114e691250146b] from 68.183.117.123:3478 at 192.168.1.200:54753
  303. [3/29/2020 3:39:00 PM] Noble Connect [123358]: Sending BIND REQUEST [27568b991ee63815b6190ba9] from 192.168.1.200:54753 to 192.168.1.69:59148
  304. [3/29/2020 3:39:00 PM] Noble Connect [123378]: Sending BIND REQUEST [a13039ea92a824c6d1f219b8] from 127.0.0.1:54761 to 127.0.0.1:59149
  305. [3/29/2020 3:39:00 PM] Noble Connect [123398]: Sending BIND REQUEST [9284382956ce4986a621c49b] from 127.0.0.1:54761 to 192.168.1.69:59148
  306. [3/29/2020 3:39:00 PM] Noble Connect [123418]: Sending BIND REQUEST [7168ccb143fc79ea0c1f3a81] from 169.254.176.12:54760 to 127.0.0.1:59149
  307. [3/29/2020 3:39:00 PM] Noble Connect [123438]: Sending BIND REQUEST [5eabffb3efb64f6f17c66a7a] from 169.254.176.12:54760 to 192.168.1.69:59148
  308. [3/29/2020 3:39:00 PM] Noble Connect [123468]: Sending BIND REQUEST [4eec1ce913086bebbcb81590] from 169.254.50.150:54759 to 127.0.0.1:59149
  309. [3/29/2020 3:39:00 PM] Noble Connect [123488]: Sending BIND REQUEST [c4dd9abe52abd0289f499bf1] from 169.254.50.150:54759 to 192.168.1.69:59148
  310. [3/29/2020 3:39:00 PM] Noble Connect [123508]: Sending BIND REQUEST [01975191451d93ae0075464b] from 169.254.44.238:54758 to 192.168.1.69:59148
  311. [3/29/2020 3:39:00 PM] Noble Connect [123529]: Sending BIND REQUEST [3cca7a943a5b80770faacf2c] from 192.168.99.1:54757 to 127.0.0.1:59149
  312. [3/29/2020 3:39:00 PM] Noble Connect [123549]: Sending BIND REQUEST [e7c039c3787a146118ea9997] from 192.168.99.1:54757 to 192.168.1.69:59148
  313. [3/29/2020 3:39:00 PM] Noble Connect [123558]: Sending BIND REQUEST [27568b991ee63815b6190ba9] from 192.168.1.200:54753 to 192.168.1.69:59148
  314. [3/29/2020 3:39:00 PM] Noble Connect [123569]: Sending BIND REQUEST [57a948815a59d4865d187106] from 192.168.57.1:54756 to 127.0.0.1:59149
  315. [3/29/2020 3:39:00 PM] Noble Connect [123578]: Sending BIND REQUEST [a13039ea92a824c6d1f219b8] from 127.0.0.1:54761 to 127.0.0.1:59149
  316. [3/29/2020 3:39:00 PM] Noble Connect [123589]: Sending BIND REQUEST [d4341309570b275de0c4bdbe] from 192.168.57.1:54756 to 192.168.1.69:59148
  317. [3/29/2020 3:39:00 PM] Noble Connect [123598]: Sending BIND REQUEST [9284382956ce4986a621c49b] from 127.0.0.1:54761 to 192.168.1.69:59148
  318. [3/29/2020 3:39:00 PM] Noble Connect [123609]: Sending BIND REQUEST [bada63467b8c117a1a560e52] from 169.254.44.238:54758 to 127.0.0.1:59149
  319. [3/29/2020 3:39:00 PM] Noble Connect [123618]: Sending BIND REQUEST [7168ccb143fc79ea0c1f3a81] from 169.254.176.12:54760 to 127.0.0.1:59149
  320. [3/29/2020 3:39:00 PM] Noble Connect [123629]: Sending BIND REQUEST [62f88063b68963f6ad74cee3] from 192.168.73.1:54754 to 192.168.1.69:59148
  321. [3/29/2020 3:39:00 PM] Noble Connect [123638]: Sending BIND REQUEST [5eabffb3efb64f6f17c66a7a] from 169.254.176.12:54760 to 192.168.1.69:59148
  322. [3/29/2020 3:39:00 PM] Noble Connect [123649]: Sending BIND REQUEST [dbd7cb2c819978589f797666] from 192.168.56.1:54755 to 127.0.0.1:59149
  323. [3/29/2020 3:39:00 PM] Noble Connect [123668]: Sending BIND REQUEST [4eec1ce913086bebbcb81590] from 169.254.50.150:54759 to 127.0.0.1:59149
  324. [3/29/2020 3:39:00 PM] Noble Connect [123669]: Sending BIND REQUEST [c3bc6d56988a6df7a9a6e193] from 192.168.56.1:54755 to 192.168.1.69:59148
  325. [3/29/2020 3:39:00 PM] Noble Connect [123688]: Sending BIND REQUEST [c4dd9abe52abd0289f499bf1] from 169.254.50.150:54759 to 192.168.1.69:59148
  326. [3/29/2020 3:39:00 PM] Noble Connect [123689]: Sending BIND REQUEST [ef168ae9544e62817b6a8d0d] from 192.168.1.200:54753 to 127.0.0.1:59149
  327. [3/29/2020 3:39:00 PM] Noble Connect [123708]: Sending BIND REQUEST [01975191451d93ae0075464b] from 169.254.44.238:54758 to 192.168.1.69:59148
  328. [3/29/2020 3:39:00 PM] Noble Connect [123709]: Sending BIND REQUEST [6a18029b165ea1ab0d9236c4] from 192.168.73.1:54754 to 127.0.0.1:59149
  329. [3/29/2020 3:39:00 PM] Noble Connect [123729]: Sending BIND REQUEST [3cca7a943a5b80770faacf2c] from 192.168.99.1:54757 to 127.0.0.1:59149
  330. [3/29/2020 3:39:00 PM] Noble Connect [123729]: Sending BIND REQUEST [de8177f53c60a42e9ecfc3d2] from 192.168.57.1:54756 to 67.38.19.212:59148
  331. [3/29/2020 3:39:00 PM] Noble Connect [123749]: Sending BIND REQUEST [e7c039c3787a146118ea9997] from 192.168.99.1:54757 to 192.168.1.69:59148
  332. [3/29/2020 3:39:00 PM] Noble Connect [123749]: Sending BIND REQUEST [65996cd375fe24cac1e66bfc] from 192.168.99.1:54757 to 67.38.19.212:59148
  333. [3/29/2020 3:39:00 PM] Noble Connect [123769]: Sending BIND REQUEST [57a948815a59d4865d187106] from 192.168.57.1:54756 to 127.0.0.1:59149
  334. [3/29/2020 3:39:00 PM] Noble Connect [123769]: Sending BIND REQUEST [00c071648ff29e37d26e5f37] from 192.168.73.1:54754 to 67.38.19.212:59148
  335. [3/29/2020 3:39:00 PM] Noble Connect [123789]: Sending BIND REQUEST [d4341309570b275de0c4bdbe] from 192.168.57.1:54756 to 192.168.1.69:59148
  336. [3/29/2020 3:39:00 PM] Noble Connect [123789]: Sending BIND REQUEST [622e021a3e8b02ac3f740f52] from 127.0.0.1:54761 to 67.38.19.212:59148
  337. [3/29/2020 3:39:01 PM] Noble Connect [123809]: Sending BIND REQUEST [bada63467b8c117a1a560e52] from 169.254.44.238:54758 to 127.0.0.1:59149
  338. [3/29/2020 3:39:01 PM] Noble Connect [123809]: Sending BIND REQUEST [3527213580409b465b58b2a9] from 169.254.44.238:54758 to 67.38.19.212:59148
  339. [3/29/2020 3:39:01 PM] Noble Connect [123829]: Sending BIND REQUEST [62f88063b68963f6ad74cee3] from 192.168.73.1:54754 to 192.168.1.69:59148
  340. [3/29/2020 3:39:01 PM] Noble Connect [123829]: Sending BIND REQUEST [ee0685fc3891a5872bfc36c2] from 169.254.176.12:54760 to 67.38.19.212:59148
  341. [3/29/2020 3:39:01 PM] Noble Connect [123849]: Sending BIND REQUEST [dbd7cb2c819978589f797666] from 192.168.56.1:54755 to 127.0.0.1:59149
  342. [3/29/2020 3:39:01 PM] Noble Connect [123849]: Sending BIND REQUEST [7f0cbdbb883cabd96dfa65f6] from 192.168.1.200:54753 to 67.38.19.212:59148
  343. [3/29/2020 3:39:01 PM] Noble Connect [123869]: Sending BIND REQUEST [c3bc6d56988a6df7a9a6e193] from 192.168.56.1:54755 to 192.168.1.69:59148
  344. [3/29/2020 3:39:01 PM] Noble Connect [123869]: Sending BIND REQUEST [54caeebf4b929bb7ce12b853] from 169.254.50.150:54759 to 67.38.19.212:59148
  345. [3/29/2020 3:39:01 PM] Noble Connect [123889]: Sending BIND REQUEST [ef168ae9544e62817b6a8d0d] from 192.168.1.200:54753 to 127.0.0.1:59149
  346. [3/29/2020 3:39:01 PM] Noble Connect [123889]: Sending BIND REQUEST [cfbe65aafd6dc3643a91c62c] from 192.168.56.1:54755 to 67.38.19.212:59148
  347. [3/29/2020 3:39:01 PM] Noble Connect [123892]: Handle response from 67.38.19.212:59148 at 192.168.1.200:54753
  348. [3/29/2020 3:39:01 PM] Noble Connect [123892]: Received BIND SUCCESS RESPONSE [7f0cbdbb883cabd96dfa65f6] from 67.38.19.212:59148 at 192.168.1.200:54753
  349. [3/29/2020 3:39:01 PM] Noble Connect [123892]: Session Candidate: HOST (192.168.1.200:54753) => SERVER_REFLEXIVE (67.38.19.212:59148)
  350. [3/29/2020 3:39:01 PM] Noble Connect [123892]: Selected Pair: HOST (192.168.1.200:54753) => SERVER_REFLEXIVE (67.38.19.212:59148)
  351. [3/29/2020 3:39:01 PM] Noble Connect [123892]: Sending BIND REQUEST [260f84443536eacd7827176f] from 192.168.1.200:54753 to 67.38.19.212:59148
  352. [3/29/2020 3:39:01 PM] Noble Connect [123933]: Handle response from 67.38.19.212:59148 at 192.168.1.200:54753
  353. [3/29/2020 3:39:01 PM] Noble Connect [123933]: Received BIND SUCCESS RESPONSE [260f84443536eacd7827176f] from 67.38.19.212:59148 at 192.168.1.200:54753
  354. [3/29/2020 3:39:01 PM] Noble Connect [123933]: Connecting via route: HOST (192.168.1.200:54753) => SERVER_REFLEXIVE (67.38.19.212:59148)
  355. [3/29/2020 3:39:01 PM] Noble Connect [123979]: Received BIND REQUEST [12a07c168f554846179c59c7] from 67.38.19.212:59148 at 192.168.1.200:54753
  356. [3/29/2020 3:39:01 PM] Noble Connect [123979]: Sending BIND SUCCESS_RESPONSE [12a07c168f554846179c59c7] from 192.168.1.200:54753 to 67.38.19.212:59148
  357. [3/29/2020 3:39:01 PM] Noble Connect [124021]: Received BIND REQUEST [b52f77a36ce50f19fe97b770] from 67.38.19.212:59148 at 68.183.117.123:3478
  358. [3/29/2020 3:39:01 PM] Noble Connect [124021]: Sending BIND SUCCESS_RESPONSE [b52f77a36ce50f19fe97b770] from 192.168.1.200:54753 to 67.38.19.212:59148
  359. [3/29/2020 3:39:17 PM] Noble Connect [139818]: Adding bridge for peer 67.38.19.212:59148 with client end point: 127.0.0.1:54781
  360. [3/29/2020 3:39:18 PM] [WARNING] Lost connection to matchmaking server : Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
  361. .
  362. [3/29/2020 3:39:23 PM] Noble Connect [145818]: Sending REFRESH REQUEST [3690ed6992cb51f680632935] from 192.168.1.200:54753 to 68.183.117.123:3478
  363. [3/29/2020 3:39:23 PM] Noble Connect [145835]: Handle response from 68.183.117.123:3478 at 192.168.1.200:54753
  364. [3/29/2020 3:39:23 PM] Noble Connect [145835]: Received REFRESH SUCCESS RESPONSE [3690ed6992cb51f680632935] from 68.183.117.123:3478 at 192.168.1.200:54753
  365. [3/29/2020 3:41:32 PM] Network setup cancelled by user.
  366. [3/29/2020 3:41:36 PM] Resolving named connection to server. [Copernicus219]
  367. [3/29/2020 3:42:40 PM] Network setup cancelled by user.
  368. [3/29/2020 3:42:41 PM] Resolving named connection to server. [Copernicus219]
  369. [3/29/2020 3:42:44 PM] Network setup cancelled by user.
  370. [3/29/2020 3:42:47 PM] Resolving named connection to server. [Copernicus219]
  371. [3/29/2020 3:48:27 PM] Network setup cancelled by user.
  372. [3/29/2020 3:48:31 PM] Resolving named connection to server. [Copernicus219]
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!