--
You received this message because you are subscribed to the Google Groups "omnetpp" group.
To post to this group, send email to omn...@googlegroups.com.
To unsubscribe from this group, send email to omnetpp+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/omnetpp?hl=en.
To unsubscribe from this group, send email to omnetpp+u...@googlegroups.com.
ThruputMeter module works also fine between TCP and TCPSessionApp.
updateStats(simTime(), PK(msg)->getBitLength()); The reason is that the active open message is no cPacket.cPacket is a descendant of cMessage.
ups sorry, should be a pointer:
cMessage *tempMsg = dynamic_cast<cPacket*>(msg);
> if(tempMsg)
> {
> send(msg, "out");
> return;
>
> }
>
> updateStates(....
Can you try again
Here the code:
cMessage *tempMsg = dynamic_cast<cMessage*>(msg);
if(tempMsg)
{
send(msg, "out");
return;
}
cPacket *tempMsg = dynamic_cast<cPacket*>(msg); if(!tempMsg) { send(msg, "out"); return; } updateStates....
I have tested it with my simulation. It works with the code I have send you.
The reason is that the active open message is not a cPacket and
therefore it doesnt matter not to put it in updateStates.
Best regards
Am 26.11.2010 16:47, schrieb Stefano:
cPacket *tempMsg = dynamic_cast<cPacket*>(msg); if(!tempMsg) { send(msg, "out"); return;
} I have tested it. It works fine. I have results in the thruputMeter vectors with this... updateStates....
>> read more �
To unsubscribe from this group, send email to omnetpp+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/omnetpp?hl=en.
Send me your handleMessage code.
>> read more �
https://github.com/aarizaq/inetmanet-3.x/commit/2a4b2cd152b6754f774bd4bb14d19309b0a41476
This modification allow to activate the meter in the ini file
**.hasThrugmeter = true
--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
omnetpp+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+unsubscribe@googlegroups.com.
Have you checked the node 3?
Apparently, it arrives a packet to the node 3 that doesn’t have udp module.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+unsubscribe@googlegroups.com.
Here you can find a simple description with figures of the rto
The mobility has a strong influence in the results OLSR
If you has high mobility the results of OLSR will be bad, the proactive protocols work well in static/quasi-static networks, in conditions of high mobility the results will be bad with independency of the number of attackers
OLSR and BATMAN will have problems, it is a high mobility scenario.
I suppose that the sources doesn't begin the transmission inmediately, OLSR and BATMAN need some time to build the routing tables, depending of the diameter of the network and number of nodes, it can take even 60 seconds
In my simulations the sources begin the transmission after the second 60, and 80 seconds is very small for routing, if you want good statistics you need to simulate several thousand of packets.
De: omn...@googlegroups.com [mailto:omn...@googlegroups.com]
En nombre de Wian Virgi
Enviado el: miércoles, 08 de febrero de 2017 1:26
Para: omn...@googlegroups.com
Asunto: Re: [Omnetpp-l] Re: INET, throughput measure
Thank you Mr.Alfonso..
My simulation have 80s that enough or not for OLSR and AODV simulation?
And I didn't know my simulation is already wireless mesh or not can you checking my simulatio right or not? Thank you very much you always want discusion with me
On Mon, Feb 6, 2017 at 5:56 PM Alfonso Ariza Quintana <aari...@hotmail.com> wrote:
I suppose that the sources doesn't begin the transmission inmediately, OLSR and BATMAN need some time to build the routing tables, depending of the diameter of the network and number of nodes, it can take even 60 seconds
De: omn...@googlegroups.com <omn...@googlegroups.com> en nombre de Wian Virgi <wianvi...@gmail.com>
Enviado: domingo, 5 de febrero de 2017 11:23:18
Para: omn...@googlegroups.com
Asunto: Re: [Omnetpp-l] Re: INET, throughput measure
Mr.Alfonso I have new quetion.. Why when I run my simulation Simpledropping with stationary mobility in AODV I haven't packet loss value? while in OLSR I have packet loss value? You said proaktif will have problem with mobility so I try stationary mobility with AODV too.. Thank you Mr. Alfonso...
On Wed, Feb 1, 2017 at 12:59 AM Alfonso Ariza Quintana <aari...@hotmail.com> wrote:
OLSR and BATMAN will have problems, it is a high mobility scenario.
De: omn...@googlegroups.com <omn...@googlegroups.com> en nombre de Wian Virgi <wianvi...@gmail.com>
Enviado: martes, 31 de enero de 2017 12:45:07
Para: omn...@googlegroups.com
Asunto: Re: [Omnetpp-l] Re: INET, throughput measure
I used randomWPMobility... What do you think about it? When I used StationaryMobility Still same...
On Tue, Jan 31, 2017 at 6:33 PM Alfonso Ariza Quintana <aari...@hotmail.com> wrote:
The bigger the best, the inconvenience is the duration of the simulation.
> >>>>>>>> without all possible retransmissions caused by TCP). In UDP, these
> >>>>>>>> values are the same. UDP is not asking to resubmit data if it's
> >>>>>>>> getting lost on the wireless channel, because it has no flow control.
> >>>>>>>> Frank
> >>>>>>>> On Nov 22, 12:45 pm, Pinto Pinto <pintox...@gmail.com> wrote:
> >>>>>>>>> Hi,
> >>>>>>>>> you should add the ThruputMeter module, which will measure the throughput in
> >>>>>>>>> the application level. In order to do that, you should add 2 ThruputMeter
> >>>>>>>>> modules between the IP and the TCP, one for each direction of the packets
> >>>>>>>>> (ip-->TCP : incoming throughput, TCP-->IP outgoing throughput).
> >>>>>>>>> Hope this helps
> >>>>>>>>> bye
> >>>>>>>>> pintoX
> >>>>>>>>> On Mon, Nov 22, 2010 at 11:18 AM, Stefano <ste...@gmail.com> wrote:
> >>>>>>>>>> Ok, just to be sure and give a bump to the thread: does anybody know a
> >>>>>>>>>> simple method to measure throughput when using TCPSessionApp/
> >>>>>>>>>> TCPSinkApp?
> >>>>>>>>>> S
> >>>>>>>>>> On Nov 19, 4:09 pm, Stefano <ste...@gmail.com> wrote:
> >>>>>>>>>>> Hello everybody,
> >>>>>>>>>>> I need to measure network throughput within a multi-hop wireless
> >>>>>>>>>>> network. Right now, I'm testing my network with fixed-size file
> >>>>>>>>>>> transfers between a central node (TCPSinkApp) and many peripheral AP
> >>>>>>>>>>> (TCPSessionApp) which generate traffic at tcp level.
> >>>>>>>>>>> The problem is that I want to measure the actual throughput
> >>>>>>>>>>> (application level) of my file transfer in a simple way. Is there
> >>>>>>>>>>> something integrated into TCPSessionApp or do I need some other block?
> >>>>>>>>>>> I've seen ThruputMeter, but it lacks of documentation, can you point
> >>>>>>>>>>> me to some example?
> >>>>>>>>>>> Thank you.
> >>>>>>>>>> --
> >>>>>>>>>> You received this message because you are subscribed to the Google Groups
> >>>>>>>>>> "omnetpp" group.
> >>>>>>>>>> To post to this group, send email to omn...@googlegroups.com.
> >>>>>>>>>> To unsubscribe from this group, send email to
> >>>>>>>>>> omn...@googlegroups.com<omnetpp%2Bunsu...@googlegroups.com >
> >>>>>>>>>> .
> >>>>>>>>>> For more options, visit this group at
> >>>>>>>>>>http://groups.google.com/group/omnetpp?hl=en.
> >>>>>> Hi,
> >>>>>> ThruputMeter module works also fine between TCP and TCPSessionApp.
> >> have you checked if you have set in the .ini file the run time of the
> >> simulation. Perhaps this is the reason why it stops before transmitting
> >> the whole data?