API tools faq
paste
Advertisement
YeiZeta

Message of Navy.mil USA STATE MAILERS

YeiZeta
Dec 15th, 2012
395
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 24.92 KB | None | 0 0
raw download clone embed print report
  1. From alx.mancini at gmail.com Mon Dec 3 11:50:36 2012
  2. From: alx.mancini at gmail.com (Alessandro Mancini)
  3. Date: Mon, 3 Dec 2012 17:50:36 +0100
  4. Subject: [core-users] Range Problem with EMANE
  5. In-Reply-To: <[email protected]>
  6. References: <CABSfiGMMO98xX+h4sqSTkys_U8E40p9chv1rJK+xbw59dPkCvw@mail.gmail.com>
  7. <FD98F9C3CBABA74E89B5D4B5DE0263B937B5413288@XCH-NW-12V.nw.nos.boeing.com>
  8. <[email protected]>
  9. Message-ID: <CABSfiGP-xx8yCJycBNOeV6a9pso267+=37xq+gkXbnDY5sHiLA@mail.gmail.com>
  10.  
  11. Thank you Jeff and Steven for your quick responses: they are been very
  12. useful!!!
  13. Now, I understand a bit more how CORE and EMANE compute the rxPower and how
  14. a packet is dropped or accepted.
  15.  
  16. In fact, also by studying the EMANE User Manual, I discovered that:
  17. * rxPower = txpower txAntennaGain rxAntennaGain - pathloss,
  18. * rxSensitivity = noiseFigure -174 10log(bandWidth),
  19. * SINR = (rxPower / rxSensitivity).
  20.  
  21. I noted that a packet is dropped if rxPower is less than rxSensitivity and
  22. that is accepted with probability PoR (where PoR is function of SINR).
  23. I also noted that, in your Universal PHY configuration, you use only "2ray"
  24. as pathloss mode. *May be that CORE can't work with "pathloss" as pathloss
  25. mode?*
  26.  
  27. *At this point I've two residual questions...*
  28. 1* I would like to know if it is possible to use a pathloss model that
  29. is based on pathloss events (instead of one that is based on location
  30. events as 2ray or freespace).
  31. If yes, can I do this by using the EMANE Losscontroller? What are the steps
  32. that I need to perform?
  33.  
  34. 2* Can I use a customized pathloss model? If yes, do I need to use a
  35. file as "ieee80211abgphy.xml" in which I must insert the values relative to
  36. the BER curves? And, how can I set this file so that CORE can read and use
  37. it?
  38.  
  39. Thank you in advantage for your precious help.
  40.  
  41. On Fri, Nov 30, 2012 at 7:44 PM, Steven Galgano <sgalgano at cengen.com> wrote:
  42.  
  43. > Alessandro,
  44. >
  45. > The 802.11 MAC "distance" configuration parameter is used in the slot
  46. > time calculation for the 802.11 protocol (RTC, CTS, ACK etc.). It is
  47. > not used in the pathloss calculation.
  48. >
  49. > The Universal PHY can be configured to use pathloss between nodes (EMANE
  50. > pathloss events) or node locations (EMANE location events) with either
  51. > the 2-ray or freespace propagation models, to compute the rx power for
  52. > every packet. The rx power is used along with the current noise level
  53. > to compute an SINR, which in turn is used as an index into the PCR curve
  54. > file.
  55. >
  56. > --
  57. > Steven Galgano
  58. > DRS CenGen LLC
  59. >
  60. >
  61.  
  62.  
  63. --
  64. Alessandro Mancini
  65. -------------- next part --------------
  66. An HTML attachment was scrubbed...
  67. URL: http://pf.itd.nrl.navy.mil/pipermail/core-users/attachments/20121203/eabf6707/attachment.html
  68.  
  69. From jeffrey.m.ahrenholz at boeing.com Mon Dec 3 11:56:54 2012
  70. From: jeffrey.m.ahrenholz at boeing.com (Ahrenholz, Jeffrey M)
  71. Date: Mon, 3 Dec 2012 08:56:54 -0800
  72. Subject: [core-users] CORE daemon renamed
  73. Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B937B54A4E01@XCH-NW-12V.nw.nos.boeing.com>
  74.  
  75. As a heads up, in the SVN development snapshot, the CORE daemon has been renamed from 'cored.py' to 'cored'. Also, 'coresendmsg.py' is now 'coresendmsg'.
  76.  
  77. The init/systemd scripts retain their same names, so you can still start the daemon the same way as you did before (e.g. 'sudo /etc/init.d/core start'). The cored log is now '/var/log/cored.log' and PID file '/var/run/cored.pid' (instead of '/var/log/coredpy.log', '/var/run/coredpy.pid'.)
  78.  
  79. In the source code, the 'python' subdir has been renamed to 'daemon'.
  80.  
  81. These changes were made to simplify and improve the names used for CORE programs. Historically, there was a C-based 'cored' program supporting OpenVZ containers that is no longer used. In future releases, CORE will be split into two (rpm/deb) packages, one for the GUI and one for the daemon. This is because there are instances where you may want to install the CORE daemon without the GUI and X11/Tcl/Tk dependencies (e.g. for distributed emulation servers, physical nodes, Xen-based nodes, Python-only environments.)
  82.  
  83. -Jeff
  84.  
  85. From jeffrey.m.ahrenholz at boeing.com Mon Dec 3 12:05:15 2012
  86. From: jeffrey.m.ahrenholz at boeing.com (Ahrenholz, Jeffrey M)
  87. Date: Mon, 3 Dec 2012 09:05:15 -0800
  88. Subject: [core-users] Range Problem with EMANE
  89. In-Reply-To: <CABSfiGP-xx8yCJycBNOeV6a9pso267+=37xq+gkXbnDY5sHiLA@mail.gmail.com>
  90. References: <CABSfiGMMO98xX+h4sqSTkys_U8E40p9chv1rJK+xbw59dPkCvw@mail.gmail.com>
  91. <FD98F9C3CBABA74E89B5D4B5DE0263B937B5413288@XCH-NW-12V.nw.nos.boeing.com>
  92. <[email protected]>
  93. <CABSfiGP-xx8yCJycBNOeV6a9pso267+=37xq+gkXbnDY5sHiLA@mail.gmail.com>
  94. Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B937B54A4E0E@XCH-NW-12V.nw.nos.boeing.com>
  95.  
  96. Alessandro,
  97.  
  98. > SINR). I also noted that, in your Universal PHY configuration, you use
  99. > only "2ray" as pathloss mode. May be that CORE can't work with
  100. > "pathloss" as pathloss mode?
  101.  
  102. No, CORE can work with either mode; 2ray is just the default used by CORE. Configure the mode using the options button on the EMANE tab when you configure the WLAN during edit mode. CORE will generate EMANE location events when "emane_event_monitor = False" in the core.conf file. CORE does not generate pathloss events on its own.
  103.  
  104. > 1* I would like to know if it is possible to use a pathloss model that is
  105. > based on pathloss events (instead of one that is based on location events as
  106. > 2ray or freespace).
  107. > If yes, can I do this by using the EMANE Losscontroller? What are the steps
  108. > that I need to perform?
  109.  
  110. Please see this recent thread:
  111. http://pf.itd.nrl.navy.mil/pipermail/core-users/2012-November/001077.html
  112.  
  113. Here's a step-by-step:
  114. http://pf.itd.nrl.navy.mil/pipermail/core-users/2012-November/001096.html
  115.  
  116. > 2* Can I use a customized pathloss model? If yes, do I need to use a file
  117. > as "ieee80211abgphy.xml" in which I must insert the values relative to the
  118. > BER curves? And, how can I set this file so that CORE can read and use it?
  119.  
  120. Hopefully that thread linked above on the emanelosscontroller has answered this question.
  121.  
  122. -Jeff
  123.  
  124. From jeffrey.m.ahrenholz at boeing.com Mon Dec 3 14:59:39 2012
  125. From: jeffrey.m.ahrenholz at boeing.com (Ahrenholz, Jeffrey M)
  126. Date: Mon, 3 Dec 2012 11:59:39 -0800
  127. Subject: [core-users] how to setup fixed routing and fixed link loss rate
  128. In-Reply-To: <CA+z2o9sQ4Dv-8UT5Ln8d4XBOvhYE-+dZONfMsGWz6wmN7Fo8CQ@mail.gmail.com>
  129. References: <CA+z2o9sQ4Dv-8UT5Ln8d4XBOvhYE-+dZONfMsGWz6wmN7Fo8CQ@mail.gmail.com>
  130. Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B937B54A4F3A@XCH-NW-12V.nw.nos.boeing.com>
  131.  
  132. Raymond,
  133.  
  134. > 1.If say, two end user, A send a packet to B, the routing is a fixed routing,
  135. > I might dont know the packet route but I do need that two packets sent by A
  136. > destined to B, they travel exactly the same path. (I dont want to use static
  137. > routing, cuz I have many routers to manually configure)
  138.  
  139. Are these nodes moving?
  140.  
  141. > 2. I need to configure the link loss rate, so that it is a fixed value.
  142. > Currently I setup loss rate by "ber" property of a link. I find this problem.
  143. > Suppose all the link ber rate is configured to 1%. And there are 6 hops
  144. > between A and B. I use "iperf -su" to test the link loss rate. Exactly the
  145. > end-to-end loss rate should be 1-(0.99)&^6=5.85%. But the loss rate vibrates
  146. > from 4.1%-6.8%. Is there anyway to may the end-to-end loss rate more stable?
  147.  
  148. Note that it is PER (packet error rate) and not BER (bit error rate) under Linux.
  149.  
  150. The default iperf setting only transmits for 10 seconds. Try a larger -t value, such as '-t 90'. Then you should see more stable loss results. Since the loss incurred by netem is statistical, it is more accurate with more packets, e.g. 10 seconds / 893 packets versus 90 seconds / 8026 packets.
  151.  
  152. Here is the output that I'm seeing; notice the latter three tests (90, 90 and 180 seconds) are closer to your expected loss (mine was also running OSPFv3 that would affect this):
  153.  
  154. Server listening on UDP port 5001
  155. Receiving 1470 byte datagrams
  156. UDP buffer size: 224 KByte (default)
  157. ------------------------------------------------------------
  158. [ 3] local 10.0.0.7 port 5001 connected with 10.0.0.1 port 36792
  159. [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
  160. [ 3] 0.0- 9.8 sec 1.16 MBytes 995 Kbits/sec 0.105 ms 66/ 893 (7.4%)
  161. [ 4] local 10.0.0.7 port 5001 connected with 10.0.0.1 port 50510
  162. [ 4] 0.0-10.3 sec 1.17 MBytes 959 Kbits/sec 15.687 ms 56/ 893 (6.3%)
  163. [ 3] local 10.0.0.7 port 5001 connected with 10.0.0.1 port 40505
  164. [ 3] 0.0-90.3 sec 10.6 MBytes 989 Kbits/sec 15.714 ms 435/ 8026 (5.4%)
  165. [ 4] local 10.0.0.7 port 5001 connected with 10.0.0.1 port 43443
  166. [ 4] 0.0-90.0 sec 10.6 MBytes 991 Kbits/sec 0.055 ms 442/ 8026 (5.5%)
  167. [ 3] local 10.0.0.7 port 5001 connected with 10.0.0.1 port 38397
  168. [ 3] 0.0-180.0 sec 21.2 MBytes 986 Kbits/sec 0.047 ms 960/16051 (6%)
  169.  
  170. -Jeff
  171.  
  172. From JAMES.J.SAMMATARO at saic.com Tue Dec 4 11:29:58 2012
  173. From: JAMES.J.SAMMATARO at saic.com (Sammataro, James J.)
  174. Date: Tue, 4 Dec 2012 11:29:58 -0500
  175. Subject: [core-users] WLAN Range question
  176. Message-ID: <05D35E9CAC2A2F459F83D0C0235074F80690C0D4@0015-its-exmb12.us.saic.com>
  177.  
  178. Hello,
  179.  
  180.  
  181.  
  182. Is it possible, using CORE in a Basic WLAN configuration, to set the
  183. range of one node much greater than the rest? For example, what would
  184. be the best way to set up a scenario where a "UAV" node can connect to
  185. all nodes "on the ground" but the nodes "on the ground" have a range
  186. that is much less than the "UAV" node?
  187.  
  188.  
  189.  
  190. Thank you,
  191.  
  192. James
  193.  
  194.  
  195.  
  196. -------------- next part --------------
  197. An HTML attachment was scrubbed...
  198. URL: http://pf.itd.nrl.navy.mil/pipermail/core-users/attachments/20121204/e9fcf834/attachment.html
  199.  
  200. From pengxu216 at gmail.com Tue Dec 4 18:09:54 2012
  201. From: pengxu216 at gmail.com (xu peng)
  202. Date: Tue, 4 Dec 2012 15:09:54 -0800
  203. Subject: [core-users] about EMANE PHY configuration
  204. Message-ID: <CABEcf7EYu6dwHt95nBsq+XAkDzvu1Zt8aFKDkmGc_1oBgDR8Sg@mail.gmail.com>
  205.  
  206. Hi,
  207.  
  208. How can I get a realistic VANET scenario by configuring the PHY parameters
  209. in EMANE? For example, it can have the realistic connectivity range.
  210.  
  211. If so , how can I adjust the connectivity range? Why the default value of
  212. transmit power and antenna gain are 0? Can signals be transmitted when
  213. they are 0?
  214.  
  215. Thank you,
  216.  
  217. Sissi
  218. -------------- next part --------------
  219. An HTML attachment was scrubbed...
  220. URL: http://pf.itd.nrl.navy.mil/pipermail/core-users/attachments/20121204/84a19d07/attachment.html
  221.  
  222. From alx.mancini at gmail.com Wed Dec 5 11:51:03 2012
  223. From: alx.mancini at gmail.com (Alessandro Mancini)
  224. Date: Wed, 5 Dec 2012 17:51:03 +0100
  225. Subject: [core-users] Range Problem with EMANE
  226. In-Reply-To: <FD98F9C3CBABA74E89B5D4B5DE0263B937B54A4E0E@XCH-NW-12V.nw.nos.boeing.com>
  227. References: <CABSfiGMMO98xX+h4sqSTkys_U8E40p9chv1rJK+xbw59dPkCvw@mail.gmail.com>
  228. <FD98F9C3CBABA74E89B5D4B5DE0263B937B5413288@XCH-NW-12V.nw.nos.boeing.com>
  229. <[email protected]>
  230. <CABSfiGP-xx8yCJycBNOeV6a9pso267+=37xq+gkXbnDY5sHiLA@mail.gmail.com>
  231. <FD98F9C3CBABA74E89B5D4B5DE0263B937B54A4E0E@XCH-NW-12V.nw.nos.boeing.com>
  232. Message-ID: <CABSfiGMdsNafKYJ8mEHoov7PS_xyjDXn0LUaF-3rcpUJ-USvBg@mail.gmail.com>
  233.  
  234. Thank you very much Jeff,
  235. the example that you have used in the previous thread (
  236. http://pf.itd.nrl.navy.mil/pipermail/core-users/2012-November/001096.html)
  237. was very useful for me.
  238. I've following it and I was able to run correctly the EMANE Loss Controller.
  239. Furthermore, I understood the difference between 2ray and pathloss modes
  240. and the difference between location and pathloss events.
  241.  
  242. However, I've two last (I hope so...) questions about Loss Controller:
  243. * I can insert some values relating to the paths between two nodes in
  244. the matrix. How these values are used by EMANE? Are they the values
  245. relative to the pathloss variable that are used in the equation:
  246. rxPower = txPower + txAntennaGain +
  247. rxAntennaGain - pathloss?
  248. * What is the meaning of the values "No Loss Threshold" and "Full Loss
  249. Threshold"? How are they used by EMANE?
  250.  
  251. I'm so grateful for your help so far, and I thank you again in advantage
  252. for your future response.
  253.  
  254. On Mon, Dec 3, 2012 at 6:05 PM, Ahrenholz, Jeffrey M <
  255. jeffrey.m.ahrenholz at boeing.com> wrote:
  256.  
  257. > Alessandro,
  258. >
  259. > > SINR). I also noted that, in your Universal PHY configuration, you use
  260. > > only "2ray" as pathloss mode. May be that CORE can't work with
  261. > > "pathloss" as pathloss mode?
  262. >
  263. > No, CORE can work with either mode; 2ray is just the default used by CORE.
  264. > Configure the mode using the options button on the EMANE tab when you
  265. > configure the WLAN during edit mode. CORE will generate EMANE location
  266. > events when "emane_event_monitor = False" in the core.conf file. CORE does
  267. > not generate pathloss events on its own.
  268. >
  269. > > 1* I would like to know if it is possible to use a pathloss model
  270. > that is
  271. > > based on pathloss events (instead of one that is based on location
  272. > events as
  273. > > 2ray or freespace).
  274. > > If yes, can I do this by using the EMANE Losscontroller? What are the
  275. > steps
  276. > > that I need to perform?
  277. >
  278. > Please see this recent thread:
  279. > http://pf.itd.nrl.navy.mil/pipermail/core-users/2012-November/001077.html
  280. >
  281. > Here's a step-by-step:
  282. > http://pf.itd.nrl.navy.mil/pipermail/core-users/2012-November/001096.html
  283. >
  284. > > 2* Can I use a customized pathloss model? If yes, do I need to use a
  285. > file
  286. > > as "ieee80211abgphy.xml" in which I must insert the values relative to
  287. > the
  288. > > BER curves? And, how can I set this file so that CORE can read and use
  289. > it?
  290. >
  291. > Hopefully that thread linked above on the emanelosscontroller has answered
  292. > this question.
  293. >
  294. > -Jeff
  295. >
  296.  
  297.  
  298.  
  299. --
  300. Alessandro Mancini
  301. -------------- next part --------------
  302. An HTML attachment was scrubbed...
  303. URL: http://pf.itd.nrl.navy.mil/pipermail/core-users/attachments/20121205/6ee64215/attachment.html
  304.  
  305. From jeffrey.m.ahrenholz at boeing.com Wed Dec 5 12:04:18 2012
  306. From: jeffrey.m.ahrenholz at boeing.com (Ahrenholz, Jeffrey M)
  307. Date: Wed, 5 Dec 2012 09:04:18 -0800
  308. Subject: [core-users] Range Problem with EMANE
  309. In-Reply-To: <CABSfiGMdsNafKYJ8mEHoov7PS_xyjDXn0LUaF-3rcpUJ-USvBg@mail.gmail.com>
  310. References: <CABSfiGMMO98xX+h4sqSTkys_U8E40p9chv1rJK+xbw59dPkCvw@mail.gmail.com>
  311. <FD98F9C3CBABA74E89B5D4B5DE0263B937B5413288@XCH-NW-12V.nw.nos.boeing.com>
  312. <[email protected]>
  313. <CABSfiGP-xx8yCJycBNOeV6a9pso267+=37xq+gkXbnDY5sHiLA@mail.gmail.com>
  314. <FD98F9C3CBABA74E89B5D4B5DE0263B937B54A4E0E@XCH-NW-12V.nw.nos.boeing.com>
  315. <CABSfiGMdsNafKYJ8mEHoov7PS_xyjDXn0LUaF-3rcpUJ-USvBg@mail.gmail.com>
  316. Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B937B54A5670@XCH-NW-12V.nw.nos.boeing.com>
  317.  
  318. Alessandro,
  319.  
  320. > * I can insert some values relating to the paths between two nodes in the
  321. > matrix. How these values are used by EMANE? Are they the values relative to
  322. > the pathloss variable that are used in the equation:
  323. > rxPower = txPower + txAntennaGain +
  324. > rxAntennaGain - pathloss?
  325.  
  326. Yes, the pathloss will be the amount of dB subtracted from the receive power. Think of the radio wave travelling across a path that includes going through a building or mountain. The higher the value, the less likely the packet will be received.
  327.  
  328. > * What is the meaning of the values "No Loss Threshold" and "Full Loss
  329. > Threshold"? How are they used by EMANE?
  330.  
  331. These seem to be minimum and maximum values used by the emanelosscontroller tool. I think there should be 0% loss for a given model at the no loss threshold and 100% loss at full loss. I think they are only used in the tool for configuring the pathloss events that are sent out (i.e. they are not necessarily communicated to EMANE or included in a config file.)
  332.  
  333. -Jeff
  334.  
  335. From jeffrey.m.ahrenholz at boeing.com Wed Dec 5 12:09:17 2012
  336. From: jeffrey.m.ahrenholz at boeing.com (Ahrenholz, Jeffrey M)
  337. Date: Wed, 5 Dec 2012 09:09:17 -0800
  338. Subject: [core-users] WLAN Range question
  339. In-Reply-To: <05D35E9CAC2A2F459F83D0C0235074F80690C0D4@0015-its-exmb12.us.saic.com>
  340. References: <05D35E9CAC2A2F459F83D0C0235074F80690C0D4@0015-its-exmb12.us.saic.com>
  341. Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B937B54A5680@XCH-NW-12V.nw.nos.boeing.com>
  342.  
  343. > Is it possible, using CORE in a Basic WLAN configuration, to set the range of
  344. > one node much greater than the rest? For example, what would be the best way
  345. > to set up a scenario where a "UAV" node can connect to all nodes "on the
  346. > ground" but the nodes "on the ground" have a range that is much less than the
  347. > "UAV" node?
  348.  
  349. No, the basic range model doesn't support this.
  350.  
  351. If you want a manual workaround, look at the output of 'ebtables -L'. The default rule for the bridge representing a WLAN network will be to DROP all packets. Then rules are added to enable communication between nodes. Two rules, one for each direction (-i = in, -o = out).
  352.  
  353. For example, here is 3 nodes, all connected together:
  354.  
  355. > sudo ebtables -L
  356. Bridge table: filter
  357.  
  358. Bridge chain: INPUT, entries: 0, policy: ACCEPT
  359.  
  360. Bridge chain: FORWARD, entries: 1, policy: ACCEPT
  361. --logical-in b.4.33974 -j b.4.33974
  362.  
  363. Bridge chain: OUTPUT, entries: 0, policy: ACCEPT
  364.  
  365. Bridge chain: b.4.33974, entries: 6, policy: DROP
  366. -i n3.eth0.50 -o n1.eth0.50 -j ACCEPT
  367. -i n1.eth0.50 -o n3.eth0.50 -j ACCEPT
  368. -i n3.eth0.50 -o n2.eth0.50 -j ACCEPT
  369. -i n2.eth0.50 -o n3.eth0.50 -j ACCEPT
  370. -i n2.eth0.50 -o n1.eth0.50 -j ACCEPT
  371. -i n1.eth0.50 -o n2.eth0.50 -j ACCEPT
  372.  
  373. You could envision a script (e.g. a RUNTIME hook) that inserts ACCEPT rules that allow all nodes to communicate with a certain node. In fact, you could parse the output of 'brctl show' from said script to get a list of interfaces on the WLAN.
  374.  
  375. -Jeff
  376.  
  377. From jeffrey.m.ahrenholz at boeing.com Wed Dec 5 12:18:22 2012
  378. From: jeffrey.m.ahrenholz at boeing.com (Ahrenholz, Jeffrey M)
  379. Date: Wed, 5 Dec 2012 09:18:22 -0800
  380. Subject: [core-users] about EMANE PHY configuration
  381. In-Reply-To: <CABEcf7EYu6dwHt95nBsq+XAkDzvu1Zt8aFKDkmGc_1oBgDR8Sg@mail.gmail.com>
  382. References: <CABEcf7EYu6dwHt95nBsq+XAkDzvu1Zt8aFKDkmGc_1oBgDR8Sg@mail.gmail.com>
  383. Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B937B54A5694@XCH-NW-12V.nw.nos.boeing.com>
  384.  
  385. Sissi,
  386.  
  387. > How can I get a realistic VANET scenario by configuring the PHY parameters in
  388. > EMANE? For example, it can have the realistic connectivity range.
  389. >
  390. > If so , how can I adjust the connectivity range? Why the default value of
  391. > transmit power and antenna gain are 0? Can signals be transmitted when they
  392. > are 0?
  393.  
  394. Not quite sure about the answer to your questions. You could try the emane-users list [1], but I think you will need to have more specifics. What type of radio do you want to emulate? Does a model for such radios exist or can you approximate using RF-PIPE? What kind of antenna(s) would be installed on the vehicles and what kind of connectivity would they offer?
  395.  
  396. The default values used in CORE are the defaults provided by EMANE. You can find documentation on the Universal PHY model here [2].
  397.  
  398. -Jeff
  399.  
  400. [1] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
  401. [2] http://labs.cengen.com/emane/doc/0.7.4/html/universalphy.0.7.3.2.html
  402.  
  403.  
  404. From huangdan226 at gmail.com Fri Dec 7 23:28:04 2012
  405. From: huangdan226 at gmail.com (Dan Huang)
  406. Date: Fri, 7 Dec 2012 23:28:04 -0500
  407. Subject: [core-users] About Running time add router and tunnel
  408. Message-ID: <CACh8YLpW5BKCAMgGa-8T0CPW2CtU-=j39oM2rtsMxBVOZNaFRA@mail.gmail.com>
  409.  
  410. Hi Jeffrey:
  411.  
  412. I have a question about CORE state.
  413. I wanna use CORE's API message to add router in CORE's running time. When I
  414. do this, the new added nodes could show on GUI just like the router set up
  415. before running. The only difference is that there is no routing algorithm
  416. on these running time added routers. I don't know why these happen. Do you
  417. have any idea about this ?
  418.  
  419. Thank you very much
  420.  
  421. Dan
  422. -------------- next part --------------
  423. An HTML attachment was scrubbed...
  424. URL: http://pf.itd.nrl.navy.mil/pipermail/core-users/attachments/20121207/1e177f76/attachment.html
  425.  
  426. From jeffrey.m.ahrenholz at boeing.com Mon Dec 10 11:14:41 2012
  427. From: jeffrey.m.ahrenholz at boeing.com (Ahrenholz, Jeffrey M)
  428. Date: Mon, 10 Dec 2012 08:14:41 -0800
  429. Subject: [core-users] About Running time add router and tunnel
  430. In-Reply-To: <CACh8YLpW5BKCAMgGa-8T0CPW2CtU-=j39oM2rtsMxBVOZNaFRA@mail.gmail.com>
  431. References: <CACh8YLpW5BKCAMgGa-8T0CPW2CtU-=j39oM2rtsMxBVOZNaFRA@mail.gmail.com>
  432. Message-ID: <FD98F9C3CBABA74E89B5D4B5DE0263B937B5514818@XCH-NW-12V.nw.nos.boeing.com>
  433.  
  434. Dan,
  435.  
  436. > I wanna use CORE's API message to add router in CORE's running time. When I
  437. > do this, the new added nodes could show on GUI just like the router set up
  438. > before running. The only difference is that there is no routing algorithm on
  439. > these running time added routers. I don't know why these happen. Do you have
  440. > any idea about this ?
  441.  
  442. Routing is enabled by the services configured for a node. The services are not being started when you send Node Messages at runtime with the add flag.
  443.  
  444. You can add a default node type with a model of router, and you would get the default Quagga OSPFv2/v3 routing. However, currently the services for a node are only started from Session.bootnodes(), which is called from Session.instantiate() when the GUI puts the session into instantiation mode.
  445.  
  446. -Jeff
  447.  
  448.  
  449.  
  450.  
  451. Archive View by: Downloadable version
  452. December 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 6 KB ]
  453. November 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 24 KB ]
  454. October 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 6 KB ]
  455. September 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 10 KB ]
  456. August 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 16 KB ]
  457. July 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 22 KB ]
  458. June 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 16 KB ]
  459. May 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 10 KB ]
  460. April 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 5 KB ]
  461. March 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 14 KB ]
  462. February 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 13 KB ]
  463. January 2012: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 10 KB ]
  464. December 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 10 KB ]
  465. November 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 5 KB ]
  466. October 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 7 KB ]
  467. September 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 15 KB ]
  468. August 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 20 KB ]
  469. July 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 14 KB ]
  470. June 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 15 KB ]
  471. May 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 27 KB ]
  472. April 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 8 KB ]
  473. March 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 13 KB ]
  474. February 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 5 KB ]
  475. January 2011: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 7 KB ]
  476. December 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 9 KB ]
  477. November 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 18 KB ]
  478. October 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 12 KB ]
  479. September 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 21 KB ]
  480. August 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 19 KB ]
  481. July 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 5 KB ]
  482. June 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 11 KB ]
  483. May 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 6 KB ]
  484. April 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 13 KB ]
  485. March 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 3 KB ]
  486. February 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 5 KB ]
  487. January 2010: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 2 KB ]
  488. December 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 3 KB ]
  489. November 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 16 KB ]
  490. October 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 3 KB ]
  491. September 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 3 KB ]
  492. August 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 6 KB ]
  493. July 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 9 KB ]
  494. June 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 3 KB ]
  495. May 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 6 KB ]
  496. April 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 1 KB ]
  497. March 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 1 KB ]
  498. February 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 2 KB ]
  499. January 2009: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 3 KB ]
  500. December 2008: [ Thread ] [ Subject ] [ Author ] [ Date ] [ Gzip'd Text 478 bytes ]
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!