[ns] unable to have a drop-target in AODV
Dear ns-users, I am working with AODV and for that in TCL script, I have attached its agent to node-0 as follows: *set ragent [new Agent/AODV 0] $node_(0) attach $ragent 255* Other nodes are configured through the basic method viz. using* $ns_ node-config -adhocRouting AODV* When I run the simulation, AODV agent of the node-0 works well but it is not creating the drop-target (*so, drop_ = 0*), *which is there with other nodes.** Hence*, I am unable to log the drop events from node-0 in the trace file and the packet is directly freed. (as per* Connector::drop()*). I will be grateful by having the reason behind this and the probable solution. Thanking in anticipation. -- Pathik Shah
[ns] From where Connector::drop_ is initialized .?
Dear all, We know in function Connector::drop(Packet* p, const char *s), if *drop_* iszero then it will pass the packet to the object using *drop_*-recv(p,s). I want to know *where* and *when* it was *initialized*? Hoping for the best help asap. *p.s.* : It is clear to me that when we set up a simple simulation, we do not write for the initialization of the drop_. Although it is initialized. So I am asking about the insight. -- Pathik Shah
[ns] A very trivial but conceptual question regarding to AODV in MANETs
Dear users, Please let me have your vote for this simple but conceptual question regarding to AODV in MANETs. The question is- *We can expect RREP from only those nodes who accepted our broadcasted RREQ in past* True or False,..? Thanking in anticipation... -- With kind regards... Pathik Shah
Re: [ns] the address of sending RREP
Dear shanmugha priya balasubramanian, Codes for maintaining neighbor information are already written there in AODV files. The basic *class* *AODV_Neighbor* is defined in *aodv_rtable.h* denoting AODV neighbor cache history. Again there are few Neighbor Management Functions declared in *aodv.h* and further defined in *aodv.cc* which use the object of the basic class i.e. *AODV_Neighbor *nb* (see the part of Neighbor Management Functions at the end of aodv.cc). By using these all logic, list of node's neighbors is already maintained in AODV. The all remaining work is about the printing that list for debugging purpose. So for that, you can write your own function along with these defined functions and subsequently call that function whenever you require. *Make sure* that for dealing with neighbor related information, you must require to enable the HELLO packets in AODV. Hope it helps Good Luck..! On Sat, Jan 21, 2012 at 10:04 AM, shanmugha priya balasubramanian shanmughapri...@gmail.com wrote: sir, i am new to ns. i am implementingpreventing flooding attack in MANETusing AODV sir i need to maintain the list of neighbours of each node, how can i recuperate the address of the node sending HELLO Many thanx in advance.pls help me Awaiting ur reply Shanmugha Priya On 1/20/12, Pathik Shah pathikmsha...@gmail.com wrote: -- Forwarded message -- From: Pathik Shah pathikmsha...@gmail.com Date: Fri, Jan 20, 2012 at 10:51 AM Subject: Re: [ns] the address of sending RREP To: ziralda kader.el...@gmail.com Cc: ns-users@isi.edu Hi there, in recvReply function, *ih-saddr()* will give node id of RREP originator (ultimate source of RREP) *ih-daddr()* will give id of node to which this RREP is to be destined (ultimate destination of RREP) and *rp-rp_src* will give id of node from which you have received this RREP *Please note* that it is obvious to have same values of ih-saddr() and rp-rp_src if you are a neighbor of RREP originator. hope it helps you. I would like to have your acknowledgement if my information lets you solve your problem. Based on that, a generic code (showing such node IDs while debugging) can be published. Good Luck... On Thu, Jan 19, 2012 at 11:54 PM, ziralda kader.el...@gmail.com wrote: hello ns-users Please when a node X send a RREP to node Y, in the recvReply function, how can i recuperate the address of the node sending RREP please answer me i really need it Many thanks in advance -- View this message in context: http://old.nabble.com/the-address-of-sending-RREP-tp33169782p33169782.html Sent from the ns-users mailing list archive at Nabble.com. -- With kind regards... Pathik Shah -- With kind regards... Pathik Shah -- With kind regards... Pathik Shah
[ns] the address of sending RREP
-- Forwarded message -- From: Pathik Shah pathikmsha...@gmail.com Date: Fri, Jan 20, 2012 at 10:51 AM Subject: Re: [ns] the address of sending RREP To: ziralda kader.el...@gmail.com Cc: ns-users@isi.edu Hi there, in recvReply function, *ih-saddr()* will give node id of RREP originator (ultimate source of RREP) *ih-daddr()* will give id of node to which this RREP is to be destined (ultimate destination of RREP) and *rp-rp_src* will give id of node from which you have received this RREP *Please note* that it is obvious to have same values of ih-saddr() and rp-rp_src if you are a neighbor of RREP originator. hope it helps you. I would like to have your acknowledgement if my information lets you solve your problem. Based on that, a generic code (showing such node IDs while debugging) can be published. Good Luck... On Thu, Jan 19, 2012 at 11:54 PM, ziralda kader.el...@gmail.com wrote: hello ns-users Please when a node X send a RREP to node Y, in the recvReply function, how can i recuperate the address of the node sending RREP please answer me i really need it Many thanks in advance -- View this message in context: http://old.nabble.com/the-address-of-sending-RREP-tp33169782p33169782.html Sent from the ns-users mailing list archive at Nabble.com. -- With kind regards... Pathik Shah -- With kind regards... Pathik Shah
