From ioannoa at scss.tcd.ie Wed Mar 5 06:57:09 2014 From: ioannoa at scss.tcd.ie (ioannoa at scss.tcd.ie) Date: Wed, 5 Mar 2014 14:57:09 -0000 Subject: [ndnSIM] [Fwd: Producer/Consumer implementation] Message-ID: <2e9033b922b19618a3f01d6e07c33c7c.squirrel@webmail.scss.tcd.ie> Hello everyone, I am trying to implement a scenario, where i want my catalog of objects to follow a specific distribution regarding the size. e.g. a catalog size of 100 objects with a mean size of 1000 chunks following some distribution x. Would someone be able to advice me how to implement something like that, as at the moment the consumer really defines the contents characteristics using e.g. MaxSeq. In contrast the app of the producer only just replies to whatever request it receives. My biggest confusion is if each object varies in size, how can a consumer send requests only until the object is retrieved? My thought is, the producer holds a table with the size of each object. It then divides this size with 1024 so as to conclude to how many packets each object would correspond to. Then it keeps this so as to inform the consumer when the say last prefix/j is retrieved. Any better ideas? Kind regards, Andriana. From liuzongzhen at cstnet.cn Wed Mar 5 19:15:41 2014 From: liuzongzhen at cstnet.cn (=?GBK?B?wfXX3NXm?=) Date: Thu, 6 Mar 2014 11:15:41 +0800 (GMT+08:00) Subject: [ndnSIM] A problem about the protocol header in packets Message-ID: <1668727.14a3f.1449563acc6.Coremail.liuzongzhen@cstnet.cn> Hi Alex, I am trying to implement a scenario, where I want my mobile node to hand off between different access points. Before handing off, there are no problems. But after handing off, the pcap packets don't include internet protocol and transmission control protocol, just include logical-link control header and the type of which is unknown (0x7777). I am using the newest version of NS3 and ndnSIM. Besides, I utilize ndn::GlobleRoutingHelper to calculate the routes. Is there any possible solutions? Thanks a lot! Looking forward to your response. ------------------- Liu Zongzhen Beijing, China -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From sandhya.giri18 at gmail.com Thu Mar 6 23:11:55 2014 From: sandhya.giri18 at gmail.com (Sandhya Giri) Date: Fri, 7 Mar 2014 12:41:55 +0530 Subject: [ndnSIM] m_receivedDatas Message-ID: Dear sir, I want to check whether a data packet has been received for an interest packet previously sent. So, can you tell me how i can read from m_receivedDatas?? thanks and regards Sandhya -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Tue Mar 11 13:40:28 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Tue, 11 Mar 2014 13:40:28 -0700 Subject: [ndnSIM] Help In-Reply-To: References: <4E814160-12D5-4998-A73D-7AE549C9A6D8@ucla.edu>

