Flow Monitor: Did not read the Rx Bytes.

[noorm...@gmail.com]

Hi all,

I would like to measure the Packet Loss, Delay and Throughput between the UeNode and remoteHost in PMIPV6.

The flow monitor able to read the value for the Tx Bytes and Packet Loss.However, it read the Rx bytes as 0, thus resulting Throughput = 0.

And same goes with the Delay.

Could anyone of you can guide or help me what are the steps that I should do in order to obtain the result for Throughput and Delay?

Attached  are the code and print screen for your references

Thank you

Regards

[rose...@gmail.com]

Could you please tell me in which version of the NS3, such as NS-3.26 or other NS3 versions, you implemented the PMIPv6 protocol? I'm stuck with implementing PMIPv6 in NS-3.26.

[noormadinah allias]

Hi,

I am using ns-3.19, but patch it to ns-3.20.

However for the flow monitor, I used the flow monitor from ns-3.21.

What I am doing is, 

i. copy the whole folder of flow monitor folder from ns-3.21

ii. paste it into /src in the patch ns-3 version.

Then clean, configure and rebuild ns3.

./waf

./waf configure

./waf

Hope this can help you

--
Posting to this group should follow these guidelines https://www.nsnam.org/wiki/Ns-3-users-guidelines-for-posting
---
You received this message because you are subscribed to the Google Groups "ns-3-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ns-3-users+...@googlegroups.com.
To post to this group, send email to ns-3-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ns-3-users.
For more options, visit https://groups.google.com/d/optout.

[艾玲玲]

Hello

, 

I have the same problem when using Flow Monitor. Have you solved the problem? If so, can you share with me?

Or anyone can give a hint on this?

My topology:

remotehost(1.0.0.2) --pgw--enb--UE(7.0.0.3)

UE is packet source, and remotehost is packet sink. 

With the NS_LOG, I can see the packetSink is receiving packets :

At time 1.18909s packet sink received 1400 bytes from 7.0.0.3 port 49153 total Rx 54188400 bytes

At time 1.18909s packet sink received 1400 bytes from 7.0.0.3 port 49153 total Rx 54189800 bytes

At time 1.18924s packet sink received 1400 bytes from 7.0.0.3 port 49153 total Rx 54191200 bytes

At time 1.18925s packet sink received 1400 bytes from 7.0.0.3 port 49153 total Rx 54192600 bytes

At time 1.18925s packet sink received 1400 bytes from 7.0.0.3 port 49153 total Rx 54194000 bytes

At time 1.18925s packet sink received 1400 bytes from 7.0.0.3 port 49153 total Rx 54195400 bytes

At time 1.18925s packet sink received 1400 bytes from 7.0.0.3 port 49153 total Rx 54196800 bytes

But the Flow Monitor reads the TX packets numbers, but 0 RX packets. 

FlowID: 1 (TCP 7.0.0.2/49153 --> 1.0.0.2/20000)

        TX bitrate: 21727.22 kbit/s

        RX bitrate: None

        Mean Delay: None

        Packet Loss Ratio: None

FlowID: 2 (TCP 7.0.0.3/49153 --> 1.0.0.2/20000)

        TX bitrate: 21717.52 kbit/s

        RX bitrate: None

        Mean Delay: None

        Packet Loss Ratio: None

FlowID: 3 (TCP 1.0.0.2/20000 --> 7.0.0.2/49153)

        TX bitrate: 778.91 kbit/s

        RX bitrate: None

        Mean Delay: None

        Packet Loss Ratio: None

FlowID: 4 (TCP 1.0.0.2/20000 --> 7.0.0.3/49153)

        TX bitrate: 778.57 kbit/s

        RX bitrate: None

        Mean Delay: None

        Packet Loss Ratio: None

Best Regards

Lingling Ai