Thanks for the help. After all I managed to do what I wanted. I created a new
type of queue that I use to do the job of a firewall. At least it works :P
--
View this message in context:
http://old.nabble.com/Properly-drop-packet-tp34250208p34255131.html
Sent from the ns-users mailing list archi
After a closer look I saw that in the trace files the packets are delivered
normally. They only don't show up in the nam trace after the node that is
supposed to drop them...
--
View this message in context:
http://old.nabble.com/Properly-drop-packet-tp34250208p34251562.html
Sent from the ns-us
Thanks for your responce,
in my case I have a wired scenario and I use the default (static) routing.
As I say in the previous post, I do all the work in the connector class. I
don't really care from which layer the packet is dropped, as long as I have
access to the packet to read the information
first of all you should determine which layer is responsible for dropping
the packet?
I suppose it's routing agent, for example. then, put this line wherever you
want to drop the packet p:
drop(p, DROP_RTR_YOUR_REASON);
put this at line 97 in file %NS_DIRECTORY%/trace/cmu-trace.h
#define DROP_RTR
To provide some more info:
Suppose I have the following topology:
http://old.nabble.com/file/p34250683/topology.jpeg
What I want is node D to drop packets from some specific nodes. What I've
done is the following:
I added one variables in the node.cc && node.h to define if the packets from
th