Message-ID: <676A168B-CC15-48DE-80C0-AF53AFA7FB6B@ucla.edu> Hi again, I have added explanation of columns to http://ndnsim.net/metric.html --- Alex On Mar 10, 2014, at 8:55 AM, connos symeon wrote: > I have manage to do that and i understand one or two columns in that specific file. Can you explain me what are the meaning of all columns please? > > > On Sun, Mar 9, 2014 at 11:38 AM, Alex Afanasyev wrote: > The result is that on all nodes there will be L3AggregaeTracer installed and all trace will be written into the specified file. > > (Behind the scenes, there are several global variables that hold tracer instances.) > > --- > Alex > > On Mar 9, 2014, at 9:31 AM, connos symeon wrote: > >> Hello Alex, >> >> Now i understood what you said and i managed to solve my problem. Thank you for your help. I have another question if you can help me. Can you tell me what exactly are the results of ndn::L3AggregateTracer::InstallAll ? >> >> Thanks, >> Constantinos Symeonides >> >> >> On Wed, Mar 5, 2014 at 1:03 PM, Alex Afanasyev wrote: >> Hi Constantinos, >> >> This specific scenario is using ndn::GlobalRoutingController. So, to control which route is preferred, you need to adjust (add) cost metrics for each link. ndn::GlobalRoutingController then will take this cost into account when runs Dijkstra algorithm (smaller cost wins). >> >> --- >> Alex >> >> On Mar 5, 2014, at 10:33 AM, connos symeon wrote: >> >> > Mr. Alex, >> > >> > Hello, i have a question about ndnSIM. In the ndn-grid-topo-plugin i understood that the interest packet is going to a specific route from node0 to 1 to 4 to 7 and finally to 8. How can i change this route? For example from node0 to 1 to 2 to 5 and then to 8? >> > >> > Thanks in advance, >> > Constantinos Symeonides >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ali_limem2006 at hotmail.com Thu Mar 13 01:34:06 2014 From: ali_limem2006 at hotmail.com (AL IMEM ALI) Date: Thu, 13 Mar 2014 08:34:06 +0000 Subject: [ndnSIM] Signature Message-ID: HI ALEX my strategy is to implement new signature algorithms like RSA , DSA .... in the signature field related to NDN packet could you help me please , or give me an idea to implement such a method. Best Wishes AL IMEM ALI -------------- next part -------------- An HTML attachment was scrubbed... URL: From afanasev at cs.ucla.edu Thu Mar 13 16:17:24 2014 From: afanasev at cs.ucla.edu (Alex Afanasyev) Date: Thu, 13 Mar 2014 16:17:24 -0700 Subject: [ndnSIM] A question about ndnSIM (hope for answer) In-Reply-To: References: Message-ID: On Mar 13, 2014, at 2:17 AM, ??? wrote: > Hello, Alex! > I asked you question over the last year and thanks for your patience to answer. > Now, I have another question about ndnSIM. I hope that you can help me. > I use "AppDelayTracer" to obtain "hopcount". > There's description on ndnsim.net which is "One consequence is that Interests satisfied by an app will have even hop count (min hop count = 2), and Interests satisfied from caches will have odd hop count (min hop count = 1)" > > In my experiment > The number of hopcount under the path "consumer-router-router-producer" is 8. Why isn't 6(=3*2)? I don't know why there's extra two hops. > The number of hopcount under the path "consumer-router(with cache)" is 3. Why isn't 2(=1*2)? I don't know why there's extra one hop. Do I understand correctly that in the above path, each element represent a physical node? If so, you forgot to calculate in application contribution to hop count. When application sends out interest/data, hop count is not increased (send out is done via an appFace callback), when application receives interest/data, hop count **is** increased. --- Alex > > Do you know how to explain the number of hopcount? > I am looking forward to your reply. > Thank you so much for reading my email. > > --Fanyun Zou > Peking University From alexander.afanasyev at ucla.edu Thu Mar 13 16:21:22 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 13 Mar 2014 16:21:22 -0700 Subject: [ndnSIM] Signature In-Reply-To: References: Message-ID: <59FEC337-1E39-48EB-9727-546655A09B97@ucla.edu> Hi Al, Would you mind explaining what you're trying to achieve by implementing such algorithms inside the simulator? Many security-related things can be simulated in NS-3/ndnSIM without implementing actual signature algorithms. -- Alex On Mar 13, 2014, at 1:34 AM, AL IMEM ALI wrote: > HI ALEX > > my strategy is to implement new signature algorithms like RSA , DSA .... in the signature field related to NDN packet could you help me please , or give me an idea to implement such a method. > Best Wishes > > AL IMEM ALI > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Thu Mar 13 16:25:27 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 13 Mar 2014 16:25:27 -0700 Subject: [ndnSIM] m_receivedDatas In-Reply-To: References: Message-ID: <53E67A98-23EA-429E-BCBE-8E3DFAB10F37@ucla.edu> Hi Sandhya, m_receivedDatas is a TracedCallback, not a container. You can connect to this callback and receive notification whenever Data packet is received, but you would need to implement your own logic to connect Interest and Data packets. Do you need to do this check in real time? If not, you may be able to use AppDelayTracer (http://ndnsim.net/metric.html#application-level-trace-helper), which tries to do such matching automatically. --- Alex On Mar 6, 2014, at 11:11 PM, Sandhya Giri wrote: > Dear sir, > > I want to check whether a data packet has been received for an interest packet previously sent. So, can you tell me how i can read from m_receivedDatas?? > > thanks and regards > > Sandhya > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From ali_limem2006 at hotmail.com Thu Mar 13 21:24:59 2014 From: ali_limem2006 at hotmail.com (AL IMEM ALI) Date: Fri, 14 Mar 2014 00:24:59 -0400 Subject: [ndnSIM] Signature Message-ID: i wanna see the diffrences between merkle hash trees and ecdsa and also RSA and test signature verification to achieve integrity ! if there is another way could you tell me about it ? Sent from my ASUS MeMO Pad AL IMEM ALI wrote: HI ALEX my strategy is to implement new signature algorithms like RSA , DSA .... in the signature field related to NDN packet could you help me please , or give me an idea to implement such a method. Best Wishes AL IMEM ALI -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Thu Mar 13 16:30:17 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 13 Mar 2014 16:30:17 -0700 Subject: [ndnSIM] Signature In-Reply-To: References: Message-ID: <1E1BD156-CC8F-445D-AE98-B79DB57AD5AE@ucla.edu> What kind of difference? Don't forget that in the simulator all operations are performed in simulated, not real time. And all method calls are finished within 0 simulation time. Therefore, if you're planning to measure time complexity of algorithms, the simulator wouldn't give you much. Again, if the objective is to do time complexity analysis, I would recommend making a non-simulated implementation. You can check out ndn-cpp-dev library (https://github.com/named-data/ndn-cpp-dev) for that. --- Alex On Mar 13, 2014, at 9:24 PM, AL IMEM ALI wrote: > i wanna see the diffrences between merkle hash trees and ecdsa and also RSA and test signature verification to achieve integrity ! if there is another way could you tell me about it ? > > Sent from my ASUS MeMO Pad > > AL IMEM ALI wrote: > > HI ALEX > > my strategy is to implement new signature algorithms like RSA , DSA .... in the signature field related to NDN packet could you help me please , or give me an idea to implement such a method. > Best Wishes > > AL IMEM ALI -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Thu Mar 13 16:31:26 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 13 Mar 2014 16:31:26 -0700 Subject: [ndnSIM] A problem about the protocol header in packets In-Reply-To: <1668727.14a3f.1449563acc6.Coremail.liuzongzhen@cstnet.cn> References: <1668727.14a3f.1449563acc6.Coremail.liuzongzhen@cstnet.cn> Message-ID: <71B1C366-F13C-43C8-9AC8-286C5444CDE7@ucla.edu> Hi Liu, It would be helpful if you can give a very basic scenario that can reproduce the problem. Normally, in ndnSIM you don't run on top of IP. It is possible, but in most of the examples on ndnsim.net, NDN is run directly on top of PPP protocol with 0x7777 protocol number. --- Alex On Mar 5, 2014, at 7:15 PM, ??? wrote: > Hi Alex, > > I am trying to implement a scenario, where I want my mobile node to hand off between different access points. Before handing off, there are no problems. But after handing off, the pcap packets don't include internet protocol and transmission control protocol, just include logical-link control header and the type of which is unknown (0x7777). I am using the newest version of NS3 and ndnSIM. Besides, I utilize ndn::GlobleRoutingHelper to calculate the routes. > > Is there any possible solutions? Thanks a lot! > > Looking forward to your response. > > ------------------- > Liu Zongzhen > > Beijing, China > > > > -- > > > > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim From alexander.afanasyev at ucla.edu Thu Mar 13 16:34:47 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 13 Mar 2014 16:34:47 -0700 Subject: [ndnSIM] How does the fib limit be initialized with per-pit-limit forwarding strategy In-Reply-To: <3c00b768.1cc13.14477d50301.Coremail.leshuyuan@163.com> References: <3c00b768.1cc13.14477d50301.Coremail.leshuyuan@163.com> Message-ID: <9D921364-742E-44BB-96CD-D37789A19CE0@ucla.edu> Unfortunately, the current implementation does not have any helpers to set the limit. After you create your topology and set up FIB, you would need to manually go over all FIB records and set up the proper limits. --- Alex On Feb 28, 2014, at 1:30 AM, ??? wrote: > Hi all, > Sorry for my mistake in my last email. > My question is how does the fib limit be initialized. > I've looked into the ndn-stack-helper.cc and I found the face limit was initialized in method StackHelper::PointToPointNetDeviceCallback. But I have no ideal about how does fib limit be initailized. > > > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From ali_limem2006 at hotmail.com Thu Mar 13 21:35:17 2014 From: ali_limem2006 at hotmail.com (AL IMEM ALI) Date: Fri, 14 Mar 2014 00:35:17 -0400 Subject: [ndnSIM] Signature Message-ID: you said many security-related things can be simulated without implementig actual signature algorithms could you give me an idea ? Sent from my ASUS MeMO Pad Alex Afanasyev wrote: Hi Al, Would you mind explaining what you're trying to achieve by implementing such algorithms inside the simulator? Many security-related things can be simulated in NS-3/ndnSIM without implementing actual signature algorithms. -- Alex On Mar 13, 2014, at 1:34 AM, AL IMEM ALI wrote: > HI ALEX > > my strategy is to implement new signature algorithms like RSA , DSA .... in the signature field related to NDN packet could you help me please , or give me an idea to implement such a method. > Best Wishes > > AL IMEM ALI > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Thu Mar 13 16:38:11 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 13 Mar 2014 16:38:11 -0700 Subject: [ndnSIM] PIT size In-Reply-To: References: Message-ID: Hi Mohammad, An excessive DropData could be a result of the way you set up the limit. You didn't show the detail, but if you have used "Lru" policy for the limit, then this would be the core problem---whenever limit is reached, you would evict an older entry, instead of keeping it and rejecting new interest. I suspect that you will get more reasonable results if you change to "Persistent" policy (which is actually a default). --- Alex On Feb 26, 2014, at 5:43 AM, Hovaidi Ardestani Mohammad wrote: > Hi all, > I have a basic question about PIT size and its role to control the traffic flow. > > In my scenario when I change the PIT size into the lower value, the result shows more DropData. > I reckon the small size of PIT means the small number of data requests and consequently the small number of DropData but large number of InterestData. Is It so? > On the other hand, when PIT overflows, we would expect an increase rate of retransmissons from the downstream nodes. What would be the role of increasing retransmission rate on the packet drops both on layer 2 and 3. > > I really appreciate your response in advance! > -Mohammad > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Thu Mar 13 16:40:48 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 13 Mar 2014 16:40:48 -0700 Subject: [ndnSIM] Signature In-Reply-To: References: Message-ID: <263A1488-90D8-45B4-B9D3-BBD5B03D2E4B@ucla.edu> It all depends on what is your plan. What I meant is that in the simulator you always know who is the good guy and who is the attacker. All "corrupted" or incorrectly signed Datas can simply be represented by an "evil bit" and the verification process can be a matter of checking the evil bit. --- Alex On Mar 13, 2014, at 9:35 PM, AL IMEM ALI wrote: > you said many security-related things can be simulated without implementig actual signature algorithms could you give me an idea ? > > Sent from my ASUS MeMO Pad > > Alex Afanasyev wrote: > > Hi Al, > > Would you mind explaining what you're trying to achieve by implementing such algorithms inside the simulator? Many security-related things can be simulated in NS-3/ndnSIM without implementing actual signature algorithms. > > -- > Alex > > On Mar 13, 2014, at 1:34 AM, AL IMEM ALI wrote: > >> HI ALEX >> >> my strategy is to implement new signature algorithms like RSA , DSA .... in the signature field related to NDN packet could you help me please , or give me an idea to implement such a method. >> Best Wishes >> >> AL IMEM ALI >> _______________________________________________ >> ndnSIM mailing list >> ndnSIM at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim > > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Thu Mar 13 16:44:03 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 13 Mar 2014 16:44:03 -0700 Subject: [ndnSIM] Help needed on ndnSIM In-Reply-To: References: Message-ID: On Mar 12, 2014, at 10:28 PM, Samiuddin Mohammed wrote: > Hi Alex, > > I got your email from Github. I am a student at UALR and doing my project using ndnSIM and I would like to improve upon this paper "A lightweight mechanism for detection of cache pollution attacks in named data networking". > > I am a beginner in using ndnSIM and I have a problem in compiling a modified example. > > The commands: > cd > ./waf configure --enable-examples > ./waf > > are compiling without errors but I am not getting the new modified output. I am still getting same output which example program has. > > Could you please help me with this issue? Did you by any chance copied the example to scratch/ folder and modified it there? If so, you just need to rename your scenario and then use the new name to run it. --- Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From ali_limem2006 at hotmail.com Thu Mar 13 21:47:20 2014 From: ali_limem2006 at hotmail.com (AL IMEM ALI) Date: Fri, 14 Mar 2014 00:47:20 -0400 Subject: [ndnSIM] Signature Message-ID: if we are talking about signature privacy , which tools are used to check content integrity ? Sent from my ASUS MeMO Pad Alex Afanasyev wrote: It all depends on what is your plan. What I meant is that in the simulator you always know who is the good guy and who is the attacker. All "corrupted" or incorrectly signed Datas can simply be represented by an "evil bit" and the verification process can be a matter of checking the evil bit. --- Alex On Mar 13, 2014, at 9:35 PM, AL IMEM ALI wrote: > you said many security-related things can be simulated without implementig actual signature algorithms could you give me an idea ? > > Sent from my ASUS MeMO Pad > > Alex Afanasyev wrote: > > Hi Al, > > Would you mind explaining what you're trying to achieve by implementing such algorithms inside the simulator? Many security-related things can be simulated in NS-3/ndnSIM without implementing actual signature algorithms. > > -- > Alex > > On Mar 13, 2014, at 1:34 AM, AL IMEM ALI wrote: > >> HI ALEX >> >> my strategy is to implement new signature algorithms like RSA , DSA .... in the signature field related to NDN packet could you help me please , or give me an idea to implement such a method. >> Best Wishes >> >> AL IMEM ALI >> _______________________________________________ >> ndnSIM mailing list >> ndnSIM at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim > > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From stmohammed at ualr.edu Fri Mar 14 02:29:47 2014 From: stmohammed at ualr.edu (Samiuddin Mohammed) Date: Fri, 14 Mar 2014 04:29:47 -0500 Subject: [ndnSIM] Help needed on ndnSIM In-Reply-To: References:

