API tools faq
paste
Advertisement
pjj90292

bcm_wimax scans and tries to connect

pjj90292
Oct 5th, 2013
371
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 11.19 KB | None | 0 0
raw download clone embed print report
  1. Second test near tower.
  2. 10/4/13
  3. bcm_wimax
  4.  
  5. wimaxd command
  6. output
  7. .. .
  8. Timer Authentication thread has started.
  9. Process Messages thread has started.
  10. Changed state to: Waiting for WiMAX adapter ...
  11. Trying to open device.
  12. Device opened successfully.
  13. Registering callback function - Success.
  14. Changed state to: WiMAX adapter initialized
  15.  
  16. ***** Sending subscriber station information request
  17. Sent: 07 00 01 00
  18.  
  19. =============== Received Message Start (2013/09/04 18:15:03.153) ===========
  20. u32State = WiMAX adapter initialized
  21. SS info response received (Type = 7 - Subtype = 1 - Length = 184)
  22. INFO: No socket in BeceemAPI_Unlock()
  23. Client socket FFFFFFFF unlock Beceem API: Was not locked (this is not an error)
  24. Found valid library version: 6.0.37
  25. =============== Received Message End (type=7 sub-type=1) ===============
  26. ***** Message sent successfully
  27. Changed state to: Waiting for WiMAX adapter ...(truncated)
  28.  
  29.  
  30.  
  31. =============== Received Message Start (2013/09/04 18:15:15.560) ===========
  32. u32State = Waiting for PHY sync start
  33. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  34. Network Entry Status Received
  35. Link status = WAIT FOR PHY SYNC CMD
  36. =============== Received Message End (type=2 sub-type=2) ===============
  37. ***** Message sent successfully
  38. Got connection 1 from 127.0.0.1
  39. Wcm connection handling thread launched successfully
  40. Socket is 00000006
  41. Client socket 00000006 lock Beceem API: SUCCESS (wait = 0 ms)
  42. Client socket 00000006 unlock Beceem API: Success
  43.  
  44. . . . (Truncated)
  45.  
  46. ***** Message sent successfully
  47. Received 7 bytes:
  48.  
  49. 0000: 73 65 61 72 63 68 00
  50. Executing command 'search'
  51. Client socket 00000006 lock Beceem API: SUCCESS (wait = 0 ms)
  52.  
  53. ***** Sending PHY sync down request
  54. Sent: 03 00 01 00
  55. ***** Message sent successfully
  56. Changed state to: Sync down request sent
  57.  
  58. =============== Received Message Start (2013/09/04 18:15:20.957) ===========
  59. u32State = Sync down request sent
  60. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  61. Network Entry Status Received
  62. Link status = HOST INITIATED SYNC DOWN
  63. Changed state to: Connection error
  64. Search CF: 2499000 2505250 2508500 2510250 2515250 2518500 2521750 2525000 2526750 2528500 2531750 2535000 2538250 2541500 2543250 2545000 2548250 2551500 2554750 2559750 2561500 2564750 2575000 2578000 2581000 2584000 2587000 2590000 2593000 2596000 2599000 2602000 2605000 2608000 2611000 2621000 2627250 2630500 2632250 2637250 2640500 2643750 2647000 2648750 2650500 2653750 2657000 2660250 2663500 2665250 2667000 2670250 2673500 2676750 2681750 2683500 2686750
  65.  
  66. ***** Sending network search request (2013/09/04 18:15:20.959)
  67. Sent: 01 00 01 00 00 00 00 00 02 00 00 00 02 00 00 00 88 13 00 00 10 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 39 00 00 00 B8 21 26 00 22 3A 26 00 D4 46 26 00 AA 4D 26 00 32 61 26 00 E4 6D 26 00 96 7A 26 00 48 87 26 00 1E 8E 26 00 F4 94 26 00 A6 A1 26 00 58 AE 26 00 0A BB 26 00 BC C7 26 00 92 CE 26 00 68 D5 26 00 1A E2 26 00 CC EE 26 00 7E FB 26 00 06 0F 27 00 DC 15 27 00 8E 22 27 00 98 4A 27 00 50 56 27 00 08 62 27 00 C0 6D 27 00 78 79 27 00 30 85 27 00 E8 90 27 00 A0 9C 27 00 58 A8 27 00 10 B4 27 00 C8 BF 27 00 80 CB 27 00 38 D7 27 00 48 FE 27 00 B2 16 28 00 64 23 28 00 3A 2A 28 00 C2 3D 28 00 74 4A 28 00 26 57 28 00 D8 63 28 00 AE 6A 28 00 84 71 28 00 36 7E 28 00 E8 8A 28 00 9A 97 28 00 4C A4 28 00 22 AB 28 00 F8 B1 28 00 AA BE 28 00 5C CB 28 00 0E D8 28 00 96 EB 28 00 6C F2 28 00 1E FF 28 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  68. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  69. ***** Message sent successfully
  70. =============== Received Message End (type=2 sub-type=2) ===============
  71.  
  72. =============== Received Message Start (2013/09/04 18:15:20.988) ===========
  73. u32State = Connection error
  74. Network entry response received (Type = 2 - Subtype = 5 - Length = 12)
  75. Device status indication: Device is scanning
  76. =============== Received Message End (type=2 sub-type=5) ===============
  77.  
  78. =============== Received Message Start (2013/09/04 18:15:22.111) ===========
  79. u32State = Connection error
  80. Network entry response received (Type = 2 - Subtype = 5 - Length = 12)
  81. Device status indication: Device is ready
  82. =============== Received Message End (type=2 sub-type=5) ===============
  83.  
  84. =============== Received Message Start (2013/09/04 18:15:22.113) ===========
  85. u32State = Connection error
  86. Network entry response received (Type = 2 - Subtype = 5 - Length = 12)
  87. Connection status indication: Waiting for Sync
  88. =============== Received Message End (type=2 sub-type=5) ===============
  89.  
  90. =============== Received Message Start (2013/09/04 18:15:22.115) ===========
  91. u32State = Connection error
  92. Network entry response received (Type = 2 - Subtype = 5 - Length = 12)
  93. Link status indication: Link Status Normal
  94. =============== Received Message End (type=2 sub-type=5) ===============
  95.  
  96. . . . (truncated)
  97.  
  98. =============== Received Message Start (2013/09/04 18:15:29.585) ===========
  99. u32State = Waiting for PHY sync start
  100. Network entry response received (Type = 2 - Subtype = 5 - Length = 12)
  101. Link status indication: Link Status Normal
  102. =============== Received Message End (type=2 sub-type=5) ===============
  103.  
  104. ***** Sending link status request (2013/09/04 18:15:31.978)
  105. Sent: 02 00 03 00
  106. ***** Message sent successfully
  107.  
  108. =============== Received Message Start (2013/09/04 18:15:31.980) ===========
  109. u32State = Waiting for PHY sync start
  110. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  111. Network Entry Status Received
  112. Link status = WAIT FOR PHY SYNC CMD
  113. =============== Received Message End (type=2 sub-type=2) ===============
  114. . . . (truncated)
  115.  
  116. =============== Received Message Start (2013/09/04 18:15:33.268) ===========
  117. u32State = Waiting for PHY sync start
  118. Network search response received (Type = 1 - Subtype = 1 - Length = 192)
  119.  
  120. 5 base stations found.
  121.  
  122. Base Station 1
  123. Preamble Index ID: 0x0001
  124. Relative Signal Strength: 0xFFFFFFBF
  125. CINR 0x0000001D
  126. Bandwidth 0x00002710
  127. Center frequency 0x002646D4
  128. Base Station ID 20:05:81:02:00:00:01:01
  129.  
  130. Base Station 2
  131. Preamble Index ID: 0x0020
  132. Relative Signal Strength: 0xFFFFFFC9
  133. CINR 0x00000019
  134. Bandwidth 0x00002710
  135. Center frequency 0x00266DE4
  136. Base Station ID 10:05:81:02:00:00:01:01
  137.  
  138. Base Station 3
  139. Preamble Index ID: 0x0020
  140. Relative Signal Strength: 0xFFFFFFC6
  141. CINR 0x00000019
  142. Bandwidth 0x00002710
  143. Center frequency 0x002694F4
  144. Base Station ID 11:05:81:02:00:00:01:01
  145.  
  146. Base Station 4
  147. Preamble Index ID: 0x0053
  148. Relative Signal Strength: 0xFFFFFFAD
  149. CINR 0x0000000D
  150. Bandwidth 0x00002710
  151. Center frequency 0x002715DC
  152. Base Station ID 10:E9:80:02:00:00:01:01
  153.  
  154. Base Station 5
  155. Preamble Index ID: 0x0021
  156. Relative Signal Strength: 0xFFFFFFB5
  157. CINR 0x00000015
  158. Bandwidth 0x00002710
  159. Center frequency 0x0028A44C
  160. Base Station ID 00:05:81:02:00:00:01:01
  161.  
  162. -- Network Search status: Network search complete
  163. Changed state to: Network Search completed
  164. Changed state to: Waiting for PHY sync start
  165. =============== Received Message End (type=1 sub-type=1) ===============
  166. DEBUG: ServerSocketResponse for ID=20 Text chars=413: Network search returned 5 base stations.
  167. Idx BSID Pre Freq BW RSSI CINR
  168. 0 01:01:00:00:02:81:05:20 0x01 2508.500 10.000 -65 29 <--------
  169. 1 01:01:00:00:02:81:05:10 0x20 2518.500 10.000 -55 25
  170. 2 01:01:00:00:02:81:05:11 0x20 2528.500 10.000 -58 25 <--------
  171. 3 01:01:00:00:02:80:e9:10 0x53 2561.500 10.000 -83 13
  172. 4 01:01:00:00:02:81:05:00 0x21 2663.500 10.000 -75 21 <--------
  173.  
  174. Client socket 00000006 unlock Beceem API: Success
  175.  
  176. ***** Sending link status request (2013/09/04 18:15:36.085)
  177. Sent: 02 00 03 00
  178. ***** Message sent successfully
  179.  
  180. =============== Received Message Start (2013/09/04 18:15:36.085) ===========
  181. u32State = Waiting for PHY sync start
  182. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  183. Network Entry Status Received
  184. Link status = WAIT FOR PHY SYNC CMD
  185. =============== Received Message End (type=2 sub-type=2) ===============
  186.  
  187.  
  188.  
  189. . . . (truncated)
  190.  
  191. ***** Sending link status request (2013/09/04 18:15:40.189)
  192. Sent: 02 00 03 00
  193. ***** Message sent successfully
  194.  
  195. =============== Received Message Start (2013/09/04 18:15:40.190) ===========
  196. u32State = Waiting for PHY sync start
  197. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  198. Network Entry Status Received
  199. Link status = WAIT FOR PHY SYNC CMD
  200. =============== Received Message End (type=2 sub-type=2) ===============
  201.  
  202. ...
  203.  
  204. ============== Received Message End (type=2 sub-type=2) ===============
  205. ***** Message sent successfully
  206.  
  207. ***** Sending link status request (2013/09/04 18:20:19.346)
  208. Sent: 02 00 03 00
  209.  
  210. =============== Received Message Start (2013/09/04 18:20:19.346) ===========
  211. u32State = Waiting for network entry command
  212. Network entry response received (Type = 2 - Subtype = 2 - Length = 52)
  213. Network Entry Status Received
  214. Link status = WAIT FOR NETWORK ENTRY CMD
  215. EAP supplicant is not open (Program ERROR) <----------
  216. =============== Received Message End (type=2 sub-type=2) ===============
  217. . . .
  218.  
  219. End of log file (wimaxd):
  220.  
  221. ***** Message sent successfully
  222. ^CTerminating Authentication Timer thread.
  223. Timer Authentication thread has finished.
  224. Terminating Check Timeouts Timer thread.
  225. Timer Check Timeouts thread has finished.
  226. Terminating Periodic Action Timer thread.
  227. Closing device.
  228.  
  229.  
  230. The task at hand now is to determine exactly how to resolve the error 'EAP supplicant in not open'.
  231. It is also most interesting to note that when the bcm_wimax driver is used the
  232. Network Manager (KDE)
  233. opens a new networking interface of the type 'wired ethernet' under the name
  234. eth1.
  235.  
  236. This lets me think again that as soon as the EAP problem is solved and the modem actually connects it should be possible to start the 4G connection without the detour/procedures that now need to be used.
  237.  
  238. Driver drxvi314.ko showed identical results (though I am not printing the output here) - except it did not open a new wired ethernet connection.
  239.  
  240. Can anyone decode the binary output above, please? I did but it does not make sense to me.
  241. 10/05/13
  242. pjj
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!