Message-ID: Alex, I solved it. I had same name scenario in ns-3 and scratch folder. One of them was old file. I think that was the issue. Thanks for your help. And, Is there a way to color nodes in the output shown on python visualizer? Like if I want to colour all consumer nodes in one, all producers in another? How do I do that? On Thu, Mar 13, 2014 at 6:44 PM, Alex Afanasyev < alexander.afanasyev at ucla.edu> wrote: > > On Mar 12, 2014, at 10:28 PM, Samiuddin Mohammed > wrote: > > Hi Alex, > > I got your email from Github. I am a student at UALR and doing my project > using ndnSIM and I would like to improve upon this paper "A lightweight > mechanism for detection of cache pollution attacks in named data > networking". > > I am a beginner in using ndnSIM and I have a problem in compiling a > modified example. > > The commands: > > > *cd ./waf configure --enable-examples* > > *./waf * > > are compiling without errors but I am not getting the new modified output. > I am still getting same output which example program has. > > Could you please help me with this issue? > > > Did you by any chance copied the example to scratch/ folder and modified > it there? If so, you just need to rename your scenario and then use the > new name to run it. > > --- > Alex > > -- Regards, Samiuddin -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Fri Mar 14 10:08:16 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Fri, 14 Mar 2014 10:08:16 -0700 Subject: [ndnSIM] Help needed on ndnSIM In-Reply-To: References:

Message-ID: On Mar 14, 2014, at 2:29 AM, Samiuddin Mohammed wrote: > Alex, I solved it. I had same name scenario in ns-3 and scratch folder. One of them was old file. I think that was the issue. Thanks for your help. > > And, Is there a way to color nodes in the output shown on python visualizer? Like if I want to colour all consumer nodes in one, all producers in another? How do I do that? Unfortunately, I don't know an easy way to do this. You may want to explore source code of ns-3 visualizer (it is in python) or ask NS-3 guys (e.g., pyviz developers) directly... --- Alex > On Thu, Mar 13, 2014 at 6:44 PM, Alex Afanasyev wrote: > > On Mar 12, 2014, at 10:28 PM, Samiuddin Mohammed wrote: > >> Hi Alex, >> >> I got your email from Github. I am a student at UALR and doing my project using ndnSIM and I would like to improve upon this paper "A lightweight mechanism for detection of cache pollution attacks in named data networking". >> >> I am a beginner in using ndnSIM and I have a problem in compiling a modified example. >> >> The commands: >> cd >> ./waf configure --enable-examples >> ./waf >> >> are compiling without errors but I am not getting the new modified output. I am still getting same output which example program has. >> >> Could you please help me with this issue? > > Did you by any chance copied the example to scratch/ folder and modified it there? If so, you just need to rename your scenario and then use the new name to run it. > > --- > Alex > > > > > -- > Regards, > Samiuddin -------------- next part -------------- An HTML attachment was scrubbed... URL: From ali_limem2006 at hotmail.com Sat Mar 15 05:44:41 2014 From: ali_limem2006 at hotmail.com (AL IMEM ALI) Date: Sat, 15 Mar 2014 12:44:41 +0000 Subject: [ndnSIM] Sign a packet Message-ID: Dear Alex you gave me a way to verify the packet , but you could you give me a way to sign the packet ? Best Wishes AL IMEM ALI -------------- next part -------------- An HTML attachment was scrubbed... URL: From ioannoa at scss.tcd.ie Thu Mar 20 05:54:41 2014 From: ioannoa at scss.tcd.ie (ioannoa at scss.tcd.ie) Date: Thu, 20 Mar 2014 12:54:41 -0000 Subject: [ndnSIM] sample-topologies Message-ID: Hello everyone, I was currently looking at the sample topologies from Rocketfuel included into the same named directory for real-topology simulations. However, I was not able to link the sample topologies with the known paper of: " Measuring ISP topologies with Rocketfuel". The ASes seem to have different number of nodes, either concerning routers or PoPs. Does anyone have an idea of how these topologies have been concluded in ndnsim and what exactly each node, i.e. blue, green, red represents? My assumption is that blue nodes are backbone nodes, green nodes are gateway nodes and red nodes are local Points of Presence where clients are connected to. Please, keep me informed if you have any ideas on it. Kind regards, Andriana. From alexander.afanasyev at ucla.edu Thu Mar 20 12:58:32 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 20 Mar 2014 12:58:32 -0700 Subject: [ndnSIM] sample-topologies In-Reply-To: References: Message-ID: Hi Andriana, The project that you're referring provides only partial information that can be used in simulation scenarios. In particular, there were no delays and link bandwidths. What we basically did is defined a basic heuristic to classify nodes into different classes (clients, gateways, and backbones---these what colors represent) and randomly assigned delays and bandwidths based on the classification. Again, all these processing has no relation to the original Rocketfuel project, but provides some topology that can be used in the simulation, that has certain real-world characteristics (though not exact). Depending on the simulation scenario you're working on, you may need to change heuristic or try to use some other topology... For the definition of the heuristic, check the https://github.com/cawka/ndnSIM-sample-topologies/blob/master/scenarios/rocketfuel-maps-cch-to-annotaded.cc source. --- Alex On Mar 20, 2014, at 5:54 AM, ioannoa at scss.tcd.ie wrote: > Hello everyone, > > I was currently looking at the sample topologies from Rocketfuel included > into the same named directory for real-topology simulations. > > However, I was not able to link the sample topologies with the known paper > of: > " Measuring ISP topologies with Rocketfuel". The ASes seem to have > different number of nodes, either concerning routers or PoPs. > > Does anyone have an idea of how these topologies have been concluded in > ndnsim and what exactly each node, i.e. blue, green, red represents? My > assumption is that blue nodes are backbone nodes, green nodes are gateway > nodes and red nodes are local Points of Presence where clients are > connected to. > > Please, keep me informed if you have any ideas on it. > > Kind regards, > Andriana. > > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim From ali_limem2006 at hotmail.com Sat Mar 22 09:25:08 2014 From: ali_limem2006 at hotmail.com (AL IMEM ALI) Date: Sat, 22 Mar 2014 16:25:08 +0000 Subject: [ndnSIM] Urgent Message-ID: Dear Sir. I read about the new NDN packet format and in the signature block i read about signature types : i was wondering if i could use one of the values to attach a new algorithms such as merkle trees or ecdsa to sign a packet over ndnSIM Value Reference Description 0 DigestSha256 Integrity protection using SHA-256 digest 1 SignatureSha256WithRsa Integrity and provenance protection using RSA signature over a SHA-256 digest 2-200 reserved for future assignments >200 unassigned Best Wishes AL IMEM ALI -------------- next part -------------- An HTML attachment was scrubbed... URL: From liuzongzhen at cstnet.cn Sun Mar 23 20:04:47 2014 From: liuzongzhen at cstnet.cn (=?GBK?B?wfXX3NXm?=) Date: Mon, 24 Mar 2014 11:04:47 +0800 (GMT+08:00) Subject: [ndnSIM] A problem about the protocol header in packets Message-ID: <1cd3307.22e.144f20c2b04.Coremail.liuzongzhen@cstnet.cn> Hi Alex, Thank you very much for your reply! In my scenario, there are several NDN nodes, two AP nodes and one mobile Sta node. The Sta node handover between the two AP nodes. Firstly I use ndn::GlobleRoutingHelper to calculate the routes before simulation. When the Sta node connect to the first AP and to the corresponding NDN node with TCP connection. All are right. But when the Sta node walks and connects to the second AP node and fetch contents, in the pcap file from the Sta node, the type of the packets is LLC , instead TCP. In addition, I find if I use ndn::GlobleRoutingHelper to calculate the routes, the hop of shortest path between two NDN nodes, the algorithm also consider the wifi path, not just the p2p path. Looking forward to your response. Thank you very much for your help! ----------------------- Zongzhen Liu Beijing, China -------------- next part -------------- An HTML attachment was scrubbed... URL: From torjemen at topnet.tn Mon Mar 24 14:46:18 2014 From: torjemen at topnet.tn (Nabil Torjemen / Topnet) Date: Mon, 24 Mar 2014 22:46:18 +0100 Subject: [ndnSIM] Compilation Error Message-ID: <002701cf47aa$7ec07bf0$7c4173d0$@tn> Dear Sir, When I'm trying to compile ndnSIM, I get the following error as output: [1255/1996] cxx: build/src/lte/bindings/ns3module.cc -> build/src/lte/bindings/ns3module.cc.7.o In file included from src/lte/bindings/ns3module.cc:1:0: src/lte/bindings/ns3module.h:6857:5: erreur: 'UeMeasure' in namespace 'ns3' does not name a type src/lte/bindings/ns3module.h:9210:5: erreur: 'NeighbourRelation' in namespace 'ns3' does not name a type src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3UeManager_RecvUeContextRelease(PyNs3UeManager*, PyObject*, PyObject*)': src/lte/bindings/ns3module.cc:84753:16: erreur: 'class ns3::UeManager' has no member named 'RecvUeContextRelease' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3UeMeasure__get_m_cellId(PyNs3UeMeasure*, void*)': src/lte/bindings/ns3module.cc:85316:51: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3UeMeasure__set_m_cellId(PyNs3UeMeasure*, PyObject*, void*)': src/lte/bindings/ns3module.cc:85334:11: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3UeMeasure__get_m_rsrp(PyNs3UeMeasure*, void*)': src/lte/bindings/ns3module.cc:85342:56: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3UeMeasure__set_m_rsrp(PyNs3UeMeasure*, PyObject*, void*)': src/lte/bindings/ns3module.cc:85360:11: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3UeMeasure__get_m_rsrq(PyNs3UeMeasure*, void*)': src/lte/bindings/ns3module.cc:85368:56: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3UeMeasure__set_m_rsrq(PyNs3UeMeasure*, PyObject*, void*)': src/lte/bindings/ns3module.cc:85386:11: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3UeMeasure__tp_init__0(PyNs3UeMeasure*, PyObject*, PyObject*, PyObject**)': src/lte/bindings/ns3module.cc:85430:11: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc:85430:21: erreur: expected type-specifier src/lte/bindings/ns3module.cc:85430:21: erreur: expected ';' src/lte/bindings/ns3module.cc:85431:11: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc:85432:34: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3UeMeasure__tp_init__1(PyNs3UeMeasure*, PyObject*, PyObject*, PyObject**)': src/lte/bindings/ns3module.cc:85452:11: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc:85452:21: erreur: expected type-specifier src/lte/bindings/ns3module.cc:85452:21: erreur: expected ';' src/lte/bindings/ns3module.cc:85453:11: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc:85454:34: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3UeMeasure__copy__(PyNs3UeMeasure*)': src/lte/bindings/ns3module.cc:85492:14: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc:85492:24: erreur: expected type-specifier src/lte/bindings/ns3module.cc:85492:24: erreur: expected ';' src/lte/bindings/ns3module.cc:85495:56: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'void PyNs3UeMeasure__tp_clear(PyNs3UeMeasure*)': src/lte/bindings/ns3module.cc:85508:15: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc:85509:5: erreur: 'UeMeasure' is not a member of 'ns3' src/lte/bindings/ns3module.cc:85509:21: erreur: 'tmp' was not declared in this scope src/lte/bindings/ns3module.cc:85509:33: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc:85510:11: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'void _wrap_PyNs3UeMeasure__tp_dealloc(PyNs3UeMeasure*)': src/lte/bindings/ns3module.cc:85529:80: erreur: 'struct PyNs3UeMeasure' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3LteEnbRrc_HandoverLeavingTimeout(PyNs3LteEnbRrc*, PyObject*, PyObject*)': src/lte/bindings/ns3module.cc:98486:16: erreur: 'class ns3::LteEnbRrc' has no member named 'HandoverLeavingTimeout' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3LteEnbRrc_ConnectionRejectedTimeout(PyNs3LteEnbRrc*, PyObject*, PyObject*)': src/lte/bindings/ns3module.cc:98530:16: erreur: 'class ns3::LteEnbRrc' has no member named 'ConnectionRejectedTimeout' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3LteEnbRrc_HandoverJoiningTimeout(PyNs3LteEnbRrc*, PyObject*, PyObject*)': src/lte/bindings/ns3module.cc:98582:16: erreur: 'class ns3::LteEnbRrc' has no member named 'HandoverJoiningTimeout' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3LteEnbRrc_AddX2Neighbour(PyNs3LteEnbRrc*, PyObject*, PyObject*)': src/lte/bindings/ns3module.cc:98773:16: erreur: 'class ns3::LteEnbRrc' has no member named 'AddX2Neighbour' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3LteHelper_GetSchedulerType(PyNs3LteHelper*)': src/lte/bindings/ns3module.cc:101868:25: erreur: 'class ns3::LteHelper' has no member named 'GetSchedulerType' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3NeighbourRelation__get_m_detectedAsNeighbour(PyNs3NeighbourRelati on*, void*)': src/lte/bindings/ns3module.cc:118762:67: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3NeighbourRelation__set_m_detectedAsNeighbour(PyNs3NeighbourRelati on*, PyObject*, void*)': src/lte/bindings/ns3module.cc:118775:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3NeighbourRelation__get_m_noHo(PyNs3NeighbourRelation*, void*)': src/lte/bindings/ns3module.cc:118783:67: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3NeighbourRelation__set_m_noHo(PyNs3NeighbourRelation*, PyObject*, void*)': src/lte/bindings/ns3module.cc:118796:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3NeighbourRelation__get_m_noRemove(PyNs3NeighbourRelation*, void*)': src/lte/bindings/ns3module.cc:118804:67: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3NeighbourRelation__set_m_noRemove(PyNs3NeighbourRelation*, PyObject*, void*)': src/lte/bindings/ns3module.cc:118817:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3NeighbourRelation__get_m_noX2(PyNs3NeighbourRelation*, void*)': src/lte/bindings/ns3module.cc:118825:67: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3NeighbourRelation__set_m_noX2(PyNs3NeighbourRelation*, PyObject*, void*)': src/lte/bindings/ns3module.cc:118838:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3NeighbourRelation__get_m_physCellId(PyNs3NeighbourRelation*, void*)': src/lte/bindings/ns3module.cc:118846:51: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3NeighbourRelation__set_m_physCellId(PyNs3NeighbourRelation*, PyObject*, void*)': src/lte/bindings/ns3module.cc:118864:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3NeighbourRelation__tp_init__0(PyNs3NeighbourRelation*, PyObject*, PyObject*, PyObject**)': src/lte/bindings/ns3module.cc:118922:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc:118922:21: erreur: expected type-specifier src/lte/bindings/ns3module.cc:118922:21: erreur: expected ';' src/lte/bindings/ns3module.cc:118923:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc:118924:34: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'int _wrap_PyNs3NeighbourRelation__tp_init__1(PyNs3NeighbourRelation*, PyObject*, PyObject*, PyObject**)': src/lte/bindings/ns3module.cc:118944:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc:118944:21: erreur: expected type-specifier src/lte/bindings/ns3module.cc:118944:21: erreur: expected ';' src/lte/bindings/ns3module.cc:118945:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc:118946:34: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'PyObject* _wrap_PyNs3NeighbourRelation__copy__(PyNs3NeighbourRelation*)': src/lte/bindings/ns3module.cc:118984:14: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc:118984:24: erreur: expected type-specifier src/lte/bindings/ns3module.cc:118984:24: erreur: expected ';' src/lte/bindings/ns3module.cc:118987:56: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'void PyNs3NeighbourRelation__tp_clear(PyNs3NeighbourRelation*)': src/lte/bindings/ns3module.cc:119000:15: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc:119001:5: erreur: 'NeighbourRelation' is not a member of 'ns3' src/lte/bindings/ns3module.cc:119001:29: erreur: 'tmp' was not declared in this scope src/lte/bindings/ns3module.cc:119001:41: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc:119002:11: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'void _wrap_PyNs3NeighbourRelation__tp_dealloc(PyNs3NeighbourRelation*)': src/lte/bindings/ns3module.cc:119021:80: erreur: 'struct PyNs3NeighbourRelation' has no member named 'obj' src/lte/bindings/ns3module.cc: In function 'void initlte()': src/lte/bindings/ns3module.cc:158490:103: erreur: 'UeMeasure' is not a member of 'ns3' src/lte/bindings/ns3module.cc:158901:103: erreur: 'NeighbourRelation' is not a member of 'ns3' Waf: Leaving directory `/home/ndnSIM/ns-3/build' Build failed -> task in 'ns3module_lte' failed (exit status 1): {task 157630508: cxx ns3module.cc -> ns3module.cc.7.o} ['/usr/bin/g++', '-O0', '-ggdb', '-g3', '-Wall', '-Werror', '-Wno-error=deprecated-declarations', '-fstrict-aliasing', '-Wstrict-aliasing', '-fPIC', '-pthread', '-fno-strict-aliasing', '-fwrapv', '-fstack-protector', '-fno-strict-aliasing', '-fvisibility=hidden', '-Wno-array-bounds', '-pthread', '-pthread', '-fno-strict-aliasing', '-fwrapv', '-fstack-protector', '-fno-strict-aliasing', '-I.', '-I..', '-Isrc/lte/bindings', '-I../src/lte/bindings', '-I/usr/include/python2.7', '-I/usr/include/gtk-2.0', '-I/usr/lib/i386-linux-gnu/gtk-2.0/include', '-I/usr/include/atk-1.0', '-I/usr/include/cairo', '-I/usr/include/gdk-pixbuf-2.0', '-I/usr/include/pango-1.0', '-I/usr/include/gio-unix-2.0', '-I/usr/include/glib-2.0', '-I/usr/lib/i386-linux-gnu/glib-2.0/include', '-I/usr/include/pixman-1', '-I/usr/include/freetype2', '-I/usr/include/libpng12', '-I/usr/include/libxml2', '-I/usr/include', '-DNS3_ASSERT_ENABLE', '-DNS3_LOG_ENABLE', '-DHAVE_SYS_IOCTL_H=1', '-DHAVE_IF_NETS_H=1', '-DHAVE_NET_ETHERNET_H=1', '-DHAVE_PACKET_H=1', '-DHAVE_SQLITE3=1', '-DHAVE_IF_TUN_H=1', '-DHAVE_GSL=1', '-DNS_DEPRECATED=', '-DNS3_DEPRECATED_H', '-DNDEBUG', '-DNDEBUG', 'src/lte/bindings/ns3module.cc', '-c', '-o', 'src/lte/bindings/ns3module.cc.7.o'] How can I fix it ? Best regards.. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Tue Mar 25 16:51:37 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Tue, 25 Mar 2014 16:51:37 -0700 Subject: [ndnSIM] Compilation Error In-Reply-To: <002701cf47aa$7ec07bf0$7c4173d0$@tn> References: <002701cf47aa$7ec07bf0$7c4173d0$@tn> Message-ID: <8A7A245D-59A9-4DA8-B745-01E6B430283A@ucla.edu> Please mention which commit of base NS-3, ndnSIM you're using and which environment (platform, OS version, compiler). I have not seen these errors before, so cannot really comment. If you're not planning to uses python bindings, which always cause problems, just disable them using --disable-python configure command. --- Alex On Mar 24, 2014, at 2:46 PM, Nabil Torjemen / Topnet wrote: > Dear Sir, > When I?m trying to compile ndnSIM, I get the following error as output: > > [1255/1996] cxx: build/src/lte/bindings/ns3module.cc -> build/src/lte/bindings/ns3module.cc.7.o > In file included from src/lte/bindings/ns3module.cc:1:0: > src/lte/bindings/ns3module.h:6857:5: erreur: ?UeMeasure? in namespace ?ns3? does not name a type > src/lte/bindings/ns3module.h:9210:5: erreur: ?NeighbourRelation? in namespace ?ns3? does not name a type > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3UeManager_RecvUeContextRelease(PyNs3UeManager*, PyObject*, PyObject*)?: > src/lte/bindings/ns3module.cc:84753:16: erreur: ?class ns3::UeManager? has no member named ?RecvUeContextRelease? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3UeMeasure__get_m_cellId(PyNs3UeMeasure*, void*)?: > src/lte/bindings/ns3module.cc:85316:51: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3UeMeasure__set_m_cellId(PyNs3UeMeasure*, PyObject*, void*)?: > src/lte/bindings/ns3module.cc:85334:11: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3UeMeasure__get_m_rsrp(PyNs3UeMeasure*, void*)?: > src/lte/bindings/ns3module.cc:85342:56: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3UeMeasure__set_m_rsrp(PyNs3UeMeasure*, PyObject*, void*)?: > src/lte/bindings/ns3module.cc:85360:11: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3UeMeasure__get_m_rsrq(PyNs3UeMeasure*, void*)?: > src/lte/bindings/ns3module.cc:85368:56: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3UeMeasure__set_m_rsrq(PyNs3UeMeasure*, PyObject*, void*)?: > src/lte/bindings/ns3module.cc:85386:11: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3UeMeasure__tp_init__0(PyNs3UeMeasure*, PyObject*, PyObject*, PyObject**)?: > src/lte/bindings/ns3module.cc:85430:11: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc:85430:21: erreur: expected type-specifier > src/lte/bindings/ns3module.cc:85430:21: erreur: expected ?;? > src/lte/bindings/ns3module.cc:85431:11: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc:85432:34: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3UeMeasure__tp_init__1(PyNs3UeMeasure*, PyObject*, PyObject*, PyObject**)?: > src/lte/bindings/ns3module.cc:85452:11: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc:85452:21: erreur: expected type-specifier > src/lte/bindings/ns3module.cc:85452:21: erreur: expected ?;? > src/lte/bindings/ns3module.cc:85453:11: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc:85454:34: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3UeMeasure__copy__(PyNs3UeMeasure*)?: > src/lte/bindings/ns3module.cc:85492:14: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc:85492:24: erreur: expected type-specifier > src/lte/bindings/ns3module.cc:85492:24: erreur: expected ?;? > src/lte/bindings/ns3module.cc:85495:56: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?void PyNs3UeMeasure__tp_clear(PyNs3UeMeasure*)?: > src/lte/bindings/ns3module.cc:85508:15: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc:85509:5: erreur: ?UeMeasure? is not a member of ?ns3? > src/lte/bindings/ns3module.cc:85509:21: erreur: ?tmp? was not declared in this scope > src/lte/bindings/ns3module.cc:85509:33: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc:85510:11: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?void _wrap_PyNs3UeMeasure__tp_dealloc(PyNs3UeMeasure*)?: > src/lte/bindings/ns3module.cc:85529:80: erreur: ?struct PyNs3UeMeasure? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3LteEnbRrc_HandoverLeavingTimeout(PyNs3LteEnbRrc*, PyObject*, PyObject*)?: > src/lte/bindings/ns3module.cc:98486:16: erreur: ?class ns3::LteEnbRrc? has no member named ?HandoverLeavingTimeout? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3LteEnbRrc_ConnectionRejectedTimeout(PyNs3LteEnbRrc*, PyObject*, PyObject*)?: > src/lte/bindings/ns3module.cc:98530:16: erreur: ?class ns3::LteEnbRrc? has no member named ?ConnectionRejectedTimeout? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3LteEnbRrc_HandoverJoiningTimeout(PyNs3LteEnbRrc*, PyObject*, PyObject*)?: > src/lte/bindings/ns3module.cc:98582:16: erreur: ?class ns3::LteEnbRrc? has no member named ?HandoverJoiningTimeout? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3LteEnbRrc_AddX2Neighbour(PyNs3LteEnbRrc*, PyObject*, PyObject*)?: > src/lte/bindings/ns3module.cc:98773:16: erreur: ?class ns3::LteEnbRrc? has no member named ?AddX2Neighbour? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3LteHelper_GetSchedulerType(PyNs3LteHelper*)?: > src/lte/bindings/ns3module.cc:101868:25: erreur: ?class ns3::LteHelper? has no member named ?GetSchedulerType? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3NeighbourRelation__get_m_detectedAsNeighbour(PyNs3NeighbourRelation*, void*)?: > src/lte/bindings/ns3module.cc:118762:67: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3NeighbourRelation__set_m_detectedAsNeighbour(PyNs3NeighbourRelation*, PyObject*, void*)?: > src/lte/bindings/ns3module.cc:118775:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3NeighbourRelation__get_m_noHo(PyNs3NeighbourRelation*, void*)?: > src/lte/bindings/ns3module.cc:118783:67: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3NeighbourRelation__set_m_noHo(PyNs3NeighbourRelation*, PyObject*, void*)?: > src/lte/bindings/ns3module.cc:118796:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3NeighbourRelation__get_m_noRemove(PyNs3NeighbourRelation*, void*)?: > src/lte/bindings/ns3module.cc:118804:67: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3NeighbourRelation__set_m_noRemove(PyNs3NeighbourRelation*, PyObject*, void*)?: > src/lte/bindings/ns3module.cc:118817:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3NeighbourRelation__get_m_noX2(PyNs3NeighbourRelation*, void*)?: > src/lte/bindings/ns3module.cc:118825:67: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3NeighbourRelation__set_m_noX2(PyNs3NeighbourRelation*, PyObject*, void*)?: > src/lte/bindings/ns3module.cc:118838:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3NeighbourRelation__get_m_physCellId(PyNs3NeighbourRelation*, void*)?: > src/lte/bindings/ns3module.cc:118846:51: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3NeighbourRelation__set_m_physCellId(PyNs3NeighbourRelation*, PyObject*, void*)?: > src/lte/bindings/ns3module.cc:118864:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3NeighbourRelation__tp_init__0(PyNs3NeighbourRelation*, PyObject*, PyObject*, PyObject**)?: > src/lte/bindings/ns3module.cc:118922:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc:118922:21: erreur: expected type-specifier > src/lte/bindings/ns3module.cc:118922:21: erreur: expected ?;? > src/lte/bindings/ns3module.cc:118923:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc:118924:34: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?int _wrap_PyNs3NeighbourRelation__tp_init__1(PyNs3NeighbourRelation*, PyObject*, PyObject*, PyObject**)?: > src/lte/bindings/ns3module.cc:118944:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc:118944:21: erreur: expected type-specifier > src/lte/bindings/ns3module.cc:118944:21: erreur: expected ?;? > src/lte/bindings/ns3module.cc:118945:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc:118946:34: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?PyObject* _wrap_PyNs3NeighbourRelation__copy__(PyNs3NeighbourRelation*)?: > src/lte/bindings/ns3module.cc:118984:14: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc:118984:24: erreur: expected type-specifier > src/lte/bindings/ns3module.cc:118984:24: erreur: expected ?;? > src/lte/bindings/ns3module.cc:118987:56: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?void PyNs3NeighbourRelation__tp_clear(PyNs3NeighbourRelation*)?: > src/lte/bindings/ns3module.cc:119000:15: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc:119001:5: erreur: ?NeighbourRelation? is not a member of ?ns3? > src/lte/bindings/ns3module.cc:119001:29: erreur: ?tmp? was not declared in this scope > src/lte/bindings/ns3module.cc:119001:41: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc:119002:11: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?void _wrap_PyNs3NeighbourRelation__tp_dealloc(PyNs3NeighbourRelation*)?: > src/lte/bindings/ns3module.cc:119021:80: erreur: ?struct PyNs3NeighbourRelation? has no member named ?obj? > src/lte/bindings/ns3module.cc: In function ?void initlte()?: > src/lte/bindings/ns3module.cc:158490:103: erreur: ?UeMeasure? is not a member of ?ns3? > src/lte/bindings/ns3module.cc:158901:103: erreur: ?NeighbourRelation? is not a member of ?ns3? > Waf: Leaving directory `/home/ndnSIM/ns-3/build' > Build failed > -> task in 'ns3module_lte' failed (exit status 1): > {task 157630508: cxx ns3module.cc -> ns3module.cc.7.o} > ['/usr/bin/g++', '-O0', '-ggdb', '-g3', '-Wall', '-Werror', '-Wno-error=deprecated-declarations', '-fstrict-aliasing', '-Wstrict-aliasing', '-fPIC', '-pthread', '-fno-strict-aliasing', '-fwrapv', '-fstack-protector', '-fno-strict-aliasing', '-fvisibility=hidden', '-Wno-array-bounds', '-pthread', '-pthread', '-fno-strict-aliasing', '-fwrapv', '-fstack-protector', '-fno-strict-aliasing', '-I.', '-I..', '-Isrc/lte/bindings', '-I../src/lte/bindings', '-I/usr/include/python2.7', '-I/usr/include/gtk-2.0', '-I/usr/lib/i386-linux-gnu/gtk-2.0/include', '-I/usr/include/atk-1.0', '-I/usr/include/cairo', '-I/usr/include/gdk-pixbuf-2.0', '-I/usr/include/pango-1.0', '-I/usr/include/gio-unix-2.0', '-I/usr/include/glib-2.0', '-I/usr/lib/i386-linux-gnu/glib-2.0/include', '-I/usr/include/pixman-1', '-I/usr/include/freetype2', '-I/usr/include/libpng12', '-I/usr/include/libxml2', '-I/usr/include', '-DNS3_ASSERT_ENABLE', '-DNS3_LOG_ENABLE', '-DHAVE_SYS_IOCTL_H=1', '-DHAVE_IF_NETS_H=1', '-DHAVE_NET_ETHERNET_H=1', '-DHAVE_PACKET_H=1', '-DHAVE_SQLITE3=1', '-DHAVE_IF_TUN_H=1', '-DHAVE_GSL=1', '-DNS_DEPRECATED=', '-DNS3_DEPRECATED_H', '-DNDEBUG', '-DNDEBUG', 'src/lte/bindings/ns3module.cc', '-c', '-o', 'src/lte/bindings/ns3module.cc.7.o'] > > How can I fix it ? > Best regards.. > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From ioannoa at scss.tcd.ie Wed Mar 26 12:51:47 2014 From: ioannoa at scss.tcd.ie (ioannoa at scss.tcd.ie) Date: Wed, 26 Mar 2014 19:51:47 -0000 Subject: [ndnSIM] consumer attribute Message-ID: <1cb996e02f9668fa7f2b228c450cdc56.squirrel@webmail.scss.tcd.ie> Hello everyone, I am trying to find a way to link my tables in my simulation file with each consumer (the consumer class). I want each consumer to have access (just reading) on two of the tables that i define in the .cc file in the scenarios directory. I have read about attributes and found only two related: ObjectVector Vector As fas as i understand though none of these would do cause: ObjectVector still supports ns3 objects that inherit the Object class and Vector is standard defined up to 3 dimensions. My tables in the .cc simulation file may be different in each run depending on the parameters that i am giving. Plus, they are of type std::vector. The question is: How could i pass these tables as attributes (or any other way) into the consumer class? Anyone that had something similar? Google search honestly gives me nothing. Kind regards, Andriana. From amin1431 at yahoo.com Thu Mar 27 03:36:28 2014 From: amin1431 at yahoo.com (amin1431) Date: Thu, 27 Mar 2014 03:36:28 -0700 (PDT) Subject: [ndnSIM] Co-operation for a new Caching mechanism in ndnSIM In-Reply-To: <1395915899.22508.YahooMailNeo@web160104.mail.bf1.yahoo.com> References: <1395915899.22508.YahooMailNeo@web160104.mail.bf1.yahoo.com> Message-ID: <1395916588.69535.YahooMailNeo@web160103.mail.bf1.yahoo.com> Dear friends, There is a research project about cache replacement policies in ndnSIM (in NDN). We invite people who know ndnSIM programming about cache manipulation and analysis. Is there any interested person to join us as co-author? please send email to amin1431 at yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Thu Mar 27 13:16:06 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 27 Mar 2014 13:16:06 -0700 Subject: [ndnSIM] Questions About the Hop Counts In-Reply-To: <201403261452050413834@qq.com> References: <201403261452050413834@qq.com> Message-ID: Hi Aaron, Sorry for the confusion. But here is the basic rule that I tried to explain in the docs, but apparently fail (you're not the first one who confused). HopCount is increased any time "Send" is called from the forwarder side. forwarder -> other node; forwarder -> applications. It is never increased when application sends anything towards the forwarder, since it doesn't use "Send" method, it uses a different mechanism provided by AppFace/ApiFace. So. Again. When application sends out interest/data, hop count is not increased (send out is done via an appFace callback), when application receives interest/data, hop count **is** increased. Hop count cannot be zero. If data is satisfied from local cache, hop count would be 1 (app->forwarder +0, forwarder->app +1). Is it still confusing? --- Alex On Mar 25, 2014, at 11:52 PM, Aaron wrote: > Hi, Alex > > Why the HopCounts in the AppDelayTracer can be an odd hop counts? Since one interest matches one data, if the hop counts combine the interest and data, it should be a even hop counts. What causes an odd hop counts? > > Another question is that, the hop counts can be zero if the consumer gets data from its access node, is that right? I'm not sure how the consumer as an application sends its interest to the access node in the code? > > void > Consumer::SendPacket () > { > ...... > m_transmittedInterests (interest, this, m_face); > m_face->ReceiveInterest (interest); > ..... > } > > m_face->ReceiveInterest (interest); It seems to send the interest to the AppFace that is towards access node. > > > bool > Face::ReceiveInterest (Ptr interest) > { > if (!IsUp ()) > { > // no tracing here. If we were off while receiving, we shouldn't even know that something was there > return false; > } > > m_upstreamInterestHandler (this, interest); > return true; > } > > I'not sure which function will call the m_upstreamInterestHandler so that the interest is finally sent to the ForwardingStrategy::Oninterest()? > > > Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Thu Mar 27 13:18:56 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 27 Mar 2014 13:18:56 -0700 Subject: [ndnSIM] consumer attribute In-Reply-To: <1cb996e02f9668fa7f2b228c450cdc56.squirrel@webmail.scss.tcd.ie> References: <1cb996e02f9668fa7f2b228c450cdc56.squirrel@webmail.scss.tcd.ie> Message-ID: <15BAF775-1FD5-475C-A8CC-F612010AA1D0@ucla.edu> Hi Andriana, Not very sure what tables you want to pass, but can you make just an object (derived from ns3::Object) that contains the whole table you want to pass (or being a container for all parameters you want to pass)? This way you don't need to jingle with NS-3 and you can simply pass your object as an attribute. -- Alex On Mar 26, 2014, at 12:51 PM, ioannoa at scss.tcd.ie wrote: > Hello everyone, > > I am trying to find a way to link my tables in my simulation file with > each consumer (the consumer class). I want each consumer to have access > (just reading) on two of the tables that i define in the .cc file in the > scenarios directory. I have read about attributes and found only two > related: > ObjectVector > Vector > > As fas as i understand though none of these would do cause: > ObjectVector still supports ns3 objects that inherit the Object class and > Vector is standard defined up to 3 dimensions. > > My tables in the .cc simulation file may be different in each run > depending on the parameters that i am giving. Plus, they are of type > std::vector. > > The question is: How could i pass these tables as attributes (or any other > way) into the consumer class? > > Anyone that had something similar? Google search honestly gives me nothing. > > Kind regards, > Andriana. > > > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim From azarmehr65 at gmail.com Thu Mar 27 23:23:12 2014 From: azarmehr65 at gmail.com (Azar Fazel) Date: Thu, 27 Mar 2014 23:23:12 -0700 Subject: [ndnSIM] question about FIB,CS, PIT Message-ID: Hi Alex I'm new in ndnsim and am trying to run a scenario to see the behavior of CS, FIB and PIT. In this scenario I have one consumer and two producers in a 9 grid topology. There is a list of prefixes that every time consumer selects one of them randomly. Every producer that has that prefix will response to this request. Before sending the requests, I have assigned some of the prefixes to producer 1 and some of them to producer 2 ( by using SetAttribuyes, Install and Addorigins methods). and I think these prefixes are actually the FIB entries for each producer. but when I print the FIB table, the entries does not make any sense, they are not what I expect. Can you please help me, how can I implement a scenario to see the functionality of CS, FIB and PIT together. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From amin1431 at yahoo.com Mon Mar 31 04:20:16 2014 From: amin1431 at yahoo.com (amin1431) Date: Mon, 31 Mar 2014 04:20:16 -0700 (PDT) Subject: [ndnSIM] Cache Pollution in ndnSIM Message-ID: <1396264816.5390.YahooMailNeo@web160104.mail.bf1.yahoo.com> Dear Alex, I am going to implement two common cache pollution attacks in my scenario in ndnSIM. i.e., (1) locality disruption: generate some Interest requests for non-popular contents in caches, thus ruining the cached contents locality. (2) false-locality: repeatedly request the same set of (fake) contents, thus creating false contents locality in cache. Would you mind please giving me some hints to how implement them? /amin -------------- next part -------------- An HTML attachment was scrubbed... URL: